Interesting. I didn’t even know those instructions existed. I was planning to try out Plasma Mobile by installing postmarketOS.
1 Like
Why Installing instead Testing? 
I guess that Plasma Mobile will in Gnu Crimson.
Purism
2 Likes
The installation instruction at the Install Plasma Mobile are fine. I modified the deb Index of /debpm/ buster main to use bullseye.
The phone boots fine after the installation. But the Plasma Mobile GUI does not show up. The screen is blank. @dos, do you have any suggestions?
1 Like
Try the instructions here to install Plasma Mobile: Librem 5 and KDE Plasma mobile - #30 by lgtmak
1 Like
I’m just starting to experiment with PostmarketOS now. I tried install plasma-mobile and it didn’t manage to boot into the GUI, instead showing a console login. I couldn’t log on as the keyboard input only seemed to work 50% of the time, so didn’t manage to enter my password.
I tried gnome-mobile and that is working (though it is quite laggy). Anyone have luck getting plasma-mobile to install recently?
Will keep on trying. Going to try crymson with plasma-mobile first (Librem 5 and KDE Plasma mobile - #30 by lgtmak).
The librem5-flash-image script seems to be broken for me:
Traceback (most recent call last):
File "/home/jack/Development/_external/librem5/librem5-flash-image/./scripts/librem5-flash-image", line 538, in <module>
sys.exit(main())
^^^^^^
File "librem5/librem5-flash-image/./scripts/librem5-flash-image", line 521, in main
flash_image(uuu_target, args.debug)
File "librem5/librem5-flash-image/./scripts/librem5-flash-image", line 351, in flash_image
subprocess.check_call(['uuu', uuu_target])
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['uuu', './tmp_librem5-flash-image_y9jnn12b/flash_librem5r4.lst']' returned non-zero exit status 255.
2 Likes
I got it mostly working with Mobian with their March installer with LUKS + BTRFS, but couldn’t figure out how to get KDE Discover working/appearing. I have it working now via Mobian on top of the original Phosh (most recent installer with LUKS + BTRFS), after I resolved package dependency issues. I have only been using it as a tablet though, didn’t test the phone/sms.
I somehow ended up with Plasma Desktop Wayland + X11 installed as well, which probably helped get it working, but I want to remove these sometime soon, as the login screen is now too small
2 Likes
Use a recent version of Debian or its derivatives on a USB drive, then follow the instructions again:
Otherwise, use the thread I linked and the instructions I provided within it.
Hello,
I’ve followed the steps in the tutorial so far. I added
deb https://repo.kaidan.im/debpm/ buster main devkit
to /etc/apt/sources.list but apt update says
Err:5 Index of /debpm/ buster Release
404 Not Found [IP: …]
E: The depot »Index of /debpm/ buster Release« contains no release file.
What is the status of lgtmak’s solution?
My release is byzantium, not crimson. So is crimson the newer development version and purism is going to add plasma mobile support there?
And I update by changing byzantium to crimson in the sources.list, run
apt-get update
apt-get upgrade
reboot
ant then I can continue installing plasma mobile.?
1 Like
That documentation is very outdated. Amber is based on Buster, whereas Byzantium is based on Bullseye, so you will at least need to change the Debian codename in your entry:
deb https://repo.kaidan.im/debpm/ bullseye main devkit
Ok, I will try this. Upgrading to crimson didn’t work. The phone is not showing a keyboard for file system password on boot but says after a few seconds, that all attempts had failed. I need to reflash byzantium and try again.
1 Like
Upgrading from Byzantium to Crimson via apt sources is currently unsupported and will cause system instability.
Ok… I’ve added the line with bullseye to sources.list. apt update now gives me some warnings like
Loading of configuration file »devkit/binary-arm64/Packages« skipped, because the depot »https://repo.kaidan.im/debpm bullseye InRelease« does not contain the component »devkit«.
Should I proceed? Should I install crimson on another way (which?)?
1 Like
The very outdated documentation was for the Librem 5 development kit, so you will need to remove that from the entry:
deb https://repo.kaidan.im/debpm/ bullseye main
Plasma Mobile from Kaidan’s repository only has support up to Bullseye.
When I was thumbling around with mobian and phosh parallel to plasma I had a similar issue.
Have you tried to change the options behind the shutdown button? I was able to get it working by changing the login screen.
Both phosh and plasma at the same time had some quirks.
Mobian had version trixie.
2 Likes
Recently I installed plasma mobile with PostmarketOS stable branch. It booted into GUI fine, but it was not very stable. I was stuck in some settings screen with no way to exit the full screen. PostmarketOS phosh was fine, but then I was more comfortable with phosh on Mobian Bookworm, so using that currently. I had to downgrade to bookworm since trixie was too unstable (phone was powering off while connected to charger when kept for charging over night - this is fine in bookworm).
2 Likes
If I remember correctly, plasma mobile comes with a matrix client (While the nheko-version of phosh is very unusable). This is one important motivation for me to try plasma
1 Like
Ok, I’ve tried to install Plasma Mobile with
deb https://repo.kaidan.im/debpm/ bullseye main
The installation works, but the login screen stays black after reboot. Via SSH I can see, that simplelogin and phosh were running. I disabled phosh and rebooted, but still no success. So I disabled simplelogin and enabled phosh again. Good news: Phosh still works then.
What am I missing?
1 Like
I suspect the very outdated instructions simply do not fully work with the provided repository, which is likely why @lgtmak provided instructions in a different topic.
Have you tryied to use an external monitor or swipe down from the top.
Maybe post a picture because it is difficult to imagine your problem. Either the display is not set and therfore useable but black or it is not detected correctly and not useable in your current config.
Did you change from official pureos port or did you use postmarketos or mobian?
1 Like
lgtmak’s solution requires upgrading to crimson, which didn’t work in my case for whatever reason (Don’t remember yet).
This points me to my last question: Will crimson support Plasma Mobile out of the box?
@ein_dude I installed Plasma Mobile on top of pureOS / bullseye. There was no menu at all.
1 Like