Interesting. For some reason they are in my newly installable list (see the earlier lists with removed files) and were marked for installation with Synaptic too.
Again, they might be just a red herring in this. Hopefully the current experiment will tell… something.
edit: Some error “tpm-udev: installed tpm-udev package post installation script subprocess returned error exit status 1”
… but an intermediate result is that now dist-upgrade only has 93 to be upgraded. Continuing with that… [except Codeberg pages are down again]
Aaaand, nope. As L5 rebooted after crashing, once again, no LUKS prompt and I’m going to flash again later (need to take a walk now).
So,try #34566489. This time a clean byz flash (instead of using copies of my actual disc image backups) that I updated first. The backportsu pgrade went ok - network stayed, kbd was automatically installed etc. Still got the same libtss errors, but at least the install went through after doing dist-upgrade again. Noticed some updated bits here and there. But, even after all seemed well, after reboot the luks prompt failed again. So, no luck. Will have to return to this tomorrow. It’s getting a bit annoying.
Ok… The main thing I love in Linux (GNU/Linux of course, sorry ) is that you can do almost everything by your hands using a hammer and a strong word (sorry, do not know how to say it correctly in English).
So, @JR-Fi , your reason is the tpm-udev post install script. It is located here:
/var/lib/dpkg/info/tpm-udev.postinst
It should create tss group and the same user if they are not already there (but must be there in fresh Byzantium). You could find exact commands (like addgroup, adduser and chown) inside. What you need is to run these command by yourself (with sudo prefix) before upgrade. After that we will achieve the next round with upgrading your phone
Nope. the tss (at the latest try) seemed to resolve with simple dpkg --cofigure -a and all the suggested packages were installed. I’ve ran out of things to try. Only thing showing is that there is no LUKS prompt (text that shows intermittenly seems to indicate that there is some automatic input that fails to open LUKS as it reaches the limit for tries, before it goes blank). There is no prompt, no input possibility (even tried external methods) and no way to get any feedback, so I’m stumped. I can’t figure what in the apt process would or could effect those parts that startup before system is even started. Does the backport update have something that messes with boot?
May have to wait for crimson and/or crimson backports.
But I have both on the mmc and sd-card and everything works pretty good… I think a problem could be in initrd generation that may be blocked by tpm-udev, but it is really difficult to say without logs.
Crimson backports are in the progress, but they need more time that is really limited for me…
Some notes so far: after a few false tries, I’ve managed to do a suitable partial upgrade (sans those tss-related files), and when that failed the boot again, I used an earlier boot partition image that I wrote on top of the created failing one. At least most of my byz is now backported - looks nice (gain, thanks @galilley). I still have a group of 50 various files to upgrade (doing it a few at a time - synaptic has helped [works from terminal via sudo -E synaptic]) but so far so good - any setbacks and I can always return to previous working state with disc images. Still unclear why this happened, though (haven’t looked into it that much).
Hi, so I have installed everything awhile ago after many tries. Question to ask, should I comment out the repo in the source.list? Or keep it there for apt update?
Also, is there anyway to disable the transparent background on phosh in this backports? Thanks
The transparent background is very annoying and visual disturbing when we do the multi tasking on the phosh. The pmos version phone is also the lastest without the transparent background.