Byzantium backports unofficial

[galilley]

What is ‘stable’ for you?..
It works well with sms and show me notification about whatsapp (WA) messages using libpurple (LP). I can not answer as I do not see any WA contacts due to lacks in integration with LP, but it is not for what chatty was designed. I built the last version with ‘debugoptimized’ rather that ‘plain’ and it seems that it woks a little bit faster that before. So, it is better to try and do it with some large number of messages.

[nerd7473]

Have been having recent issues with Chatty, so I may try backports before I reflash.

[galilley]

Upgrade to Crimson backports

Today I finally made a backup (for the first time) and tried to upgrade my daily used L5 with Byzantium backports to Crimson ones! Surprisingly, but everything went more or less well ! A few packages were fixed in order to provide the right replacement, so, I will make a tag in the git repo to use it by someone who decided to do the same upgrade later.

0. Backup your phone

Just do it.
Also backup your Authentificator accounts if exist, the upgraded version does not read the old config.

1. Update sources.list

$ cat /etc/apt/sources.list
deb https://repo.pureos.net/pureos crimson main
deb https://repo.pureos.net/pureos crimson-security main
deb https://repo.pureos.net/pureos crimson-updates main
deb [allow-insecure=yes] https://codeberg.org/galilley/librem5-crimson-backports/raw/branch/master/debs ./

2. Run update and dist-upgrade

Yes, it was so simply

$ sudo apt update
$ sudo apt dist-upgrade

At this step be aware about preliminary apt output, especially, about this point:

The following packages have been kept back: …

This is the list of packages with a possibly broken dependencies. So, say N and try to update this packages separately to investigate the reason that prevent upgrade.
bm818-tools has problems with upgrade, but I left it as is. Will fix it later…

3. Downgrade dpkg

I hurried and upgrade dpkg to the latest version which is adopted to support t64 packages that are not supported in Crimson (Bookworm). So, I believe it would be better to return back the original version:

$ sudo apt reinstall dpkg=1.21.22pureos2~cri2 dpkg-dev=1.21.22pureos2~cri2 libdpkg-perl=1.21.22pureos2~cri2

4. Downgrade gcc-14

In the case if you used newer gcc from backports it worth to return back to Crimson’s one (gcc-12), but you need to downgrade some dependencies first:

$ sudo apt reinstall libstdc++6=12.2.0-14+deb12u1 libatomic1=12.2.0-14+deb12u1 libgomp1=12.2.0-14+deb12u1 libgcc-s1=12.2.0-14+deb12u1 libubsan1=12.2.0-14+deb12u1 libitm1=12.2.0-14+deb12u1 liblsan0=12.2.0-14+deb12u1 libcc1-0=12.2.0-14+deb12u1

5. Remove all t64-related packages

Just to clean your installation. You could get the list of such packages as follow:

$ apt list | grep t64

Some packages should be upgraded manually to replace their t64 versions:

sudo apt install libgnome-desktop-3-20 libgnome-bg-4-2 libgnome-desktop-4-2 libgnome-rr-4-2 libhwy1 libpng16-16 libgsound0

6. Reboot your phone

Say bye-bye to Byzantium…

Afterwords

At least I’m able to reboot successfully. I’m not sure that all functionality preserved, so, here I will write about the issues that I found after upgrade:

• chatty crash: $ sudo apt reinstall libpurple0
• no vibro feedback: have no idea yet…
• chromium do not see the camera: go to chrome://flags and enable PipeWire Camera support
• to be continued…

[carlosgonz]

I just wanted if you can purge the Mobian Logo from setting about.

Thanks

[galilley]

Could you explain what exactly did you mean?..

[FranklyFlawless]

@carlosgonz wants the Mobian logo removed from the GNOME Settings app → About tab.

[dos]

Crimson has recently received an updated g-c-c package that does this along with lots of other improvements to make it always fit the screen and not show things that are irrelevant under Phosh, so if you’re using packages from other sources you may be missing out.

[carlosgonz]

Wow, i always trusted on @dos work for Librem 5.

Thanks for Everything dos …and yes you are a Super Hero! too as @austriancoder

[galilley]

The original Crimson’s gnome-control-center has the version of 43.6, but in the backports I have 47.3 from debian trixie. I will look inside the original sources to find the patch to change the logo

[dos]

crimson has version 1:43.6-2~deb12u1pureos2, which is 43.6 with 67 patches applied on top. If you want to update it to 47.3 then you’ll have plenty of rebasing to do first

[galilley]

In fact it works as is… may be not so nice as the patched one
I hope I will have a chance to look inside these patches Fortunately, I stopped to use Byzantium and can concentrate with Crimson.

[Christal]

@galilley

2. Run update and dist-upgrade

Yes, it was so simply

I updated my Librem5 to crimson Stable and try now to user your crimson-backports Branch. I stuck with this howto at Step 2 “Run update and dist-upgrade”.

apt update worked fine. Just running dist-upgrade command failed with “too many connections”.

I try to slow apt down with

Acquire::http::Timeout "10";
Acquire::https::Timeout "10";

In /etc/apt/apt.conf.d/99timeout but it did not help.

[JR-Fi]

That’s the Codeberg problem - it’s got limits. Use --fix-missing at the end of the command and run it a few times to get all the updates (that gets the operation to continue on where it was cut off and continue dl). It’s unclear if Codeberg settings will appreciate a few seconds or a minutes pause between re-running the command but at one point I had to update some 275 packets and needed to run the update command about five times.

[Christal]

Thanks JR-Fi.

I got it done right now before by increase the seconds to 240 instead of 10.

I leave a mark in my comments to adjust the timeout or try the --fix-missing switch in future.

Edit: Reboot did not work if you have luke encrypted discs.

“./librem5-flash-image --stable --variant luks --dist crimson”

And it worked for booting Pureos Crimson stable, and enable my Backup restart it with the new not default luke encryption.

Then i updated the rest. I downgrade/reinstall dpkg as suggested in 3. downgrade dpkg.

I did not “4. Downgrade gcc-14” Since my Version was still gcc-12. And “5. Remove all t64-related packages” shows just some crimson packages with “…int64” or “…bit64” packages with crimson in its name.

So i did not replace libgnome-desktop or libpng16 like in step 5 mentioned.

It not bad, i still reflash crimsion later.

So how can i get around the cryptosetup issue? Should i use autoremove after that apt dist-upgrade was complete? It was mentioned by the shell but i thought ok just reboot first.

If i reboot my Librem5 right now, the LUKS Prompt/Keyboard did not comes up. Push Vol down one time the Boot-Messages is cryptosetup ERROR $Partition-UUID
It retry often but i push my phone off by holding Power button.

Have a nice Sunday!

[JR-Fi]

@Christal

LUKS Prompt/Keyboard did not comes up

This seems to come up a lot with LUKS images and backports. I haven’t done this update procedure, but rather started from clean luks crimson image (then you shouldn’t need to do the steps 3-5, because everything is already crimson from crimson backports) and with that I had to install unl0kr before restarting to get a prompt/keyboard.

[galilley]

Just to be clear, which system you had before upgrade?

If you used Crimson please use this link (the most latest successful case).

Regarding to this thread I considered direct upgrade from Byzantiym backports to Crimson backports. The first one were done in a wrong way, that is because now we should avoid all -t64 packages.

[Christal]

Before i had Byzantiym - Evergreen Phone. Did today a full new flash with the command above. Crimson with “–variant luks” flag.

Crimson backports unofficial

Via Mullvad VPN I managed to finish the download. After running the apt dist-upgrade command I did a reboot. The Librem 5 does not fully boot any more, and gives this errors on a black screen and stops continuing to boot (note that I typed the errors below manually, so there can be spelling errors:) I see around 12 times: Nothing to read on input. Next three times: cryptsetup: ERROR: luks-xxxxxxxxxxxxxx: cryptsetup failed, bad password or options? Then: cryptsetup: ERROR: luks-xxxxxxxxxxx…

Describe the same error i had with cryptosetup.

As recommended i try to

Byzantium backports unofficial

unl0kr 2.0.3 Today I tried to run apt dist-upgrade on my daily driver Byzantium with applied backports and lost luks promt exactly as @JR-Fi reported before. A brief inspection of the problem showed that one of the shared library lost in initrd.img file. To be honestly I’ve wanted to try it for a long time another osk for the boot screen - unl0kr. unl0kr be built without issues and to replace osk-sdl you just need to fix your /etc/crypttab file (replace osk-sdl-keyscript to unl0kr-keyscript) a…

to upgrate to unl0kr to get around the luks issue.

Update to my post before with the Timeout. This did not work too. I Upgrade to a higher value for the Timeouts. But have to run/rerun the apt dist-upgrade with a delay of X Minutes. The Script starts from the later level, like after download 60% before… and go on later.

But i understand that codeberg have to defeat itself again A.I. requesting Bots.

[Christal]

@galilley

The first one were done in a wrong way, that is because now we should avoid all -t64 packages.

Here my

apt list | grep t64
WARNING; apt does not have a stable CLI interface. Use with caution in scripts.

libmath-int64-per/crimson 0.54-2+b1 arm64
r-cran-bit64/crimson 4.0.5-r1 arm64
tnat64/crimson 0.06-1+b1 arm64

I have typed it from the screen. So some typos are likely.

Update: After my working apt dist-upgrade.
Done apt install unl0kr
and change the /etc/crypttab
The osk-sdl-keyscrit to unl0kr-keyscript in that line. But did not worked. I checked before with grep to ensure that the existing files path String from ls - is matching my cryptotab path. But boot did not work.

Update 20250728-01:27 Paris Time:
I just updated the crypttab file and it may not enough to update the initramfs Boot configuration. Just stay for now with my fresh flashed crimson L5 and flatpak updated packages. Even the calculator works after upgrade it to 48.0 instead of 43.0.1 of crimson overlay one.
I may have misunderstand the whole backport system. If you port Crimson apps to gtk3 and Bayzantium Systems it will not work on my phone which i pushed to a higher level of course. But i am stupid on my holiday.

[galilley]

If you used clean Byzantium you should update to Crimson first (if you like to preserve all your settings) and next you can apply Crimson backports. In this case you will have no -t64 packages as well. The stuff like int64, bit64 are completely Ok.

@Christal

I just updated the crypttab file and it may not enough to update the initramfs Boot configuration.

Are you rebuild initrd.img as described in the same post?

@galilley

(just run sudo dpkg-reconfigure linux-image-6.6.0-1-librem5)

@Christal

I may have misunderstand the whole backport system. If you port…

I did not port anything. I just rebuild newer version in the different environment taking into account critical dependencies. Also, I may miss some pureos-specific patches that improve usability in clean Crimson.

[Christal]

I did not. Thank you for wrote this. I think i have some wrong view on your overlay and that fooled me. I did not read the thread before i just followed the two posts because i imagine it understood it.

Thank you for that reconfigure some kernel image suggestion. It would be nice to have it in one post with update and time to be up to date. This Forum loads later post only if some one scroll down the stream or read it in between.

Right now i am fine with the crimson phone. I am exited about the suspend after x Minutes, now i have to Power it one a day instead of twice. And i can run up to date Apps through flatpak. Just Clocks in Gnome 48 will add some Alarm with a wake up. And Clocks from flathup.org will still not work since the crimson overlay only have gnome 43.

Thank you very much galilley, for your afford and support in this thread too.