http://bugzilla.suse.com/show_bug.cgi?id=1089287
http://bugzilla.suse.com/show_bug.cgi?id=1089287#c28
Michal Srb changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INVALID
--- Comment #28 from Michal Srb ---
I see. This is only informative message, not even warning. X server always
tries to enable systemd-logind integration and it will print message like this
when it is not possible.
The systemd-logind integration in X server does the following:
1) X server will find the session it belongs to using
"org.freedesktop.login1.Manager.GetSessionByPID" method.
2) It will set itself as the controller for the session using
"org.freedesktop.login1.Session.TakeControl" method.
3) It will react to "PauseDevice"/"ResumeDevice" events.
AFAIK this whole thing only makes sense when the X server is running its whole
lifetime inside one session of one specific user. This is the case when
launched by GDM, but not (yet) when launched by SDDM, XDM or any others.
With SDDM the X server runs as root and the same instance is used for both the
greeter session and then for the user session. So it can not become the
controller for them. There would have to be some mechanism to signal to it that
it stopped displaying X clients from one session and started displaying X
clients from the other session, in order for it to release control of one
session and take control of the other. But there is no such mechanism and
likely never will be - the future is doing it the GDM way and start separate X
server for each session.
So when SDDM gets the ability to run X server under the user's account, just
like GDM does, then it should pass the -keeptty. Until then it is correct to
not pass it.
--
You are receiving this mail because:
You are on the CC list for the bug.