[Solved] System can't reboot or poweroff because of Xorg

Superjolly002 · 2020-02-20 21:25:27

Hi everyone,

then after the penultimate update of KDE my system didn't poweroff/reboot because of kwin_x11.
Anyway with the last update it seems resolved, but now my system doesn't poweroff/reboot because of Xorg, this is the log of Xorg.

For information, I'm using Arch up-to-date with linux 5.4.20-1-lts.

Someone can help me?
Thanks to everyone.

Last edited by Superjolly002 (2020-02-29 15:33:45)

seth · 2020-02-20 22:02:13

The backtrace looks like nvidia, but the log complains about the "Holtek USB Gaming Mouse" (is that device also the cause for the HID quirks?)
The stall of either could cause the other to yell errors (debouncing, inability to remove the kernel module)

The easy isolation test would be to replace the mouse w/ a less fancy one.

Superjolly002 · 2020-02-21 11:42:08

To understand if it really was the mouse, I tried to poweroff without connect the mouse to the pc and it poweroff, after a long time but it poweroff.
This mouse is too comfortable for me and I want avoid change the mouse or disconnect it to the pc every time I have to poweroff.

There is an alternative solution than change mouse?

Last edited by Superjolly002 (2020-02-21 11:42:18)

seth · 2020-02-21 12:07:13

I'd like you to boot and run and power-off the system w/o that mouse. And if it still takes "a long time", post updated logs.
First step is to figure what's actually the cause, next step will be to figure how to deal with that.

Superjolly002 · 2020-02-21 14:05:55

I think I just was lucky, this time it redone the issue with kwin_x11...
Anyway there are the logs of errors.log, everything.log and last -x.

seth · 2020-02-22 09:32:21

Can you please post the complete system journal from that boot?

Superjolly002 · 2020-02-22 12:04:08

I had to split the output in 3 parts because of pastebin.com doesn't paste file that exceed 512KB, sorry for this drawback.
journalctl1, journalctl2 and journalctl3

seth · 2020-02-22 15:41:17

This looks super-suspicious:

feb 21 23:32:53 pc-arch org_kde_powerdevil[1065]: powerdevil: Releasing inhibition with cookie  393
feb 21 23:32:53 pc-arch org_kde_powerdevil[1065]: powerdevil: Restoring DPMS features after inhibition release
feb 21 23:32:53 pc-arch org_kde_powerdevil[1065]: powerdevil: Scheduling inhibition from ":1.20" "My SDL application" with cookie 394 and reason "Playing a game"
feb 21 23:32:53 pc-arch org_kde_powerdevil[1065]: powerdevil: Can't contact ck
feb 21 23:32:58 pc-arch org_kde_powerdevil[1065]: powerdevil: Enforcing inhibition from ":1.20" "My SDL application" with cookie 394 and reason "Playing a game"
feb 21 23:32:58 pc-arch org_kde_powerdevil[1065]: powerdevil: Added change screen settings
feb 21 23:32:58 pc-arch org_kde_powerdevil[1065]: powerdevil: Added interrupt session
feb 21 23:32:58 pc-arch org_kde_powerdevil[1065]: powerdevil: Disabling DPMS due to inhibition
feb 21 23:32:58 pc-arch org_kde_powerdevil[1065]: powerdevil: Can't contact ck

The session doesn't end, sddm later receives a sigterm, kills X11, several processes (incl. actually kwin_x11) wet themselves and you get a super-unclean shutdown.

Why is "my sdl application" "playing a game"?

Superjolly002 · 2020-02-22 16:33:16

Why is "my sdl application" "playing a game"?

I have no idea what do it want to refer "playing game"...
Could steam be the problem? But I don't think so

seth · 2020-02-22 17:30:48

Google says that this is steam (very professional of them to use such a generic term… I thought that was some hobby project you were working on. tsss)
So ensure to not start that (boot, login, shutdown => works?) to see whether it's (along maybe powerdevil) the culprit.

Superjolly002 · 2020-02-23 08:34:10

I tried to uninstall steam and seems that solved problem with powerdevil, anyway it doesn't poweroff.
This is the log

seth · 2020-02-23 12:26:23

feb 23 09:25:43 pc-arch systemd-logind[508]: New session 2 of user antonio.
…
feb 23 09:25:43 pc-arch systemd[1]: Started User Manager for UID 1000.
feb 23 09:25:43 pc-arch systemd[1]: Started Session 2 of user antonio
…
feb 23 09:25:53 pc-arch systemd[1]: Stopping User Manager for UID 974...
feb 23 09:25:53 pc-arch systemd[575]: Stopped target Main User Target.
feb 23 09:25:53 pc-arch systemd[575]: Stopping D-Bus User Message Bus...
feb 23 09:25:53 pc-arch systemd[575]: dbus.service: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Stopped D-Bus User Message Bus.
feb 23 09:25:53 pc-arch systemd[575]: Stopped target Basic System.
feb 23 09:25:53 pc-arch systemd[575]: Stopped target Paths.
feb 23 09:25:53 pc-arch systemd[575]: Stopped target Sockets.
feb 23 09:25:53 pc-arch systemd[575]: Stopped target Timers.
feb 23 09:25:53 pc-arch systemd[575]: dbus.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed D-Bus User Message Bus Socket.
feb 23 09:25:53 pc-arch systemd[575]: dirmngr.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed GnuPG network certificate management daemon.
feb 23 09:25:53 pc-arch systemd[575]: gpg-agent-browser.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
feb 23 09:25:53 pc-arch systemd[575]: gpg-agent-extra.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
feb 23 09:25:53 pc-arch systemd[575]: gpg-agent-ssh.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed GnuPG cryptographic agent (ssh-agent emulation).
feb 23 09:25:53 pc-arch systemd[575]: gpg-agent.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed GnuPG cryptographic agent and passphrase cache.
feb 23 09:25:53 pc-arch systemd[575]: p11-kit-server.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed p11-kit server.
feb 23 09:25:53 pc-arch systemd[575]: pipewire.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed Multimedia System.
feb 23 09:25:53 pc-arch systemd[575]: pulseaudio.socket: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Closed Sound System.
feb 23 09:25:53 pc-arch systemd[575]: Reached target Shutdown.
feb 23 09:25:53 pc-arch systemd[575]: systemd-exit.service: Succeeded.
feb 23 09:25:53 pc-arch systemd[575]: Started Exit the Session.
feb 23 09:25:53 pc-arch systemd[575]: Reached target Exit the Session.
feb 23 09:25:53 pc-arch systemd[576]: pam_unix(systemd-user:session): session closed for user sddm
…
feb 23 09:25:55 pc-arch kwin_x11[746]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6294, resource id: 37748823, major code: 15 (QueryTree), minor code: 0
…
feb 23 09:25:57 pc-arch plasmashell[756]: trying to show an empty dialog
…
feb 23 09:26:05 pc-arch systemd[641]: Stopped Sound Service.
feb 23 09:26:05 pc-arch systemd[641]: Starting Sound Service...
…
feb 23 09:26:18 pc-arch kded5[677]: Registering ":1.138/StatusNotifierItem" to system tray

The session for "antonio" never stops.
a) How do you attempt to shutdown
b) do you use some autologin stuff?
c) can you actually log out of the session (and into sddm)
d) eliminate SDDM, try eg. startx, https://wiki.archlinux.org/index.php/Xinit (pay attention to the notes on a proper xinitrc)

Superjolly002 · 2020-02-23 14:42:22

Then:
a) I shutdown with the button at menu of KDE, but sometimes I shutdown via terminal.
b) No
c) Yes
d) Now I try and see what happend

Superjolly002 · 2020-02-23 15:33:17

I configured Xorg and it turns off but it takes a very long time...
There are the logs of the two shutdown: journalctl1 and journalctl2

seth · 2020-02-24 14:05:14

Those logs don't seem to cover a shutdown at all.

Can you shutdown from the multi-user.target?
https://wiki.archlinux.org/index.php/Sy … _boot_into

Superjolly002 · 2020-02-27 10:39:25

Hi,
sorry for my absence but I had to stay away from pc for some time.
Anyway I can't shutdown from multi-user.target, there is my log.

P.S: There is a little change, I switched from KDE to GNOME

seth · 2020-02-27 21:04:41

Networkmanager and by inference wpa_supplicant seem to linger around after the shutdown.
No idea whether that's significant, but you could try stopping NM before the shutdown…

Superjolly002 · 2020-02-28 11:19:56

Same problem... I don't have any idea...
There is the log

Superjolly002 · 2020-02-29 12:38:26

I think I solved the problem, I've just updated the bios and my pc shutdown and reboot works without problem.
Before to mark as "Solved" this problem I'll wait for some more time to be sure

Arch Linux

#1 2020-02-20 21:25:27

[Solved] System can't reboot or poweroff because of Xorg

#2 2020-02-20 22:02:13

Re: [Solved] System can't reboot or poweroff because of Xorg

#3 2020-02-21 11:42:08

Re: [Solved] System can't reboot or poweroff because of Xorg

#4 2020-02-21 12:07:13

Re: [Solved] System can't reboot or poweroff because of Xorg

#5 2020-02-21 14:05:55

Re: [Solved] System can't reboot or poweroff because of Xorg

#6 2020-02-22 09:32:21

Re: [Solved] System can't reboot or poweroff because of Xorg

#7 2020-02-22 12:04:08

Re: [Solved] System can't reboot or poweroff because of Xorg

#8 2020-02-22 15:41:17

Re: [Solved] System can't reboot or poweroff because of Xorg

#9 2020-02-22 16:33:16

Re: [Solved] System can't reboot or poweroff because of Xorg

#10 2020-02-22 17:30:48

Re: [Solved] System can't reboot or poweroff because of Xorg

#11 2020-02-23 08:34:10

Re: [Solved] System can't reboot or poweroff because of Xorg

#12 2020-02-23 12:26:23

Re: [Solved] System can't reboot or poweroff because of Xorg

#13 2020-02-23 14:42:22

Re: [Solved] System can't reboot or poweroff because of Xorg

#14 2020-02-23 15:33:17

Re: [Solved] System can't reboot or poweroff because of Xorg

#15 2020-02-24 14:05:14

Re: [Solved] System can't reboot or poweroff because of Xorg

#16 2020-02-27 10:39:25

Re: [Solved] System can't reboot or poweroff because of Xorg

#17 2020-02-27 21:04:41

Re: [Solved] System can't reboot or poweroff because of Xorg

#18 2020-02-28 11:19:56

Re: [Solved] System can't reboot or poweroff because of Xorg

#19 2020-02-29 12:38:26

Re: [Solved] System can't reboot or poweroff because of Xorg

Board footer