Running sudo dpkg --configure -a notes that headers for kernel can not be found from their respective folders. So it’s apparently using old kernel (not even previous in this case) and not the latest - which related version files seem to be flashed to boot/initramfs. Otherwise everything seems to update. Reboot brings out the inability to start LUKS prompt - unsurprisingly, noting the kernel version differences… So, re-doing again.
1 Like
But the headers exist (link), but another package seems to be missed…
No, everything must be there. Could you provide the exact output of the sudo dpkg --configure -a command?
1 Like
Not untill I get to re-do the update again
2 Likes
Update shows:
dpkg: error processing archive /temp/apt-dpkg-install-3fS3AR/11-bluez_5.79-1_arm64.dep (--unpack): trying to overwrite '/usr/lib/systemd/user/mpris-proxy.service', which is also in package librem5-base-defaults66pureos1~byz1 and at the end there’s a note that needrestart is being skipped since dpkg had error
And dpkg --configure -a shows:
Setting up linux-image-6.6.0-1-librem5 (6.6.83pureos1~byz1.4) ... dkms: running auto installation service for kernel 6.6.0-1-librem5:Error! echo Your kernel headers for kernel 6.6.0.-1-librem5 cannot be found at /lib/modules/6.6.0-1-librem5/build or /lib/modules/6.6.0-1-librem5/source. You can use the --kernelsourcedir option to tell DKMS where it's located..
I’ve stopped there for now (will be back in an hour or two).
1 Like
That is exactly what I talked about, try to install librem5-base-defaults first, the version must be 66pureos1~byz3.1.
Regarding to the second issue… In fact I have no installed kernel headers package, will try to check. It may also be related to the first issue as far as upgrade has not completed.
2 Likes
Nah, no change with installing that first. Still missing those headers, preventing those installations.
1 Like
But the first issue should disappeared at least and apt dist-upgrade should finished without errors.
1 Like
I just ran sudo apt dist-upgrade when those came up and everything (but the camera) works normally.
On the camera side, none of the the listed commands work for me
2 Likes
try to turn off and on camera kill switch… and let’s continue in another thread 
2 Likes
Still not going the right way. I’ve lost all network connectivity after doing update (while apparently having all the files - including those mentioned at Codeberg). Managed that with the “use old disc image of boot partition” trick to get phone to boot (not fail with LUKS prompt) after update - takes forever to boot now though. No wifi, mobile data nor usb-lan. Curious…
1 Like
What is your state before upgrade? Clean Byzantium or Byzantium with backports? how old?
1 Like
I’ve tried a couple of versions but mostly backported backup from end of January, I think. [Currently taking a break and going to Crimson test image to see what has been happening]
1 Like
Ok. But one more idea to check - just remove linux-headers before upgrade.
2 Likes
Nope. I’m thinking the time between updates has been too long and apt just isn’t able to figure things out. I had similar problems with Crimson testing too, it too didn’t want to boot either on any of the tries and installations after these updates, no matter what I installed before dist-upgrade. Annoying.
1 Like
I’ve just push the commit where I try to fix this issue by removing conflicting file from bluez package rather than librem-base. In fact there is no difference as the files are the same.
1 Like
Phosh 0.46 is here! Wow!
5 Likes
For Gnu Crimson? as i not using Biz anymore as too old.
Thank you 
1 Like
A little bit later… right now I’m trying to upgrade mesa that requires newer rust that requires clang-17 for which I spend the last week because it failed in the last stage several times. 
3 Likes
So, I went back and started from scratch: clean byz flash and so on - trying to chart how currently starting using backports goes.
- After clean byzantium flash an update and reboot - ok
- Then added backports - ok
- Started dist-upgrade - got what @VClaw had first week of January (“Yes do as I Say”), due to librem5-gnome was to be removed (and nautilus as a bonus)… so: “No”
- Then did (just) upgrade - no dangerous requests but got the libtss* related errors (“dpkg: error processing package libtss2-esys-3.0.2-0:arm64 (–configure): dependency problems - leaving unconfigured” AND “dpkg: dependency problems prevent configuration of libtss2-tcti-mssim0:arm64: libtss2-tcti-mssim0:arm64 depends on tpm-udev; however: Package tpm-udev is not configured yet. libtss2-tcti-mssim0:arm64 depends on libtss2-mu0 (>= 3.0.1)” and then a list consisting of tpm-udev and libtss2-* x7) [allowed for automatic service restarts]
- Then did the dist-upgrade - took the chance and commanded (in loud booming voice) “Do as I say!” [L5 did not immediately catch fire], which went through with errors about 49-gnome-console and network-manager being de-configured
- Then followed that with sudo apt --fix-broken install - which reinstalled gnome-console and did a lot of configuring to network stuff… and no errors
AND just to be on the same side, one more update & dist-upgrade - which found a few more to install … but no errors, but some 21 packages were kept back (chatty, eog, evolution-data-server gir1.2-gnomedesktop-3.0 gnome-calendar gnome-control-center gnome-controlcenter-data gnome-desktop3-data gnome-initial-setup gnome-session-bin gnome-settings-daemon gnome-settings-daemon-common gnome-weather libpurple-bin phoc phosh phosh-tour pidgin-data purple-xmpp-carbons purple-xmpp-htt-upload sqeekboard - nothing reeeeeaally important, right) - Tried to install the 21 missing but that doesn’t go through as libdisplay-info1 is not installable, has not installation candidate, but is a requirement for libwlroots-0.18
… and that’s where I’m at the moment with trying to get backports installed. Any chance that libdisply-info1 is something that can be added to backports? Could it be the culprit that prevents a straight up installation or is this just a symptom of too many steps and telling system to do silly things when I should know better? I dare not reboot and keep it powered if by chance this is still fixable - so I wait.
2 Likes
Oh… I’v push libdisplay-info2 and believed that it replaced libdisplay-info1 but it is wrong. The last one still required. I’ve returned it back, please try again.
2 Likes