2026-02-12 15:47:58
🛡️ The project has been externally audited twice – the most recent audit in August 2025 found zero security vulnerabilities
⚠️ Critics argue asterisks reveal password length to 'shoulder surfers' – #Ubuntu marked the bug
report as 'Won't Fix', no rollback planned
⚙️ Disable the new behavior via: Defaults !pwfeedback in the sudoers configuration file
🔄…
g'damit. why is it that even #ubuntu 25.10 still only has #libsodium v1.0.18? 1.0.20 is even getting stale (actually i just checked v1.0.21 is out since two weeks) and all i need is only 1.0.19, breaks my CI/CD pipeline.
TIL this doc is inaccurate https://rocm.docs.amd.com/en/latest/compatibility/compatibility-matrix.html#compatibility-matrix
I can’t even install graphics drivers for RDNA4 on
No progress at all on this #Ubuntu #GDM login failure issue; I can now only use the machine with a PTS console login, then run gnome-session --wayland, and that gives me only basic function, no access to things like User Accounts.
journalctl only gives these two clues, neither of which yields any meaningful Search results (in 2026)
gdm-autologin][]: gkr-pam: no password is available for user
gdm-autologin][]: pam_unix(gdm-autologin:session): session opened for user guest(uid=1005) by guest(uid=0)
gdm-autologin][]: gkr-pam: couldn't unlock the login keyring.
gdm3[841002]: Gdm: GdmDisplay: Session never registered, failing
but console login proves the user has a perfectly good password! GDM3 fails on the auto-login acct, presents the list of users, clicking one lets you enter pw, then bounces back to the acct list screen and any subsequent attempts are shown a non-functional box to enter their pw and a 'back' button that does nothing. 😩
something I didn't need for a Sunday morning: my #Ubuntu 25.10 media machine will no longer login via gdm3 since the last upgrade, I can use a console to run gnome-shell -wayland without issue, but the gdm3 (even re-installed) just returns to the list of users and after the first attempt will no longer offer to enter passwords and hangs.
I did inadvertently leave my keyboard unlocked and two cats in the house left unattended, but it was logged into the guest account, so I doubt they did this 😅
Curiously their snap-edition "firefox -kiosk <url>" now also hangs.
I don't want to spend too much on this: as soon as no.4 son drops by to unlock the broken Win10 and fetch his stuff, I will wipe the thing to install Debian 13 anyway.
this is exceedingly strange and the only obvious symptom is gtk-keystores failing to open, and a search on those can only suggest creating fresh accounts and copying over from all previous, which is far more work than blowing away #Ubuntu and starting over with #Debian13, but this SHOULDN"T be so mysterious and require such drastic measures! All that happened was perhaps an auto-update, but gdm3 rejects the first login then accepts none further, and gnome-shell --wayland will run, but highly crippled, hotkeys disabled, and many programs will not run.
Today's tech puzzle I did not ask for 😞