Bug 711234

Summary: attempts to lock KDE console gives "Will not lock the session, as unlocking would be impossible: No appropriate greeter plugin configured."
Product: [Fedora] Fedora Reporter: wallyk <wallykramer>
Component: kdebase-workspaceAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: andreas.petzold, dennis, fedora, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: kdebase-workspace-4.6.5-2.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-06 04:14:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
list of packages installed none

Description wallyk 2011-06-06 22:22:39 UTC 
Created attachment 503341 [details]
list of packages installed

Description of problem:

There appears to be no reasonable way to lock the console when using KDE.  The most friendly way (so far) is to execute xlock from a command prompt, but this sometimes (one in four) hoses the session (requires restarting the XServer or logging in remotely and killing xlock).

With previous Fedora releases, typing Ctrl-Alt-L locks the screen just fine.  Ctrl-Alt-L also works as expected on the exact same system using GNOME under the same Fedora 15 installation.  With KDE, it does not lock the screen; instead a pop-up appears with:

   Will not lock the session, as unlocking would be impossible:
   No appropriate greeter plugin configured.
                          OK

I have searched for missing dependencies without success and been updating Fedora every night ("yum update") in the hopes the issue was resolved.

The only comments I find on the forums are a year or two old and suggest that KDE was not packaged correctly.  For example http://forum.kde.org/viewtopic.php?f=66&t=88525 and http://forums.gentoo.org/viewtopic-t-571969.html

How reproducible:
100% on this system.  Haven't tried it on another system.  So far, this is the only system I have running Fedora 15.

Steps to Reproduce:
1. Install Fedora 15, any patch since release
2. Login using KDE
3. press Ctrl-Alt-L
  
Actual results:
Message says it won't lock the session.

Expected results:
Screen locked, password required to unlock

Additional info:
  Linux 2.6.38.6-27.fc15.i686 i686
  System:  Fedora release 15 (Lovelock)
  KDE:  4.6.3 (4.6.3)

  Vendor: X.Org
  Model:   Gallium 0.4 on AMD RS780
  Driver:   2.1 Mesa 7.11-devel

  Processor (CPU):   AMD Athlon(tm) II X2 215 Processor
  Speed:  2,700.00 MHz
  Cores:  2

  Total memory (RAM):  2.7 GB
  Free memory:  209.2 MB (+ 1.6 GB Caches)
  Free swap:  4.7 GB
Comment 1 Rex Dieter 2011-07-06 15:47:49 UTC 
I cannot reproduce this on any of my f14 or f15 boxes, using kde-4.6.3


How did you install kde?
Comment 2 Rex Dieter 2011-07-06 15:49:22 UTC 
Reading those other threads, implies this only happens when kdm is not installed or in use.  Is that the case for you?
Comment 3 Andreas Petzold 2011-07-06 15:53:33 UTC 
I had the same problem and installing kdm fixed it. So I guess either the packaging of the greeter plugins need to be changed, or kdm needs to be a dependency for a kde session.
Comment 4 Rex Dieter 2011-07-06 16:00:01 UTC 
OK, I'll look into making a kdm-less setup work.
Comment 5 Rex Dieter 2011-07-06 16:19:39 UTC 
kdebase-workspace...
%changelog
* Wed Jul 06 2011 Rex Dieter <rdieter> 4.6.5-2
- move kgreet_* plugins to main pkg, needed by kscreenlocker (#711234)
Comment 6 wallyk 2011-07-06 16:28:45 UTC 
(In reply to comment #1)
> I cannot reproduce this on any of my f14 or f15 boxes, using kde-4.6.3
> 
> 
> How did you install kde?

I installed kde using the "Add/Remove Software" utility gpk-application 3.0.0 package manager for GNOME.  I'm not sure which options I explicitly selected and which were included as dependencies.  Maybe that is in a log file?

I have not used kde since reporting the bug:  The dilemma of hosing or not locking the session is unacceptable.  Kde is still configured if any experiments would be useful, but GNOME works well enough for secure usage.