I came back to Linux after too long. Ubuntu was my jam of choice back in the day. Loved the Gnome focus on a pretty desktop... couldn't wait to see all the progress in the last 10 years. It's free for real. No Redhat BS. Love it... only within 2 days, the list of broken shit was long. So long was the list, I couldn't remember it all. Claude and I made great progress on some things. Others, require forking Gnome and Wayland which is way farther than I want to go to get a computer that actually works like Ubuntu used to work in 2007.
- Graphics drivers were not installed correctly - fixed by manually installing nvidia drivers.
- No way to extend a gnome control panel to add missing accessibility features!
- Netflix - Fixed by disabling accelloration and making my browser slower! Booo.
- Uninstalling software from the app center - not fixed - removed snaps because It tried to backup 90 GB of crap to uninstall steam!
- Clicklock - Fixed here: https://github.com/Greg-Boggs/ClickLock
- Push to talk on Discord - Fixed here: https://github.com/Greg-Boggs/ptt-mic
- Suspend bricks - fixed. Details below.
- Sleep locks the computer and logs me out of gmail in Chromium - not fixed. Switched to Chrome.
- Session resume - No fixed. Force suspends instead because suspend resumes.
- Apt itself stopped working. The Claude Desktop .deb added a second apt source with a conflicting Signed-By, so every apt command failed with "list of sources could not be read." Fixed by sudo rm /etc/apt/sources.list.d/claude-desktop.sources.
- No "Ubuntu on Xorg" login option anymore. GNOME 50 (26.04) deleted the Xorg session upstream. That's why the Discord/Foxhole keybind stuff had no easy escape hatch. Not fixable, it's gone.
- Changing keyboard options needs a full logout/login. Remapping Caps Lock via xkb-options didn't take until re-login because mutter won't reload the keymap live. And caps:none makes the key invisible to games entirely.
- gnome-keyring never auto-unlocks under autologin. No TPM, no disk encryption on this box, so there's no clean way to auto-unlock a password-protected keyring without a login password. This is the real reason #7 was so sticky, separate from the broken Chromium build.
The fix for suspend:
Swap the open kernel module for the closed one. The open module was corrupting VRAM on resume.
sudo apt install nvidia-driver-610
Added mem_sleep_default=deep to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then sudo update-grub. This forces real S3 sleep instead of s2idle. s2idle was doing a userspace freeze that gnome-shell refused, so suspend aborted and wedged the GPU.
sudo sed -i 's/\bquiet splash\b/quiet splash mem_sleep_default=deep/' /etc/default/grub
sudo update-grub
Result: clean PM: suspend entry (deep) and resume, no freeze failures, no NVRM errors.
Night suspend: Nothing scheduled. GNOME's built-in idle auto-suspend does it: 30 minutes with no input and nothing playing or holding a wake lock, and it suspends. Adjust with gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout or Settings, Power, Automatic Suspend.