Tootfinder

Anyone have thoughts on dropping Ubuntu 22.04 support in the ngscopeclient CI build moving forward since 26.04 is coming out very soon?
We won't be actively going out of our way to break 22.04 (i.e. adding a dependency not available there) but it will no longer be routinely tested.
The main reason is some Vulkan packaging issues that require special handling for 22.10 and older, the CI scripts will be a lot simpler if I can just forget that (the documentation mentions the nec…

Wow, just managed to fix a problem that has hounded me the last few days: after a reboot, one of my home servers (Ubuntu 24.04, 2 NVMEs with XFS filesystems) couldn't find its RAID 1 boot volume, claiming 'duplicate MD device names in conf file were found'. Gulp. Managed to find the solution here:

@…

Even old x86 Apple laptops run Linux poorly, at least without a lot of tinkering.
I have a MBP 14,3 with miserable WiFi and no sound on Ubuntu 24.04.
Don't buy Apple hardware.

https://www.codemacs.com/other/anything/my-review-of-ubuntu-touch-as-a-replacement-for-iphone-or-android.0229091.htm
> „I’ve been working in IT for a long time, so the idea of having a full terminal in my pock…

I'm struggling with getting a functional environment which includes the following:
-Ubububu 26.04
-Kernel 6.19
-Nvidia 580.xx drivers
-CUDA 13.0.x
Until I get at least the last three of those things in one place on a recent Ubuntu release, I can't try out nvidia_greenboost :-/

I don't know who needs to see this, but I've had some issues with a pre-26.04 Ubuntu, which were (apparently) fixed with the following:
echo "@{run}/systemd/journal/dev-log wm," > /etc/apparmor.d/local/unix-chkpwd

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. 😩