You are not logged in.
Hi,
I installed Arch Linux on my ThinkPad P71 two days ago and everything is working like a charm. The only problem I currently have is that I cannot shut down or reboot the machine from GNOME.
% sudo poweroffor
% sudo rebootwork without problems. I also can log out normally.
When trying to shut down or reboot the machine with
% systemctl poweroffor
% systemctl rebootI get the error message
Failed to power off system via logind: There's already a shutdown or sleep operation in progressThis also happens if it is the first thing I do after starting the machine.
journalctl shows these errors:
Mär 18 13:08:09 sledgehammer gnome-session-binary[998]: Unrecoverable failure in required component org.gnome.Shell.desktop
Mär 18 13:08:35 sledgehammer gdm-password][1278]: gkr-pam: unable to locate daemon control file
Mär 18 13:08:41 sledgehammer systemd[1283]: Failed to start Application launched by gnome-session-binary.It also appears that my $XDG_SESSION_ID is undefined which seems odd.
I already read about a problem where others were also unable to shut down or restart from GNOME due to a bug in gnome-session-restart-dbus.service - this issue has of course been fixed already in the current version.
Some reported that they had a problem with the module acpi_thinkpad - blacklisting it did not help in my case though.
Could this be related to the NVIDIA binary driver? It was mentioned somewhere that it might be a problem.
I am happy to provide further information if required. Thanks in advance!
Thomas
Last edited by volatile void (2021-03-19 10:46:43)
Offline
How do you start nome? If xinitrc is involved, see the links in my signature… ![]()
Offline
How do you start nome? If xinitrc is involved, see the links in my signature…
I am using GDM, so .xinitrc is not involved. ![]()
The exact same setup was by the way working properly in a VirtualBox VM. Forgot to mention this in the original post.
Thomas
Offline
The thing that would concern me is
It also appears that my $XDG_SESSION_ID is undefined which seems odd.
Can you
loginctl session-statusPlease post a complete system journal, "gnome-session-binary[998]: Unrecoverable failure in required component org.gnome.Shell.desktop" means that something™ likely (crashes and) inhibits the session, but we lack the context.
sudo journalctl -b | curl -F 'f:1=<-' ix.ioOffline
loginctl session-status
4 - thomas (1000)
Since: Thu 2021-03-18 23:32:49 CET; 5min ago
Leader: 1102 (gdm-session-wor)
Seat: seat0; vc2
TTY: tty2
Service: gdm-password; type x11; class user
State: active
Unit: session-4.scope
├─1102 gdm-session-worker [pam/gdm-password]
├─1118 /usr/bin/gnome-keyring-daemon --daemonize --login
├─1122 /usr/lib/gdm-x-session --run-script /usr/bin/gnome-session
├─1124 /usr/lib/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
└─1132 /usr/lib/gnome-session-binary
Mär 18 23:36:43 sledgehammer /usr/lib/gdm-x-session[1124]: (--) NVIDIA(GPU-0): DFP-5: 960.0 MHz maximum pixel clock
Mär 18 23:36:43 sledgehammer /usr/lib/gdm-x-session[1124]: (--) NVIDIA(GPU-0):
Mär 18 23:36:43 sledgehammer /usr/lib/gdm-x-session[1124]: (--) NVIDIA(GPU-0): DFP-6: disconnected
Mär 18 23:36:43 sledgehammer /usr/lib/gdm-x-session[1124]: (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
Mär 18 23:36:43 sledgehammer /usr/lib/gdm-x-session[1124]: (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
Mär 18 23:36:43 sledgehammer /usr/lib/gdm-x-session[1124]: (--) NVIDIA(GPU-0):
Mär 18 23:37:27 sledgehammer /usr/lib/gdm-x-session[1124]: (EE) client bug: timer event6 debounce: scheduled expiry is in the past (-8ms), your system is too slow
Mär 18 23:37:27 sledgehammer /usr/lib/gdm-x-session[1124]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-22ms), your system is too slow
Mär 18 23:37:32 sledgehammer /usr/lib/gdm-x-session[1124]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-4ms), your system is too slow
Mär 18 23:37:42 sledgehammer /usr/lib/gdm-x-session[1124]: (EE) event6 - Logitech MX Master 3: client bug: event processing lagging behind by 12ms, your system is too slowsudo journalctl -b | curl -F 'f:1=<-' ix.io
Thanks for your support so far!
Thomas
Offline
Mär 18 23:32:20 sledgehammer gnome-session[823]: gnome-session-binary[823]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mär 18 23:32:20 sledgehammer gnome-session-binary[823]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mär 18 23:32:20 sledgehammer gnome-session[823]: gnome-session-binary[823]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mär 18 23:32:20 sledgehammer gnome-session-binary[823]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mär 18 23:32:20 sledgehammer gnome-session-binary[823]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Mär 18 23:32:20 sledgehammer gnome-session[823]: gnome-session-binary[823]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
…
Mär 18 23:32:25 sledgehammer /usr/lib/gdm-x-session[855]: dbus-daemon[855]: [session uid=120 pid=855] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Mär 18 23:32:25 sledgehammer gsd-sharing[942]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Mär 18 23:32:25 sledgehammer gsd-sharing[942]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Mär 18 23:32:25 sledgehammer gsd-sharing[942]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1Here's your problem.
Not sure, but looks close enough to a race condition because you're trying to start a wayland session on nvidia and especially the GPU is also late.
Mär 18 23:32:20 sledgehammer gnome-shell[831]: Failed to open gpu '/dev/dri/card0': Failed to activate universal planes: Die Operation ist nicht erlaubt
Mär 18 23:32:20 sledgehammer gnome-shell[831]: Failed to create backend: No GPUs found
Mär 18 23:32:20 sledgehammer gnome-session[823]: gnome-session-binary[823]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mär 18 23:32:20 sledgehammer gnome-session-binary[823]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mär 18 23:32:20 sledgehammer gnome-session-binary[823]: Unrecoverable failure in required component org.gnome.Shell.desktophttps://wiki.archlinux.org/index.php/GD … rg_backend
https://wiki.archlinux.org/index.php/NV … de_setting
https://wiki.archlinux.org/index.php/Ke … _KMS_start
Offline
You probably will not believe what the issue behind this problem was. ![]()
Added nvidia, nvidia_modeset, nvidia_uvm and nvidia_drm to the initramfs MODULES and rebuilt the image: No difference.
Added nvidia-drm.modeset=1 to the kernel boot parameters: Shutting down was possible once, then same problem as before.
Every time it was not possible to shut down or reboot, the machine entered a strange "reset" state at least once before GDM was visible. Sometimes it also "reset" when loading GNOME. This means that the power LED actually went out and the Blu-ray drive spun up. journalctl even showed that shutdown events were detected.
The laptop is docked in a 230W ThinkPad Workstation Dock. My display was attached to the dock via DisplayPort (as HDMI only supports 4K@30Hz).
Long story short: Undocked the laptop, started it, no "resets", shutting down and rebooting is possible. Put it back in the dock, attached the display directly to the machine via Thunderbolt - all is well.
Looks like the graphics pass-through of the dock is a bit broken...
Thomas
Offline