Suddenly I'm kicked out to login screen, all apps closed

Topic: Suddenly I'm kicked out to login screen, all apps closed (Read 3364 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Suddenly I'm kicked out to login screen, all apps closed

01 November 2017, 13:43:52

Hello,

It happened a few times already, randomly. I'm working on my XFCE4 desktop, not reproducible, and suddenly I see my sddm login screen, I was logged out. It also happened with lightdm DM, so it's not sddm.

The logs tell almost nothing, the precise time was 11:48:21:095

sddm.log:

Code: [Select]

[11:28:46.056] (II) DAEMON: Session started
[11:48:21.095] (II) HELPER: [PAM] Closing session
[11:48:21.097] (II) HELPER: [PAM] Ended.
[11:48:21.098] (II) DAEMON: Auth: sddm-helper exited successfully
[11:48:21.098] (II) DAEMON: Socket server stopping...
[11:48:21.098] (II) DAEMON: Socket server stopped.
[11:48:21.098] (II) DAEMON: Display server stopping...
[11:48:22.295] (II) DAEMON: Display server stopped.
[11:48:22.295] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[11:48:22.298] (II) DAEMON: Removing display ":0" ...
[11:48:22.299] (II) DAEMON: Adding new display on vt 7 ...
[11:48:22.299] (II) DAEMON: Loading theme configuration from ""
[11:48:22.299] (II) DAEMON: Display server starting...
[11:48:22.299] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{9abd59b6-6491-40fb-b700-0d5c322cf310} -background none -noreset -displayfd 19 -seat seat0 vt7
[11:48:23.218] (II) DAEMON: Setting default cursor
[11:48:23.226] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"

Xorg.0.log, only tail; nothing here, I think.

Code: [Select]

[    18.660] (II) event15 - (II) Logitech M570: (II) is tagged by udev as: Mouse Trackball
[    18.660] (II) event15 - (II) Logitech M570: (II) device set to 540 DPI
[    18.660] (II) event15 - (II) Logitech M570: (II) device is a pointer

messages.log: suspicious bluetoothd log at 11:48:21 is always present when this happens, is it the trigger?

Code: [Select]

Nov  1 11:44:57 beluga nm-dispatcher[8301]: req:1 'dhcp4-change' [wlan0]: start running ordered scripts...
Nov  1 11:48:21 beluga bluetoothd[4464]: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource
Nov  1 11:48:21 beluga bluetoothd[4464]: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink
Nov  1 11:48:22 beluga acpid[4258]: client 4440[0:0] has disconnected
Nov  1 11:48:22 beluga acpid[4258]: client 4440[0:0] has disconnected
Nov  1 11:48:22 beluga acpid[4258]: client connected from 8387[0:0]
Nov  1 11:48:22 beluga acpid[4258]: 1 client rule loaded
Nov  1 11:48:22 beluga acpid[4258]: client connected from 8387[0:0]
Nov  1 11:48:22 beluga acpid[4258]: 1 client rule loaded
Nov  1 11:48:50 beluga rtkit-daemon[7588]: Successfully made thread 8503 of process 8503 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov  1 11:48:50 beluga bluetoothd[4464]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSource
Nov  1 11:48:50 beluga bluetoothd[4464]: Endpoint registered: sender=:1.62 path=/MediaEndpoint/A2DPSink
Nov  1 11:48:50 beluga dbus[3470]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Nov  1 11:48:51 beluga blueman-mechanism[8627]: Starting blueman-mechanism
Nov  1 11:48:51 beluga dbus[3470]: [system] Successfully activated service 'org.blueman.Mechanism'
Nov  1 11:48:51 beluga blueman-mechanism[8627]: loading Ppp
Nov  1 11:48:51 beluga blueman-mechanism[8627]: loading Rfcomm
Nov  1 11:48:51 beluga blueman-mechanism[8627]: loading RfKill
Nov  1 11:48:51 beluga blueman-mechanism[8627]: loading Network
Nov  1 11:49:07 beluga dhclient[7369]: DHCPREQUEST on wlan0 to 192.168.1.2 port 67
Nov  1 11:49:07 beluga dhclient[7369]: DHCPACK from 192.168.1.2

daemon.log (same comments as above)

Code: [Select]

Nov  1 11:44:57 beluga nm-dispatcher[8301]: req:1 'dhcp4-change' [wlan0]: startrunning ordered scripts...
Nov  1 11:48:21 beluga bluetoothd[4464]: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource
Nov  1 11:48:21 beluga bluetoothd[4464]: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink
Nov  1 11:48:21 beluga kernel: udevd[615]: RUN{builtin}: 'uaccess' unknown /usr/lib/udev/rules.d/73-seat-late.rules:15
Nov  1 11:48:22 beluga acpid[4258]: client 4440[0:0] has disconnected
Nov  1 11:48:22 beluga acpid[4258]: client 4440[0:0] has disconnected
Nov  1 11:48:22 beluga acpid[4258]: client connected from 8387[0:0]
Nov  1 11:48:22 beluga acpid[4258]: 1 client rule loaded
Nov  1 11:48:22 beluga acpid[4258]: client connected from 8387[0:0]
Nov  1 11:48:22 beluga acpid[4258]: 1 client rule loaded
Nov  1 11:48:50 beluga rtkit-daemon[7588]: Successfully made thread 8503 of process 8503 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov  1 11:48:50 beluga rtkit-daemon[7588]: Supervising 1 threads of 1 processes of 1 users.

auth.log, something suspicious here as well:

Code: [Select]

Nov  1 11:28:46 beluga polkitd[4169]: Registered Authentication Agent for unix-session:c2 (system bus name :1.30 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
Nov  1 11:48:21 beluga polkitd[4169]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.30, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus)
Nov  1 11:48:21 beluga sddm-helper[7484]: pam_unix(sddm:session): session closed for user myuser
Nov  1 11:48:21 beluga kernel: elogind[3504]: Removed session c2.
Nov  1 11:48:21 beluga kernel: elogind[3504]: Failed to remove runtime directory /run/user/1000: Permission denied
Nov  1 11:48:23 beluga sddm-helper[8396]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Nov  1 11:48:23 beluga kernel: elogind[3504]: New session c3 of user sddm.

The other logs don't add anything, I think.
This is my daily use laptop so I must fix this fast. So, any help will be much appreciated.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #1 – 01 November 2017, 19:58:06

I've no idea about the problem, but I found 2 forum (ubuntu mainly) describing exactly your problems. The strange thing is that, despite the problem is and old one (2012), there is a post with the same error that appear on October 2017.

The links are:

https://bugs.launchpad.net/bugs/980519
https://bugs.launchpad.net/bugs/1010803

It seems something linked with the graphic card. Good luck

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #2 – 02 November 2017, 00:40:20

Thank you for the links.

At least one of the posts on the first link shows a log that has the two bluetooth messages similar to mine. I just wonder if that is the cause or a consequence. Anyway, they come before the kick-off message.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #3 – 02 November 2017, 10:00:23

Try out a different DM; maybe a GTK based one? because so is the DE.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #4 – 02 November 2017, 10:15:21

You should rule out the causes one by one. Begin by disabling the bluetooth daemon and, if need be, blacklisting the BT modules.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #5 – 02 November 2017, 12:38:11

Thank you for your help.

@physkets: it already did happen sometimes with lightdm and Manjaro-openrc, although not so frequently, before I changed to sddm.

@nous: it's going to be a very patient and stressing work. Saving my work every minute, not knowing when it's going to happen, fearing that my fs is broken next time...
Anyway, let's do it.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #6 – 02 November 2017, 15:31:12

I know, its a stupid idea, but try to disable WMI

create the file /etc/modprobe.d/blacklist.conf (or whatever .conf file you like) and add the line: blacklist wmi

Save. Reboot and try. Good luck.

Simply a stupid idea, but the a2pds bluetooth protocol is not so clever and you got that message from a2pds protocol. If you add that wmi is a Windows contamination in Linux and, in some way, can interact with the devices, maybe...

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #7 – 03 November 2017, 00:20:43

Thank you for the suggestion, I don't find it stupid at all, on the contrary, it's very imaginative.

I've just put it in place, we'll have to wait for a new event now. I just wished it was possible to give some more verbosity to PAM logs, anybody knows how?

Is it possible that some piece of code is trying to escalate priviledges, and the system, not being able to stop it in any other way, just ends the session as a last resort? Is it necessary to ask Linus?

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #8 – 03 November 2017, 08:47:27

You can find more info here:
https://wiki.archlinux.org/index.php/PAM

and 2 examples on how to save debug info into the log here:

https://chadmayfield.com/2016/06/15/enable-pam-debug-logging/
https://www.ibm.com/support/knowledgecenter/en/ssw_aix_71/com.ibm.aix.security/pam_enabling_debug.htm

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #9 – 03 November 2017, 10:50:38

Quote from: jssilva – on 03 November 2017, 00:20:43

Is it possible that some piece of code is trying to escalate priviledges, and the system, not being able to stop it in any other way, just ends the session as a last resort? Is it necessary to ask Linus?

This sounds like some form of systemd logic crawling into non-systemd scripts.
Thanks for the reading material on PAM. It pays off, when in doubt read everything

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #10 – 03 November 2017, 13:12:44

Thank you for all the info, specially on PAM.

So, everything is in place, waiting, but the system has behaved since my op. One would say it heard the discussion...

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #11 – 03 November 2017, 13:49:38

I would never recommend lightdm if you look at its history its never been a stable alternative. I would use LXDM and it is very customisable and in most cases just works.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #12 – 27 January 2018, 16:16:31

I know this thread is a bit old but I've been suffering from this issue during all this time, studying it, and I think I found the culprit: VirtualBox. So,
everything.log (first line just a mark, incident started at 01:24:24):

Code: [Select]

Jan 27 01:24:20 mypc kernel: [UFW BLOCK] IN=wlan0 OUT= MAC=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx RC=192.168.1.2 DST=192.168.1.11 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=35670 DF PROTO=UDP SPT=48747 DPT=514 LEN=120
Jan 27 01:24:24 mypc kernel: traps: VirtualBox[3896] general protection ip:7fc295706385 sp:7ffe3435f840 error:0 in libc-2.26.so[7fc2956cf000+1ae000]
Jan 27 01:24:24 mypc kernel: traps: VBoxCrWinCmd[8360] general protection ip:7ff4485c5385 sp:7ff3fa13ecd0 error:0 in libc-2.26.so[7ff44858e000+1ae000]
Jan 27 01:24:24 mypc bluetoothd[7222]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSource
Jan 27 01:24:24 mypc bluetoothd[7222]: Endpoint unregistered: sender=:1.28 path=/MediaEndpoint/A2DPSink
Jan 27 01:24:24 mypc kernel: traps: nspr-3[8325] trap int3 ip:7f573fd89074 sp:7f573c10da00 error:0
Jan 27 01:24:24 mypc kernel: udevd[763]: specified group 'kvm' unknown
Jan 27 01:24:24 mypc kernel: udevd[763]: RUN{builtin}: 'uaccess' unknown /usr/lib/udev/rules.d/73-seat-late.rules:15
Jan 27 01:24:24 mypc kernel: udevd[763]: specified group 'pcscd' unknown
Jan 27 01:24:25 mypc acpid[7016]: client 7198[0:0] has disconnected
Jan 27 01:24:25 mypc acpid[7016]: client 7198[0:0] has disconnected

And X crashes pushing me to login sddm login screen, xorg-session.log:

Code: [Select]

weather-Message: getting https://api.met.no/weatherapi/locationforecastlts/1.3/?lat=38.716702;lon=-9.133300;msl=45
VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
keepassxc: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: xfce4-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Gdk-Message: thunderbird: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
VirtualBox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Gdk-Message: wrapper-2.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

xfce4-panel-Message: Plugin systray-6 has been automatically restarted after crash.
xfce4-panel-Message: Plugin xfce4-orageclock-plugin-5 has been automatically restarted after crash.
xfce4-panel-Message: Plugin weather-12 has been automatically restarted after crash.
...

And dmesg:

Code: [Select]

[23021.086312] [UFW BLOCK] IN=wlan0 OUT= MAC=xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx SRC=192.168.1.2 DST=192.168.1.11 LEN=140 TOS=0x00 PREC=0x00 TTL=64 ID=35670 DF PROTO=UDP SPT=48747 DPT=514 LEN=120
[23025.339586] traps: VirtualBox[3896] general protection ip:7fc295706385 sp:7ffe3435f840 error:0 in libc-2.26.so[7fc2956cf000+1ae000]
[23025.340466] traps: VBoxCrWinCmd[8360] general protection ip:7ff4485c5385 sp:7ff3fa13ecd0 error:0 in libc-2.26.so[7ff44858e000+1ae000]
[23025.353611] elogind[3372]: Removed session c2.
[23025.355223] elogind[3372]: Failed to remove runtime directory /run/user/1000: Permission denied
[23025.414577] traps: nspr-3[8325] trap int3 ip:7f573fd89074 sp:7f573c10da00 error:0
[23025.501498] udevd[763]: specified group 'kvm' unknown
[23025.506661] udevd[763]: RUN{builtin}: 'uaccess' unknown /usr/lib/udev/rules.d/73-seat-late.rules:15
[23025.508662] udevd[763]: specified group 'pcscd' unknown
[23027.094822] elogind[3372]: New session c3 of user sddm.
[23050.190325] elogind[3372]: New session c4 of user root.

I probably need to create group kvm, but who belongs there? Didn't find leads on literature. But I guess this is not a reason to a segfault. I know pcscd, it is related to my smart card reader, irrelevant here.

So, I wonder if someone can help me stop this, once again; would be deeply appreciated.

Also, do you think I should file a bug on VirtualBox?

Furthermore, do you think I should migrate to qemu-kvm?

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #13 – 27 January 2018, 21:25:50

Running these examples on hardware which does not support required graphics features can cause this symptom, X crashing and returning to the login screen.
https://github.com/GNOME/cogl/tree/master/examples
Code should check if features are available before using them to avoid this. So if it was something along these lines, then it could certainly be a bug somewhere. There are many other graphics libs, it might not involve COGL. I don't think you would get FS corruption from these crashes as the computer is not powered off, but you could lose work.
Are you running Artix in virtualbox, or running virtualbox on Artix? Either it could be not providing graphics features or asking for unsupported ones. There are probably other ways to crash X I expect, that's just one possibility.

Re: Suddenly I'm kicked out to login screen, all apps closed

Reply #14 – 28 January 2018, 01:16:02

Thank you for helping

Quote from: ####### – on 27 January 2018, 21:25:50

Are you running Artix in virtualbox, or running virtualbox on Artix?

Sorry for not antecipating this; it's an Artix host running W10 guest.

It happens within a few minutes with demanding graphics apps in guest, but it also happened already with VB not even running, although I think just once in all this time. Turning off 2D and/or 3D acceleration in VB doesn't change the situation.

The host is a MacBook pro with the radeon turned off and using integrated intel HD3000, by means of vgaswitcheroo.

Do you think it would be better migrating to qemu-kvm?