From the xsession output it looks like the lockscreen successfully exited. It
http://bugzilla.opensuse.org/show_bug.cgi?id=964548
http://bugzilla.opensuse.org/show_bug.cgi?id=964548#c5
Martin Gräßlin changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kde@martin-graesslin.com
--- Comment #5 from Martin Gräßlin ---
Upstream maintainer speaking.
prints "Grab Released" which is in method
void KSldApp::doUnlock()
which is called from three places:
1) If the kscreenlocker_greet failed to start. This would print an error
message "Greeter Process not available" which is not in the log
2) If logind send the Unlock dbus signal
3) If kscreenlocker_greet exits with exit code 0. This can happen after grace
time (given description not the case), after logind Unlock or - the normal case
- after the password was accepted successfully.
Given the information in the bug report I can exclude case 1), consider case 2)
unlikely and am sure that the condition grace time of number 3) is not the
case.
So I assume we found a new way to exit kscreenlocker_greet successfully. My gut
feeling tells me it's related to Qt's utterly broken multi screen handling
including crashes when screens are turned off (see "requesting unexisting
screen 0" in log). But to figure that out we would need the debug output of
kscreenlocker_greet which is only available since
http://commits.kde.org/kscreenlocker/a68dda3dd2a8a60e7f03beb5f0e652ef10fedba...
So we need to manually try that.
@Dirk: can you please try to run:
1) run "kscreenlocker_greet --testing" from a konsole
2) turn off the display
Afterwards please tell us whether the application exited or not. If it did,
please add the debug output from the konsole.
Please note that kscreenlocker_greet is installed into the libexec directory
and is not in $PATH. Unfortunately I do not know where openSUSE installs that
file.
--
You are receiving this mail because:
You are on the CC list for the bug.