On 06/17/2011 06:48 AM, Wes Hardaker wrote: >>>>>> On Thu, 16 Jun 2011 20:59:15 -0700, Emmett Culley<emmett@xxxxxxxxxxxxxxx> said: > > EC> Anybody else seeing this? > > Yep. > > EC> This all work in Fedora 14, and I believe it also worked when I first > EC> installed Fedora 15. > > It didn't work for me after install F15. But I did a clean install and > have been figuring I must have missed installing some package. Right after I sent the above note I suddenly found that I could lock my screen normally, both with the Leave | Lock menu item and with inactivity timeouts. It stayed like that until I logged out again, now that I logged back in I can only lock the screen using the commandline: /usr/libexec/kde4/kscreenlocker --forcelock I have no idea why it stared working, nor why it stopped working. I thought at first it started working because I used the command line to lock, as it appeared to after I discovered that method that id worked again. But that is not the case. I've used the command line method a couple of times to day, and that is still the only way to lock the screen. On my laptop where I did a successful upgrade via DVD it all works as expected. I tried a DVD upgrade on my workstation (this machine where it doesn't work) and it wouldn't restart after reboot, so I did a fresh install, copying my ~/.kde directory form the old system. BTW, when I user the command line to lock my screen I see the following in the console when I return: [emmett@ws1 ~]$ /usr/libexec/kde4/kscreenlocker --forcelock X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 2 (X_ChangeWindowAttributes) Resource id: 0x640001e I suppose it is time to do a bug report. Emmett _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
