You are not logged in.
Pages: 1
Hello everyone,
I've had a problem for two days. My Arch Linux logout unexpectedly (it brings me back to the black screen before the display manager starts), after 2-3 seconds, LXDM starts and let me login.
My Desktop environment is XFCE4 and Display manager is LXDM.
Here is the output of dmesg: https://pastebin.com/Aaqw2fJk
Here is the contents of Xorg.0.log: https://pastebin.com/UfJJF0cU , and Xorg.0.log.old: https://pastebin.com/4cYntEhX
Here is the output of journalctl -b 0: https://pastebin.com/vgc8u6Vz
I've done a google search and found this thread: https://bbs.archlinux.org/viewtopic.php?id=224959, but the OP doesn't reply anymore so I create this one.
Thanks for your help.
Last edited by Endless Love (2017-09-02 14:14:07)
Offline
Aug 31 15:32:33 archlinux kernel: microcode: sig=0x20655, pf=0x10, revision=0x4
Aug 31 15:32:33 archlinux kernel: microcode: Microcode Update Driver: v2.2.You do not appear to have enabled microcode updates
Aug 31 15:34:20 archlinux kernel: traps: light-locker[933] trap int3 ip:7f0f83c00411 sp:7fffe3297140 error:0
....
Aug 31 15:34:21 archlinux systemd-coredump[949]: Process 933 (light-locker) of user 1000 dumped core.
....
Aug 31 17:41:45 archlinux kernel: traps: light-locker[7342] trap int3 ip:7f67dac21411 sp:7fffd7388af0 error:0
....
Aug 31 17:41:46 archlinux systemd-coredump[7363]: Process 7342 (light-locker) of user 1000 dumped core.
....That would appear to be the cause of the logout
Aug 31 17:30:13 archlinux kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
Aug 31 17:30:13 archlinux kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
Aug 31 17:30:13 archlinux kernel: CPU2: Core temperature/speed normal
Aug 31 17:30:13 archlinux kernel: CPU3: Core temperature/speed normalYou might want to also investigate this.
Edit:
Oh and welcome to the arch linux forums Endless Love.
Last edited by loqs (2017-08-31 12:35:14)
Offline
You do not appear to have enabled microcode updates
Hmm I remembered I had enabled it when I finished installing Arch Linux
That would appear to be the cause of the logout
Yeah, I also thought it was because of light-locker when I first look at the output of
journalctl -b 0, because I got logged out two times this afternoon and they happened at exactly the time of the light-locker things. I've done some google searches but I found nothing so I decided to post here.
I have just remembered that two days ago I change the "Automatically lock the session" setting of light-locker from "When the screensaver is activated" to "When the screensaver is deactivated", I've changed it back and hope I won't be logged out in the future (although I think it's not relevant)
You might want to also investigate this.
I'm using an old laptop and this has happened for about 3 years already, I've tried a lot of things but the temperatures doesn't go down. I will buy a new laptop next year so I don't no longer care about it.
Thanks for your reply. (and sorry for my bad English)
Offline
It might relate to the locker, but the X11 server probably segfaults because of the synaptics driver
This is bad:
[ 1724.011] (EE) BUG: triggered 'if (priv->num_active_touches > priv->num_slots)'
[ 1724.026] (EE) BUG: synaptics.c:3028 in UpdateTouchState()
[ 1724.045] (EE)
[ 1724.045] (EE) Backtrace:
[ 1724.097] (EE) 0: /usr/lib/xorg/modules/input/synaptics_drv.so (_init+0x8dd) [0x7f0dd395564d]
[ 1724.097] (EE) 1: /usr/lib/xorg/modules/input/synaptics_drv.so (_init+0x17d8) [0x7f0dd3957018]
[ 1724.098] (EE) 2: /usr/lib/xorg/modules/input/synaptics_drv.so (_init+0x3da3) [0x7f0dd395bff3]
[ 1724.099] (EE) 3: /usr/lib/xorg-server/Xorg (input_unlock+0x293) [0x55c5f5b79483]
[ 1724.099] (EE) 4: /usr/lib/xorg-server/Xorg (OsCleanup+0x621) [0x55c5f5b7bea1]
[ 1724.100] (EE) 5: /usr/lib/xorg-server/Xorg (input_unlock+0xde) [0x55c5f5b7907e]
[ 1724.110] (EE) 6: /usr/lib/libpthread.so.0 (start_thread+0xd9) [0x7f0ddb895049]
[ 1724.122] (EE) 7: /usr/lib/libc.so.6 (clone+0x3f) [0x7f0ddb5d5f48]And probably the cause of
[ 7722.420] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x55c5f5b7af39]
[ 7722.422] (EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x50) [0x7f0ddb89f82f]
[ 7722.423] (EE) 2: /usr/lib/xorg-server/Xorg (XIGetDeviceProperty+0x40) [0x55c5f5b0fa40]
[ 7722.423] (EE) 3: /usr/lib/xorg-server/Xorg (XIGetDeviceProperty+0x182) [0x55c5f5b0fc32]
[ 7722.423] (EE) 4: /usr/lib/xorg-server/Xorg (XISetDevicePropertyDeletable+0x3d8) [0x55c5f5b10438]
[ 7722.424] (EE) 5: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x368) [0x55c5f5a151e8]
[ 7722.424] (EE) 6: /usr/lib/xorg-server/Xorg (InitFonts+0x420) [0x55c5f5a191f0]
[ 7722.425] (EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xea) [0x7f0ddb5084ca]
[ 7722.426] (EE) 8: /usr/lib/xorg-server/Xorg (_start+0x2a) [0x55c5f5a02e9a]The locker segfault *might* be due to the unexpected loss of the server connection (many X11 clients don't handle this gracefully)
This thread says the cause of the synaptics hiccup is "Disable Touchpad While Typing" - does that ring a bell for you?
https://www.linuxquestions.org/question … 175547050/
Offline
It might relate to the locker, but the X11 server probably segfaults because of the synaptics driver
This is bad:[ 1724.011] (EE) BUG: triggered 'if (priv->num_active_touches > priv->num_slots)' [ 1724.026] (EE) BUG: synaptics.c:3028 in UpdateTouchState() [ 1724.045] (EE) [ 1724.045] (EE) Backtrace: [ 1724.097] (EE) 0: /usr/lib/xorg/modules/input/synaptics_drv.so (_init+0x8dd) [0x7f0dd395564d] [ 1724.097] (EE) 1: /usr/lib/xorg/modules/input/synaptics_drv.so (_init+0x17d8) [0x7f0dd3957018] [ 1724.098] (EE) 2: /usr/lib/xorg/modules/input/synaptics_drv.so (_init+0x3da3) [0x7f0dd395bff3] [ 1724.099] (EE) 3: /usr/lib/xorg-server/Xorg (input_unlock+0x293) [0x55c5f5b79483] [ 1724.099] (EE) 4: /usr/lib/xorg-server/Xorg (OsCleanup+0x621) [0x55c5f5b7bea1] [ 1724.100] (EE) 5: /usr/lib/xorg-server/Xorg (input_unlock+0xde) [0x55c5f5b7907e] [ 1724.110] (EE) 6: /usr/lib/libpthread.so.0 (start_thread+0xd9) [0x7f0ddb895049] [ 1724.122] (EE) 7: /usr/lib/libc.so.6 (clone+0x3f) [0x7f0ddb5d5f48]And probably the cause of
[ 7722.420] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x55c5f5b7af39] [ 7722.422] (EE) 1: /usr/lib/libpthread.so.0 (funlockfile+0x50) [0x7f0ddb89f82f] [ 7722.423] (EE) 2: /usr/lib/xorg-server/Xorg (XIGetDeviceProperty+0x40) [0x55c5f5b0fa40] [ 7722.423] (EE) 3: /usr/lib/xorg-server/Xorg (XIGetDeviceProperty+0x182) [0x55c5f5b0fc32] [ 7722.423] (EE) 4: /usr/lib/xorg-server/Xorg (XISetDevicePropertyDeletable+0x3d8) [0x55c5f5b10438] [ 7722.424] (EE) 5: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x368) [0x55c5f5a151e8] [ 7722.424] (EE) 6: /usr/lib/xorg-server/Xorg (InitFonts+0x420) [0x55c5f5a191f0] [ 7722.425] (EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xea) [0x7f0ddb5084ca] [ 7722.426] (EE) 8: /usr/lib/xorg-server/Xorg (_start+0x2a) [0x55c5f5a02e9a]The locker segfault *might* be due to the unexpected loss of the server connection (many X11 clients don't handle this gracefully)
This thread says the cause of the synaptics hiccup is "Disable Touchpad While Typing" - does that ring a bell for you?
https://www.linuxquestions.org/question … 175547050/
Thanks for pointing that out, in fact I switched from libinput to xf86-input-synaptics-led yesterday, but I got logged out the day before that so I didn't think synaptics was the problem. I've uninstalled light-locker and I don't get logged out anymore but sometimes the X session gets hanged for a while (I still can move the mouse but it doesn't response to the click events).
I do have the "Disable Touchpad While Typing" enabled, but that feature doesn't seem to work (i.e. I can still use the touchpad while typing), I've just disabled it now. Hope this will work.
Thanks for your help.
Last edited by Endless Love (2017-09-01 06:20:50)
Offline
I no longer get logged out after remove light-locker and turn off the "Disable Touchpad While Typing" feature of synaptics.
Thank you guys, @loqs and @seth for helping me.
How can I close this thread by the way?
Last edited by Endless Love (2017-09-02 13:09:06)
Offline
You can't - just mark ist "[SOLVED]" by editing the subject of your original posts.
Mods close threads to prevent them from being spammed/necrobumped etc.
Offline
Pages: 1