FS#57730 - [xscreensaver] Crash unlocks session
Attached to Project:
Arch Linux
Opened by Tom Herbert (mashdot) - Tuesday, 06 March 2018, 09:29 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 13 March 2018, 07:22 GMT
Opened by Tom Herbert (mashdot) - Tuesday, 06 March 2018, 09:29 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 13 March 2018, 07:22 GMT
|
Details
Over the last two weeks I have been locking my laptop with
xscreensaver, closing the lid to suspend, only to find the
next morning my session is unlocked. It is random, and
cannot reproduce it, but it is serious enough that I can no
longer use it in my workplace.
A quick Google reveals that there has been issues (for a number of years) with forcing an xscreensaver crash indeed unlocks the user session. This was news to me. Packages that are most likely pertinent to my bug: xscreensaver 5.38-1 xorg-server 1.19.6+13+gd0d1a694f-1 stumpwm (https://github.com/stumpwm/stumpwm) Still trying to find a way to reproduce it, and figuring out a way to understand what is crashing xscreensaver overnight during suspend. |
This task depends upon
Closed by Antonio Rojas (arojas)
Tuesday, 13 March 2018, 07:22 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Tuesday, 13 March 2018, 07:22 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
---
xscreensaver: signal: 1: child pid 28047 (energystream) terminated with signal 15.
xscreensaver: signal: 0: child pid 28046 (energystream) terminated with signal 15.
xscreensaver: 21:12:33: 0: visual 0x20 (TrueColor, depth: 24, cmap: 256)
xscreensaver: 21:12:33: 0: saver window is 0x16001af.
xscreensaver: 21:12:33: 0: destroyed old saver window 0x16001ab.
xscreensaver: 21:12:33: 0: spawning "energystream -root" in pid 28337.
xscreensaver: 21:12:33: 1: visual 0x20 (TrueColor, depth: 24, cmap: 256)
xscreensaver: 21:12:33: 1: saver window is 0x16001b1.
xscreensaver: 21:12:33: 1: destroyed old saver window 0x16001ad.
xscreensaver: 21:12:33: 1: spawning "energystream -root" in pid 28338.
xscreensaver: 21:15:33: 0: killing pid 28337 (energystream)
xscreensaver: 21:15:33: 1: killing pid 28338 (energystream)
xscreensaver: signal: 1: child pid 28338 (energystream) terminated with signal 15.
xscreensaver: signal: 0: child pid 28337 (energystream) terminated with signal 15.
xscreensaver: 21:15:33: 0: visual 0x20 (TrueColor, depth: 24, cmap: 256)
xscreensaver: 21:15:33: 0: saver window is 0x16001b3.
xscreensaver: 21:15:33: 0: destroyed old saver window 0x16001af.
xscreensaver: 21:15:33: 0: spawning "energystream -root" in pid 28595.
xscreensaver: 21:15:33: 1: visual 0x20 (TrueColor, depth: 24, cmap: 256)
xscreensaver: 21:15:33: 1: saver window is 0x16001b5.
xscreensaver: 21:15:33: 1: destroyed old saver window 0x16001b1.
xscreensaver: 21:15:33: 1: spawning "energystream -root" in pid 28596.
xscreensaver: 21:18:33: 0: killing pid 28595 (energystream)
xscreensaver: 21:18:33: 1: killing pid 28596 (energystream)
xscreensaver: signal: 0: child pid 28595 (energystream) terminated with signal 15.
xscreensaver: signal: 1: child pid 28596 (energystream) terminated with signal 15.
XIO: fatal IO error 10 (No child processes) on X server ":0.0"
after 21085 requests (21085 known processed) with 1 events remaining.
---
Tonight I will test with another screensaver as perhaps "energystream" is to blame.
The XIO fatal IO error at the end is X exiting because the last child process exited.