You are not logged in.
Pages: 1
Topic closed
Hello, I have this problem now every time I turn off or reboot my laptop, and I have the same problem on my 3 laptops and also included some VMs. I tried LTS and the latest kernel. The only thing that they have in common is Gnome desktop, but I don't know how to troubleshoot properly this problem:
> Journalctl -p 3 -xb
-- Journal begins at Fri 2020-08-07 16:23:38 WEST, ends at Wed 2020-12-09 00:12:54 WET. --
Dec 08 23:57:55 aspire-e5-573 kernel: dw_dmac INTL9C60:00: Missing DT data
Dec 08 23:57:56 aspire-e5-573 kernel: proc: Bad value for 'hidepid'
Dec 08 23:57:56 aspire-e5-573 kernel: proc: Bad value for 'hidepid'
Dec 08 23:58:02 aspire-e5-573 kernel: proc: Bad value for 'hidepid'
Dec 08 23:58:13 aspire-e5-573 gdm-password][794]: gkr-pam: unable to locate daemon control file
Dec 08 23:58:16 aspire-e5-573 pulseaudio[923]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus>
Dec 08 23:58:24 aspire-e5-573 kernel: proc: Bad value for 'hidepid'
Dec 08 23:58:58 aspire-e5-573 kernel: proc: Bad value for 'hidepid'
Dec 09 00:05:39 aspire-e5-573 sudo[2300]: pam_unix(sudo:auth): conversation failed
Dec 09 00:05:39 aspire-e5-573 sudo[2300]: pam_unix(sudo:auth): auth could not identify password for [aaron]
> systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
SOLUTION:
Ok, I solved the problem with this:
https://bbs.archlinux.org/viewtopic.php?id=261369
https://gitlab.gnome.org/GNOME/gnome-se … ote_978036
It's a problem related to Gnome and the jobs under the user 1000, you can check that with:
> sudo systemctl --user list-jobs
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined
> sudo systemctl --user list-sockets
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined
To fix the problem is by editing the file: /usr/lib/systemd/user/gnome-session-restart-dbus.service and adding Slice=-.slice at the end of the [Service] section:
...
[Service]
Type=notify
ExecStart=/usr/lib/gnome-session-ctl --restart-dbus
Slice=-.slice
I hope this will help others, Thanks
Last edited by aaronglz23 (2020-12-09 01:11:03)
Offline
This bug has been posted a few times around here, e.g. https://bbs.archlinux.org/viewtopic.php?id=261530.
Offline
It is solved now, I edited the post with the solution. Thanks
SOLUTION: https://bbs.archlinux.org/viewtopic.php?id=261556
Last edited by aaronglz23 (2020-12-09 01:12:01)
Offline
Hi, thanks @aaronglz23 I confim it has worked fine for me too!
Edit: it worked the first time now I get always the delay on shutdown
Last edited by toketin (2020-12-25 11:22:15)
Offline
Hello !
Thx for pointing out the issue and proposing a fix @aaronglz23
however for me adding the line at the end of the [Service] section does not fix the problem (i still have the error msg at shutdown for about 3-4 seconds).
Also the line was already there after inspecting /usr/lib/systemd/user/gnome-session-restart-dbus.service
I'm on 5.15.8-arch1-1 and gnome 41.1-1 something (according to the current version of the gnome package group)
For me this problem arose quite recently like 1 week ago or so.
when i run
sudo systemctl --user list-jobs
I get the following output:
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
Any tips on how I can debug this properly ?
Last edited by darsonis (2021-12-15 16:56:22)
Offline
I have also still the problem. But for me
sudo systemctl --user list-jobs
prints out
Failed to connect to bus: No medium found
Offline
I have also still the problem. But for me
sudo systemctl --user list-jobs
prints out
Failed to connect to bus: No medium found
I use plasma.
I have similar problem.
Offline
Make a new thread after reproduction and post the outputs of
sudo journalctl -b-1
after rebooting from a failed attempt.
Closing this old solved thread.
Offline
Pages: 1
Topic closed