Review Request 118804: Register ksmserver as logind session leader

[Elias Probst]

> On June 22, 2014, 2:54 p.m., Àlex Fiestas wrote:
> > According to Lennart we should not call TakeControl, so I guess that while we wait for kdbus we should discard this review?
> 
> Martin Gräßlin wrote:
>     why? And what does that have to do with kdbus? And how long should we wait for kdbus (my understanding here is that we cannot use kdbus any time soon as Qt won't support it)?

Now that I gained a little more insight into the whole situation, I agree that TakeControl() is not ksmserver's duty - that's up to X.org/Wayland/...

The reason I was seeing the "The session is not registered with logind: "PID 2979 does not belong to any known session"" message was caused by the fact, that I'm running everything as systemd user-session services, which are currently run outside any logind context - they aren't assigned to any systemd-logind session.

I think I can still make some progress on the "Run a Plasma Workspace based on user-session services" without having to wait on memfd/kdbus as there are some "workarounds" on other fronts (e.g. http://cgit.freedesktop.org/polkit/commit/?id=a68f5dfd7662767b7b9822090b70bc5bd145c50c) which could help getting forward.

I'll discard this RR and keep on experimenting further on all this stuff.


- Elias


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118804/#review60716
-----------------------------------------------------------


On June 19, 2014, 7:03 p.m., Elias Probst wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/118804/
> -----------------------------------------------------------
> 
> (Updated June 19, 2014, 7:03 p.m.)
> 
> 
> Review request for Plasma.
> 
> 
> Bugs: 335390
>     https://bugs.kde.org/show_bug.cgi?id=335390
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> -------
> 
> This is an initial (not yet working) attempt to fix bug#335390.
> 
> After some discussion in #systemd, it seems there's some more work needed outside of ksmserver. Will have to figure out the next actions to be taken to continue on this.
> 
> See also my mail on systemd-devel: http://lists.freedesktop.org/archives/systemd-devel/2014-June/020238.html
> 
> 
> Diffs
> -----
> 
>   ksmserver/screenlocker/logind.cpp dcfc7f321b3cf29ef68aac8006aa37f5e4e00956 
> 
> Diff: https://git.reviewboard.kde.org/r/118804/diff/
> 
> 
> Testing
> -------
> 
> - Copy /usr/lib/systemd/system/systemd-logind.service to /etc/systemd/system/systemd-logind.service
> - Set "Environment=SYSTEMD_LOG_LEVEL=debug" in the [Service] section of /etc/systemd/system/systemd-logind.service
> - Run "systemctl daemon-reload"
> - Reboot (also possible without a reboot, but far more complicated and requires to terminate the X session anyways, so a reboot is the most straightforward solution)
> 
> To test
> - apply patch + rebuild plasma-workspace
> - kill ksmserver
> - Run "journalctl -n 20 -f -u systemd-logind" to monitor logind
> - Run "tail -f ~/.xsession-errors" or "journalctl --user -n 20 -f --user-unit ksmserver" (for systemd user-session users) to monitor ksmserver's output
> - restart ksmserver
> 
> 
> Thanks,
> 
> Elias Probst
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140623/2fa50d7d/attachment.html>