https://bugs.kde.org/show_bug.cgi?id=490924
--- Comment #6 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to Sophie Dexter from comment #5) > (In reply to Fabian Vogt from comment #4) > > It would be useful if you could run > > > > QT_LOGGING_RULES=kscreenlocker_greet.debug=true > > /usr/libexec/kscreenlocker_greet --testing -platform xcb > > > > and reproduce the issue. > > Hmm, running that is proving to be tricky since this only occurs immediately > after waking my system from sleep and I don't know how to do what you ask. > I've tried running from a different TTY but I am greeted with: You should be able to run the command and try the sleep button. > ... > I suspect I've missed something obvious and there is a way to run this > immediately after waking my system from sleep to test kscreenlocker but I > cannot fathom what, is there a way to simulate system sleeping and/or make > the PAM conversation fail instead? It's also possible to "fake" the suspend by removing the call to PowerManagement::instance()->suspend(); instead of m_authenticators->cancel(); -- You are receiving this mail because: You are watching all bug changes.
