Bug 162260

Summary: Recognize SLiM as login manager and activate "shutdown" and "reboot" options.
Product: [Plasma] ksmserver Reporter: DrSlony <bugs>
Component: generalAssignee: Lubos Lunak <l.lunak>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: mail, see.kde
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description DrSlony 2008-05-18 15:46:38 UTC
Version:            (using KDE 3.5.9)
Installed from:    Gentoo Packages
OS:                Linux

Recognize SLiM as login manager and activate "shutdown" and "reboot" options.
Comment 1 DrSlony 2009-05-19 13:03:43 UTC
Bump
Comment 2 SeeSchloss 2010-08-12 22:02:04 UTC
Now, I'm not a KDE dev but I took a look at ksmserver's code. What the code does now is:
- check if the offerShutdown setting is enabled (enabling it by default)
- check if KDM allows shutdown

The actual shutdown code checks these things too, and has special handling when shutdown is requested even though KDM or the offerShutdown setting do not "allow" it.

From this, a few remarks:
- right now, the offerShutdown setting seems useless, it looks to me as an exact duplicate of KDM's "Allow shutdown" setting.
- it sure does not work the way anyone would expect it to: enabling the "Offer shutdown options" setting does *not* make KDE offer shutdown options in several cases.
- ksmserver already seems to handle shutdown when KDM is not present.

And a few solutions I see:
- in KSMServer::canShutdown() return true if offerShutdown is enabled, and KDM allows shutdown OR if the login manager is not KDM.
- always disable and grey out "Offer shutdown options" if KDM does not allow shutdown or if the login manager is not KDM.
- remove "Offer shutdown options" altogether and just use KDisplayManager.canShutdown().

Of course, the first one seems best to me.

In the current state of things this looks more like a bug than a wish, to me.
Comment 3 Oswald Buddenhagen 2010-10-24 12:04:26 UTC
ftr, much of what was said in bug 186198 applies here as well.
Comment 4 DrSlony 2014-09-15 16:31:49 UTC
Abandoning it.