For the last few Fedora releases I have not been able to lock my screen except using the command line. The command line that I use is:
/usr/libexec/kde4/kscreenlocker --forcelock --daemon
I can also get the screen to lock on timeout by causing the above script to run via the power management systems settings dialog. Without adding the script definition the screen only goes dark. Checking the "Lock screen on resume" has no effect.
Selecting Lock from the menu or clicking on the lock widget has no effect. When I first installed Fedora 17 those methods did not work until after the first full update, then stopped on a subsequent full update.
I even installed Fedora 17 fresh, instead of updating as I did for two previous releases, so as to start with a fresh ~/.kde directory.
How can I troubleshoot this? Where do I find how the Lock menu item is programmed and how do I find out what the lock widget is supposed to do.
Emmett
On Thursday 28 June 2012 06:37:37 Emmett Culley wrote:
How can I troubleshoot this? Where do I find how the Lock menu item is programmed and how do I find out what the lock widget is supposed to do.
Did you try locking with Ctrl+Alt+L ? My observation has been that screen locking is provided by krunner. Do you have it running? Does krunner react on Alt+F2 ?
Ctrl+Alt+L does nothing and neither does Alt+F2
Emmett
On 06/28/2012 06:46 AM, Lukas Middendorf wrote:
On Thursday 28 June 2012 06:37:37 Emmett Culley wrote:
How can I troubleshoot this? Where do I find how the Lock menu item is programmed and how do I find out what the lock widget is supposed to do.
Did you try locking with Ctrl+Alt+L ? My observation has been that screen locking is provided by krunner. Do you have it running? Does krunner react on Alt+F2 ?
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On 06/28/2012 08:36 AM, Rex Dieter wrote:
On 06/28/2012 10:27 AM, Emmett Culley wrote:
Ctrl+Alt+L does nothing and neither does Alt+F2
try running by hand in a konsole:
krunner
then repeat.
-- rex
[emmett@ws1 ~]$ krunner krunner(19739) KDevelopSessions::KDevelopSessions: INIT KDEV krunner(19739) KDevelopSessions::loadSessions: LOADSESSION!.>>> I/O warning : failed to load external entity "/home/emmett/.qalculate/eurofxref-daily.xml" I/O warning : failed to load external entity "/home/emmett/.qalculate/eurofxref-daily.xml" krunner(19739)/libplasma Plasma::Package::isValid: Could not find required file mainscript
I'll check to see if qalculate is installed...
Emmett
On 06/28/2012 10:41 AM, Emmett Culley wrote:
[emmett@ws1 ~]$ krunner krunner(19739) KDevelopSessions::KDevelopSessions: INIT KDEV krunner(19739) KDevelopSessions::loadSessions: LOADSESSION!.>>> I/O warning : failed to load external entity "/home/emmett/.qalculate/eurofxref-daily.xml" I/O warning : failed to load external entity "/home/emmett/.qalculate/eurofxref-daily.xml" krunner(19739)/libplasma Plasma::Package::isValid: Could not find required file mainscript
I'll check to see if qalculate is installed...
OK, some krunner plugin isn't loading properly the 'calculator' or some other one that seems to want some missing "mainscript" (which I think has something to do with qml plasma elements)
-- rex
On Thursday 28 June 2012 08:27:54 Emmett Culley wrote:
Ctrl+Alt+L does nothing and neither does Alt+F2
So this is a problem with krunner. Is it running? what does "ps aux| grep krunner" produce? What happens if you start krunner manually in konsole? You could try deleting ~/.kde/share/config/krunnerrc
On 06/28/2012 08:37 AM, Lukas Middendorf wrote:
On Thursday 28 June 2012 08:27:54 Emmett Culley wrote:
Ctrl+Alt+L does nothing and neither does Alt+F2
So this is a problem with krunner. Is it running? what does "ps aux| grep krunner" produce? What happens if you start krunner manually in konsole? You could try deleting ~/.kde/share/config/krunnerrc
[emmett@ws1 ~]$ ps aux| grep krunner emmett 19739 1.4 0.4 868948 39860 ? Sl 08:39 0:02 krunner emmett 19989 0.0 0.0 109400 844 pts/6 S+ 08:41 0:00 grep --color=auto krunner
It seems to be running, but I suspect it is running now because I ran it manually a few minutes ago, because lock screen now works. I'll try logging out and see if it is running when I log back in.
Emmett
On 06/28/2012 08:46 AM, Emmett Culley wrote:
On 06/28/2012 08:37 AM, Lukas Middendorf wrote:
On Thursday 28 June 2012 08:27:54 Emmett Culley wrote:
Ctrl+Alt+L does nothing and neither does Alt+F2
So this is a problem with krunner. Is it running? what does "ps aux| grep krunner" produce? What happens if you start krunner manually in konsole? You could try deleting ~/.kde/share/config/krunnerrc
[emmett@ws1 ~]$ ps aux| grep krunner emmett 19739 1.4 0.4 868948 39860 ? Sl 08:39 0:02 krunner emmett 19989 0.0 0.0 109400 844 pts/6 S+ 08:41 0:00 grep --color=auto krunner
It seems to be running, but I suspect it is running now because I ran it manually a few minutes ago, because lock screen now works. I'll try logging out and see if it is running when I log back in.
Emmett
I just updated my workstation to the latest and rebooted. When I logged in the screen lock did not work, and krunner was running:
[emmett@ws1 ~]$ ps aux| grep krunner emmett 2426 0.0 0.0 109400 844 pts/2 S+ 09:02 0:00 grep --color=auto krunner
Then I ran krunner from the console:
[emmett@ws1 ~]$ krunner krunner(2475) KDevelopSessions::KDevelopSessions: INIT KDEV krunner(2475) KDevelopSessions::loadSessions: LOADSESSION!.>>> I/O warning : failed to load external entity "/home/emmett/.qalculate/eurofxref-daily.xml" I/O warning : failed to load external entity "/home/emmett/.qalculate/eurofxref-daily.xml" krunner(2475)/libplasma Plasma::Package::isValid: Could not find required file mainscript
[emmett@ws1 ~]$ ps aux| grep krunner emmett 2475 39.3 0.5 869052 44472 pts/2 Sl 09:03 0:02 krunner emmett 2486 0.0 0.0 109400 844 pts/2 S+ 09:03 0:00 grep --color=auto krunner
Then screen lock worked and I saw this on the console screen each time I locked the screen and logged back in via from the screen lock.
First time:
[emmett@ws1 ~]$ X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 2 (X_ChangeWindowAttributes) Resource id: 0x4200017
Second time:
X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 2 (X_ChangeWindowAttributes) Resource id: 0x4200017
Emmett
Am 28.06.2012 18:11, schrieb Emmett Culley:
I just updated my workstation to the latest and rebooted. When I logged in the screen lock did not work, and krunner was running:
[emmett@ws1 ~]$ ps aux| grep krunner emmett 2426 0.0 0.0 109400 844 pts/2 S+ 09:02 0:00 grep --color=auto krunner
Then I ran krunner from the console
krunner was NOT running review your outout
the only line with krunner is your grep himself
On 06/28/2012 09:14 AM, Reindl Harald wrote:
Am 28.06.2012 18:11, schrieb Emmett Culley:
I just updated my workstation to the latest and rebooted. When I logged in the screen lock did not work, and krunner was running:
[emmett@ws1 ~]$ ps aux| grep krunner emmett 2426 0.0 0.0 109400 844 pts/2 S+ 09:02 0:00 grep --color=auto krunner
Then I ran krunner from the console
krunner was NOT running review your outout
the only line with krunner is your grep himself
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
That was the clue I needed. Turns out that I had unchecked krunner in the system settings startup dialog, as is my usual practice for programs I don't know how or why.
Thanks everyone for your suggestions.
Emmett
Emmett Culley wrote:
That was the clue I needed. Turns out that I had unchecked krunner in the system settings startup dialog, as is my usual practice for programs I don't know how or why.
Randomly disabling services you don't even know what they are for is a very bad practice. They're enabled by default for a reason.
Kevin Kofler
On 06/29/2012 04:47 PM, Kevin Kofler wrote:
Emmett Culley wrote:
That was the clue I needed. Turns out that I had unchecked krunner in the system settings startup dialog, as is my usual practice for programs I don't know how or why.
Randomly disabling services you don't even know what they are for is a very bad practice. They're enabled by default for a reason.
Kevin Kofler
Easy for you to say :-)
On 06/28/2012 08:37 AM, Emmett Culley wrote:
For the last few Fedora releases I have not been able to lock my screen except using the command line. The command line that I use is:
/usr/libexec/kde4/kscreenlocker --forcelock --daemon
I can also get the screen to lock on timeout by causing the above script to run via the power management systems settings dialog. Without adding the script definition the screen only goes dark. Checking the "Lock screen on resume" has no effect.
Selecting Lock from the menu or clicking on the lock widget has no effect. When I first installed Fedora 17 those methods did not work until after the first full update, then stopped on a subsequent full update.
I even installed Fedora 17 fresh, instead of updating as I did for two previous releases, so as to start with a fresh ~/.kde directory.
How can I troubleshoot this? Where do I find how the Lock menu item is programmed and how do I find out what the lock widget is supposed to do.
Does this work?
qdbus org.kde.screensaver /ScreenSaver \ org.freedesktop.ScreenSaver.SetActive 1
-- rex
On 06/28/2012 06:57 AM, Rex Dieter wrote:
On 06/28/2012 08:37 AM, Emmett Culley wrote:
For the last few Fedora releases I have not been able to lock my screen except using the command line. The command line that I use is:
/usr/libexec/kde4/kscreenlocker --forcelock --daemon
I can also get the screen to lock on timeout by causing the above script to run via the power management systems settings dialog. Without adding the script definition the screen only goes dark. Checking the "Lock screen on resume" has no effect.
Selecting Lock from the menu or clicking on the lock widget has no effect. When I first installed Fedora 17 those methods did not work until after the first full update, then stopped on a subsequent full update.
I even installed Fedora 17 fresh, instead of updating as I did for two previous releases, so as to start with a fresh ~/.kde directory.
How can I troubleshoot this? Where do I find how the Lock menu item is programmed and how do I find out what the lock widget is supposed to do.
Does this work?
qdbus org.kde.screensaver /ScreenSaver \ org.freedesktop.ScreenSaver.SetActive 1
-- rex
[emmett@ws1 ~]$ qdbus org.kde.screensaver /ScreenSaver org.freedesktop.ScreenSaver.SetActive 1 Cannot find 'org.freedesktop.ScreenSaver.SetActive' in object /ScreenSaver at org.kde.screensaver
Nothing happens.
Emmett
-
Emmett Culley -
Kevin Kofler -
Lukas Middendorf -
Reindl Harald -
Rex Dieter