Bug 13295 - Screensaver locks screen while keeping the windows on the foreground
: Screensaver locks screen while keeping the windows on the foreground
Status: CLOSED NOTABUG
: Sisyphus
(All bugs in Sisyphus/xscreensaver)
: unstable
: all Linux
: P2 normal
Assigned To:
:
:
:
:
:
  Show dependency tree
 
Reported: 2007-11-02 01:16 by
Modified: 2008-01-30 01:35 (History)


Attachments
xscreensaver -verbose (1.98 KB, text/plain)
2007-11-02 12:33, wiee
no flags Details
Run with the -verbose option and waited until the bug reproduced itself. (35.69 KB, text/plain)
2007-11-03 02:50, wiee
no flags Details
xwininfo -root -tree (133.29 KB, text/plain)
2007-12-02 12:59, wiee
no flags Details
xwininfo -all -id 0x360007f (1.23 KB, text/plain)
2007-12-02 13:00, wiee
no flags Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-11-02 01:16:56
From time to time xscreensaver locks screen on no activity in a way that the
screensaver itself is not visible (it only overlaps desktop background), mouse
can be moved, but the system does not seem to respond to clicks or keyboard.

All this is quite natural as the system simply expects you to enter your
password in order to unlock the screen. But it is not visible, as stated above.
------- Comment #1 From 2007-11-02 12:08:02 -------
What WM/DE, what application?  Can it be easily reproduced?
------- Comment #2 From 2007-11-02 12:14:56 -------
KDE 3.5.8

In order to reproduce it, I just have to leave the PC idle for some half an hour.

The applications that usually stay on the foreground are Thunderbird, Gkrellm,
OpenOffice.org and Firefox.
------- Comment #3 From 2007-11-02 12:29:08 -------
What XOrg version and video driver?

Try to run xscreensaver with -verbose option and show log.
------- Comment #4 From 2007-11-02 12:33:33 -------
Created an attachment (id=2250) [details]
xscreensaver -verbose
------- Comment #5 From 2007-11-03 02:50:30 -------
Created an attachment (id=2251) [details]
Run with the -verbose option and wait until the bug reproduced itself.
------- Comment #6 From 2007-11-03 15:33:24 -------
Лёш, а мне сегодня с утра пришлось опять переключаться в консоль и килять
xscreensaver -- не отзывался.  В логе при этом было лишь:

Nov  3 13:02:43 pad xscreensaver: pam_tcb(xscreensaver:auth): conversation
failed
Nov  3 13:02:43 pad xscreensaver: pam_tcb(xscreensaver:auth): Unable to obtain
a
password

Недавно он в кнопку открывалки вместо "OK" писал "FAILED" чего-то там.  Передай
мужикам -- уже сломано, пора чинить ;-)
------- Comment #7 From 2007-11-03 17:21:16 -------
(In reply to comment #6)
> Nov  3 13:02:43 pad xscreensaver: pam_tcb(xscreensaver:auth): conversation failed

Вообще-то его надо было перезапустить после обновления до >= 5.02-alt1.  Там
поменялась работа с pam.  И проверить /etc/pam.d/ на тему .rpmnew, потому как
%config(noreplace).
------- Comment #8 From 2007-11-03 18:15:57 -------
xscreensaver: 02:46:09: blanking screen at Sat Nov  3 02:46:09 2007.
xscreensaver: 02:46:12: 0: grabbing keyboard on 0x58... AlreadyGrabbed.
xscreensaver: 02:46:13: couldn't grab keyboard!  (AlreadyGrabbed)
xscreensaver: 02:46:13: 0: removing focus from 0x280000b / RevertToPointerRoot.
xscreensaver: 02:46:17: 0: grabbing keyboard on 0x58... AlreadyGrabbed.
xscreensaver: 02:46:18: couldn't grab keyboard!  (AlreadyGrabbed)

Screen is not locked and window 0x280000b prevents keyboard and mouse to be grabbed.

Please repeat steps with xss -verbose, remember window id and attach:

xwininfo -root -tree
xwininfo -all -id ID_OF_PROBLEM_WINDOW
------- Comment #9 From 2007-11-03 18:48:28 -------
$ uptime
 17:47:11 up 1 day,  6:11,  1 user,  load average: 0.45, 0.11, 0.09
$ ls /etc/pam.d/*.rpm*
/bin/ls: /etc/pam.d/*.rpm*: No such file or directory
------- Comment #10 From 2007-11-03 18:56:19 -------
(In reply to comment #9)

sudo rpm -Vf /etc/pam.d/xscreensaver

И вообще, к этому багу оно отношения не имеет, а '"FAILED" чего-то там' означает
что xscreensaver не был перезапущен после обновления.
------- Comment #11 From 2007-12-02 12:59:54 -------
Created an attachment (id=2299) [details]
xwininfo -root -tree
------- Comment #12 From 2007-12-02 13:00:22 -------
Created an attachment (id=2300) [details]
xwininfo -all -id 0x360007f
------- Comment #13 From 2007-12-02 21:16:40 -------
Was it _locked_ again?  Is xscreensaver log lost?

I have no ideas.  Reported upstream...
------- Comment #14 From 2008-01-30 00:38:46 -------
From: Jamie Zawinski <jwz@jwz>

The answer is right there in the bug report -- some other app has the keyboard
grabbed.  I have no idea what that app is, or why, but it's impossible for
xscreensaver to lock the screen if it's unable to grab the keyboard.
------- Comment #15 From 2008-01-30 00:39:40 -------
Is flash plugin installed?  Is there any flash content somewhere in browser?
------- Comment #16 From 2008-01-30 00:47:53 -------
As far as I see, the conflict is that both KDE screensaver and xscreensaver are
activated. And the latter doesn't work properly under KDE.

Actually, it should be disabled, but as far as I can see it is invoked from
within somewhere around /etc/scriplets.d.
------- Comment #17 From 2008-01-30 01:35:23 -------
xscreensaver packages does not contain any autostart scripts nor XDG autostart
desktop files.  Two screensavers doesn't play well, but it's not xscreensaver's
problem.