Bug#703005: Additional Info in my environment for kscreenlocker exit delays

[Stephen Dowdy <sdowdy@ucar.edu>]

I'm not sure if this is the same bug...

Summary:
    occasional/random screen remains blank for ~10 seconds after
        typing unlock password (password dialog disappears, screen
        is completely blank) (for me, i'd say it happens
        90% + of the time)
    often followed by up to 30 second No-Mouse-Or-Keyboard
        condition (mouse cursor does not display, keyboard
        input is not accepted, just have to wait)  (this
        happens perhaps 50-75% of the time)
    not related to load/#applications/#windows/
        amount-of-time-logged-already-logged-in.

In my environment several of us have, perhaps within the last 3
or so months started seeing a *random* screenlocker exit delay
of about 10 seconds where the screen stays black. It's not clear
how many users this affects, as i have only anecdotal info from
myself and one other fellow system administrator, and one user
who only mentioned it in the course of debugging another issue
after upgrading him to Wheezy. ("everything's working great, but
there's a 10 second delay before i can get to work after unlocking
the screen...") (i.e. we may have a number of users who are not
reporting the problem, assuming that's just the way things are).

We recently (~6 months ago) instituted *advisory* (i wanted
mandatory, but we're fighting with management :-( ) screenlocking
defaults here.

    /etc/kde4/kscreensaverrc
    [ScreenSaver]
    ActionBottomLeft=0
    ActionBottomRight=0
    ActionTopLeft=0
    ActionTopRight=0
    Enabled=true
    Lock=true
    LockGrace=60000
    PlasmaEnabled=false
    Saver=kblank.desktop
    Timeout=1800

I do not know if this has any impact on this bug, but it seems unlikely.

Additionally, for myself, ocasionally, i am left without a mouse or
keyboard for upto 30 seconds after the 10 second blank screen delay
and the screen display comes back.  I have not heard others report
this (yet).

FWIW, i have been working on using the kdebugdialog function to send
'kscreenlocker' notifications to a script, so that i could also
activate other functions such as locking the ssh-agent, pausing
multi-media applications, signalling IM clients to put themselves
in "away" mode.   (it'd be awesome if 'kscreenlocker' had a mechanism
internal to run user-supplied lock/unlock functions, but at least
with the debug dialog functions, i can hack this).  I am only doing
this on my OWN system, so this should not affect any other user,
but it might help explain the 30-second no-mouse-or-keyboard condition
i sometimes see.


X0rg.0.log and .xsession-errors have nothing that appears relevant.

I have re-installed 3 variant releases of the nVidia proprietary
drivers to ensure that's not the cause.

The screensaver package has not been updated in a while, so this is
likely a change made to another X11 package/lib that affects or is
triggered by the kscreenlocker application.

thanks,
--stephen