My ksmserver plans

[David Edmundson]

>or by another 3rd process? (don't they become a bit.. many?)

In terms of processes we will have the existing:
  - ksmserver
  - logout greeter
And new:
  - startup binary (kstartup?)
  - shutdown binary (kshutdown)

The DBus name org.kde.shutdown would initially go on ksmserver, then move
to this new binary when that's done.

The last two could be merged, but then we can't make them exit when it's
finished.
The other clever part of this design is that DBus activation can contain
both an Exec line and a SystemdService. The latter is only used if the
system supports it. That way krunner/plasmashell/logout greeter have keep
one code path, but we can diverge if needed.

>"exit?...but somehow not have SDDM/kwin_wayland think the session has
ended"

I'm not entirely sure what we'll do, but we'll find something. Super worst
case we leave our process that autostarted everything linger.
For wayland it's easy, kwin becomes the main process and we'll explicitly
tell it to quit when we're finished.
Maybe I can have startup binary fork; the main process becomes ksmserver,
the "forked" version autoloads everything and quits.

....will figure it out when we get there
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20181003/d92bf931/attachment.html>