KDM plans and lightDM

Alex Fiestas afiestas at kde.org
Mon Jun 13 23:02:02 BST 2011

On Monday, June 13, 2011 10:24:22 PM Thomas Lübking wrote:
> Am Mon, 13 Jun 2011 21:34:56 +0200
> schrieb Martin Gräßlin <mgraesslin at kde.org>:
> > What does power management has to do with KDM? This belongs into
> > powerdevil where to my knowledge it should be handled fine, if
> > configured correctly.
> I guess he means:
>    "autosuspension from KDM", ie. w/o being logged in at all - he
>    started the system, didn't log in, talked a lot of meeting nonsense
>    (tm), legged in - and the battery was sucked away.
>    I won't comment on the preferred usage of advanced bioneural cpu to
> circumvent such issues in the first place, but this function does imho
> not belong into a DM but into some cron job (or whatever other daemon)
> that watches how long nobody has been logged in and *whether no relevant
> daemon is running* and then suspend the system after some time.
I don't really know what a DM should and should not do, so yes, a cron job 
should do the work just fine.
> This should also cover plymouth (the splashy replacement? really?) -
> but if you mean "bash", you'll require the feature (watching
> keystrokes) there, i think.
>    Putting this into a DM is rather bad because there's no good default*
> and it's not a DM's job to watch other processes (while maybe other
> logins...) and manage some random blacklist on them.
I'm not sure what's needed to integrate a DM with plymouth (the splashy 
replacement), though I know that KDM without patches doesn't have a smooth 
transition. There is a patch from the Fedora team that won't be applied into 
KDM because it is crappy (ossi says).
> *you do not want to suspend your system because you didn't log in since
> (despite starting to runlevel 5...) there's currently some sshd up and
> you're logged into from somewhere else, or just because the machine runs
> a webserver as well...
The 95% of desktop users doesn't use either sshd or a webserver. So at least 
this should be configurable.

GDM loads the "gnome power management" to solve the issue, what KDM does?
can KDM maybe launch kded with some daemons?

It may no be perfect but lightDM at least does some handling directly talking 
to UPower, though I agree that DM is not the place to fix this issue.

More information about the kde-core-devel mailing list