Having used both, I have to say that 22.04 LTS is much worse than 20.04 LTS.
Every once in a while, Canonical rams in the anal probe and breaks something in the middle of the night. This is called...
Type: Posts; User: John Nagle; Keyword(s):
Having used both, I have to say that 22.04 LTS is much worse than 20.04 LTS.
Every once in a while, Canonical rams in the anal probe and breaks something in the middle of the night. This is called...
NVidia bug, or Ubuntu systemd configuration bug? Report to NVidia or Ubuntu?
You just know each will blame the other.
> What did you do different, did you use my suggestion, or just happenstance?
I didn't do anything to change the system state.
So far, this has happened twice in the last two weeks. No idea...
Didn't happen last night. Here's the log in the attachment above, with some annotation. Note in ==> NOTE <==
Sep 29 06:54:48 user-desktop systemd[1]: Starting Daily apt upgrade and clean...
Hm. Despite that disabling, NVidia Hibernate did, apparently, try to hibernate.
[Mounting, checking, etc. of internal drives]
Identity=unix-group:admin;unix-group:sudo...
More years-old discussion on this: https://askubuntu.com/questions/1345073/suspend-not-working-properly-cannot-wake-up-on-ubuntu-20-04-with-nvidia
There are hacks there to work around the problem,...
A somewhat similar problem was reported back in 2021 on NVidia forums....
systemd-boot not installed in ESP.
System:
Firmware: n/a (n/a)
Secure Boot: disabled
Setup Mode: setup
TPM2 Support: no
Boot into FW: supported
Current Boot Loader:
...
This is new. Twice now, I've been unable to log into a desktop system that is not turned off or hibernating, but is only in "lock" mode. Nothing I can do
with the keyboard will wake up the system. ...
Running 22.04.02 LTS. Auto-update just ran itself. Complained that "Not all updates could be installed", with, as usual, no useful info.
Symantic package manager reports 0 open packages. And "The...
OK. Created new bug report, with all the details: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020249
Commenting out all those tests for not using Wayland is the big-hammer approach. I'd...
Turns out this is a known Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929
It was supposedly fixed, but comments after the fix indicate it is still broken, at least in LTS...
Well, yes, that hack might force Wayland. Or break something.
But why is Wayland disabled? None of the tests that take control to "gdm_disable_wayland" should be true.
# disable Wayland if...
https://i.ibb.co/cNHWVht/displaydriver.png
And this is the driver in use. 470, the recommended driver, supplied by the Ubuntu distro.
Looks like "nvidia-drm" is required for Wayland on Nvidia....
$ cat /usr/lib/udev/rules.d/61-gdm.rules
# identify virtio graphics cards to find passthrough setups
SUBSYSTEM!="virtio", GOTO="gdm_virtio_device_end"
ACTION!="add", GOTO="gdm_virtio_device_end"...
$ echo $XDG_SESSION_TYPE
x11
$ ls -l /usr/share/xsessions/ | awk '{print $9}' | grep -v '^\.'
ubuntu.desktop
ubuntu-xorg.desktop
unity.desktop
$ gnome-shell --version
GNOME Shell 42.5
https://i.ibb.co/w4b1ngz/unityselection.png
Those are the available options. No Wayland option.
https://i.ibb.co/RHvrTsX/ubuntudetails.png
System details.
Recheck:
> echo $XDG_SESSION_TYPE...
I don't get the Wayland option at login on 22.04 LTS. Just "Ubuntu" or "Unity". This is on a machine with an NVidia 640. NVidia drivers is 470 ("proprietary, tested", "This device is using the...
So I look at the key situation:
> apt-key list
...
/etc/apt/trusted.gpg.d/lutris-team_ubuntu_lutris.gpg
----------------------------------------------------
pub rsa4096 2019-03-23 [SC]
...
So Software Updater is demanding (the message is stronger than usual) that I upgrade, on Ubuntu 20.04.LTS
Then I get "Failed to download repository information - check your Internet connection"....
Found out what's happening. IDrive for Linux, the commercial backup software, is causing this.
More info. If inotify runs out of resources, it sets the error code ENOSPC. Ref:...
Still getting those messages after a reboot.
Checking obvious stuff:
* Synaptic package manager says 0 packages broken.
* Other programs now running OK.
The errors above happened right...
Program (a Rust compile) aborted, and the terminal window closed. Checked syslog:
Errors in syslog:
Nov 4 11:35:50 Nagle-LTS systemd[2249]: app-gnome-synaptic-4759.scope: Failed to add control...
Found a workaround. Apparently someone enabled Ultra Fast Boot. With that on, you have no options at boot unless boot fails. But once Windows is up, if you do a Windows Restart, you can get boot...