Re: Reboot hangs on Debian 11: gnome-session-manager@gnome.service: Failed with result 'timeout'
On Jo, 09 dec 21, 21:33:29, Tobias Boesch wrote: > Hello Debian Team, > > I would like to report a bug at Debian, but I don't know which package > I should use for the report. Please help me categorise this problem. > > I run Debian 11 with systemd (247.3-6) and I experience services > timeouts after inatalling nVidia drivers from the debian repos (not the > nVidia installer) very often (details follow). > I think Debian uses gnome-session in version 3.38. > (https://packages.debian.org/bullseye/gnome-session) > When nVidia is uninstalled it seems these delays are gone (I cannot > test for a whole day but I tested shutdowns/reboots a few times) It's pretty clear the nvidia package is somehow involved, so it's probably fine to start with a report against it. The Maintainer will reassign as needed in case it turns out it isn't the cause. Please do make sure you are using reportbug with the correct package name. This will ensure the report is sent to the correct place and will include possibly very important information about the package and your system. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Reboot hangs on Debian 11: gnome-session-manager@gnome.service: Failed with result 'timeout'
Hello Debian Team, I would like to report a bug at Debian, but I don't know which package I should use for the report. Please help me categorise this problem. I run Debian 11 with systemd (247.3-6) and I experience services timeouts after inatalling nVidia drivers from the debian repos (not the nVidia installer) very often (details follow). I think Debian uses gnome-session in version 3.38. (https://packages.debian.org/bullseye/gnome-session) When nVidia is uninstalled it seems these delays are gone (I cannot test for a whole day but I tested shutdowns/reboots a few times) The message shown when delaying ocurrs is "A stop job is running for user manager for UID 1001" (1001 - a guest user) journalctl shows a lot as usual, but I think this part is related: " Dez 07 20:28:34 tobias-pc systemd[798]: pulseaudio.service: Succeeded. Dez 07 20:28:34 tobias-pc systemd[798]: Stopped Sound Service. Dez 07 20:28:34 tobias-pc tracker-miner-fs[840]: OK Dez 07 20:28:34 tobias-pc systemd[798]: tracker-miner-fs.service: Succeeded. Dez 07 20:28:34 tobias-pc systemd[798]: Stopped Tracker file system data miner. Dez 07 20:28:34 tobias-pc systemd[798]: tracker-miner-fs.service: Consumed 2.214s CPU time. Dez 07 20:30:04 tobias-pc systemd[798]: gnome-session-manager@gnome.service: State 'final-sigterm' timed out. Killing. Dez 07 20:30:04 tobias-pc systemd[798]: gnome-session-manager@gnome.service: Killing process 1535 (kodi.bin) with signal SIGKILL. Dez 07 20:30:04 tobias-pc systemd[798]: gnome-session-manager@gnome.service: Killing process 1663 (Lirc) with signal SIGKILL. Dez 07 20:30:04 tobias-pc systemd[798]: gnome-session-manager@gnome.service: Failed with result 'timeout'. Dez 07 20:30:04 tobias-pc systemd[798]: Stopped GNOME Session Manager (session: gnome). Dez 07 20:30:04 tobias-pc systemd[798]: gnome-session-manager@gnome.service: Triggering OnFailure= dependencies. Dez 07 20:30:04 tobias-pc systemd[798]: gnome-session-manager@gnome.service: Consumed 1min 35.212s CPU time. Dez 07 20:30:04 tobias-pc systemd[798]: Removed slice app- gnome\x2dsession\x2dmanager.slice. Dez 07 20:30:04 tobias-pc systemd[798]: app- gnome\x2dsession\x2dmanager.slice: Consumed 1min 35.212s CPU time. Dez 07 20:30:04 tobias-pc systemd[798]: Stopped target Tasks to be run before GNOME Session starts. Dez 07 20:30:04 tobias-pc systemd[798]: Stopped target Session services which should run early before the graphical session is brought up. Dez 07 20:30:04 tobias-pc systemd[798]: Stopped target Basic System. Dez 07 20:30:04 tobias-pc systemd[798]: Reached target Shutdown running GNOME Session. Dez 07 20:30:04 tobias-pc systemd[798]: Stopped target Paths. " See "tobias-pc systemd[795]: gnome-session-manager@gnome.service: Failed with result 'timeout'." The delay happens nearly everytime when I reboot from Kodi (use reboot command in Kodi). When rebooting from GNOME menu the delay is not always there. Shutting down from Kodi also works fine mostly in contrast to a reboot. I saw this delay also happen when only lutris was left open before shutting down (so kodi was closed) or rebooting from GNOME menu. So it is not Kodi alone that triggers it. Again: With nouveau drivers it seems completely gone. I cannot determine to which package the issue should be related to by myself and thats why I ask for help. I already asked at gnome-session in two issues: - https://gitlab.gnome.org/GNOME/gnome-session/-/issues/74#note_1327456 - https://gitlab.gnome.org/GNOME/gnome-session/-/issues/102 They do not fix it since it is in a version that is too old. I hope there is enough information provided - if you need more let me know. Best wishes to you all. Tobias