Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrade my pi 5 system to Trixie
* What exactly did you do (or not do) that was effective (or
ineffective)?
I have tried all the common ways to address and nothing has fixeded the issue. Specfically, I tried:
Identified Tainted: unmerged-bin in systemctl status as the root cause of post-upgrade issues
Installed usrmerge package to attempt automatic filesystem merge
Installed usr-is-merged package
Confirmed /bin, /sbin, /lib were already correct symlinks
Discovered /usr/sbin was still a real directory instead of a symlink to bin
Ran conflict check — found 4 conflicting symlinks: ip, lsmod, rpcinfo, tor
Removed the 4 conflicting symlinks from /usr/sbin
Reinstalled usrmerge — still didn't convert /usr/sbin
Manually moved all unique binaries from /usr/sbin to /usr/bin, removed duplicates, replaced directory with symlink
Rebooted — systemctl status taint resolved
Installed lshw to help GNOME read CPU info
Identified snap packages as likely cause of Disk Capacity Unknown
Removed all snap packages and purged snapd entirely
Rebooted — disk still showed Unknown
Confirmed udisks2 drive object reports Size: 0 and empty ConnectionBus for the NVMe
Added unstable repository with pinning to trixie as default
Upgraded udisks2 to 2.11.1-1 from unstable
Restarted udisks2 — drive object still reports Size: 0
Cleaned up unstable repository
* What was the outcome of this action?
The bug persists.
* What outcome did you expect instead?
I had thought this would solve the issue (which is admittedly primarily cosmetic), but it did not.
*** End of the template - remove these template lines ***