http://bugzilla.suse.com/show_bug.cgi?id=1089287 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c2 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags| |needinfo?(werner@suse.com) --- Comment #2 from Fabian Vogt --- (In reply to Dr. Werner Fink from comment #0)

The current configuration in /usr/lib/sddm/sddm.conf.d/00-general.conf misses the option -keeptty to help the systemd-logind to identify the X server on vt7 with its controlling tty

Can this have any unexpected side effects or is it safe to enable it in all cases? I don't think sddm sets the controlling terminal on VT switches, so this might actually break it... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c5 --- Comment #5 from Swamp Workflow Management --- This is an autogenerated message for OBS integration: This bug (1089287) was mentioned in https://build.opensuse.org/request/show/595925 Factory / sddm https://build.opensuse.org/request/show/595926 15.0 / sddm -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c7 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com, | |sndirsch@suse.com Flags|needinfo?(werner@suse.com) |needinfo?(sndirsch@suse.com | |) --- Comment #7 from Dr. Werner Fink --- (In reply to Fabian Vogt from comment #6)

This had the opposite effect: https://openqa.opensuse.org/tests/656629#step/xorg_vt/4

Now ps does not show tty7 for X anymore, while it worked fine previously.

Any idea? I'll revert it for now.

Hmmm ... manual page of Xorg says: -keeptty Prevent the server from detaching its initial controlling terminal. If you want to use systemd-logind integration you must specify this option. Not all platforms support (or can use) this option. ... interesting fact is tath I see here [ 18039.023] (EE) systemd-logind: failed to get session: PID 31661 does not belong to any known session ... in other words this option does not work as it should ... maybe something has been disabled in the X server which does not do the controlling terminal stuff. Btw: Without the option an other error messages appears which shouts that -keeptty option is required -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c9 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sndirsch@suse.com | |) | --- Comment #9 from Stefan Dirsch --- (In reply to Dr. Werner Fink from comment #7)

[ 18039.023] (EE) systemd-logind: failed to get session: PID 31661 does not belong to any known session

... in other words this option does not work as it should ... maybe something has been disabled in the X server which does not do the controlling terminal stuff.

No idea. Andreas Jaeger ran into the same issue after updating his system from 42.3 to 15.0 (forgot about bugzilla number). He didn't run into the issue when installing 42.3 from scratch and then updating his sytem to 15.0. So not so easy to reproduce ... Could be some dbus related issue ... Needs to be debugged on the system. hw/xfree86/os-support/linux/systemd-logind.c static void connect_hook(DBusConnection *connection, void *data) [...] msg = dbus_message_new_method_call("org.freedesktop.login1", "/org/freedesktop/login1", "org.freedesktop.login1.Manager", "GetSessionByPID"); [...] reply = dbus_connection_send_with_reply_and_block(connection, msg, DBUS_TIMEOUT_USE_DEFAULT, &error); if (!reply) { LogMessage(X_ERROR, "systemd-logind: failed to get session: %s\n", error.message); [...] Maybe somebody here known how to use dbus-send, so things could be investigated on the system even without debugging this ...

Btw: Without the option an other error messages appears which shouts that -keeptty option is required

This message has been added with git commit of comment#8. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c10 --- Comment #10 from Franck Bui --- (In reply to Dr. Werner Fink from comment #3)

The EE message about

[ 840.157] (EE) systemd-logind: failed to get session: PID 2837 does not belong to any known session

remains, but this seems to be another problem. There seems to exist a process which already locks the controlling tty on vt7

Hmm it would be interesting to find out the session X server belongs to. You can try "ps -eo cmd,lsession | grep X" or something similar. If X server doesn't have a session, it might be SDDM that hasn't properly set up things before starting the server. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c14 --- Comment #14 from Stefan Dirsch --- Not sure, but gdm is running the Xserver on which the greeter runs as gdm user and the Xserver on which runs the Xsession as regular user. gdm 1427 0.3 2.2 463764 41524 tty7 Sl+ 15:01 0:00 /usr/bin/X vt7 -displayfd 3 -auth /run/user/464/gdm/Xauthority -background none -noreset -keeptty -verbose 3 tux 1922 0.2 2.2 464060 41660 tty2 Sl+ 15:02 0:00 /usr/bin/X vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 I don't believe NVIDIA has special requirements here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c16 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #16 from Fabian Vogt --- I tried to debug this further, the issue is that sddm doesn't actually create a session and set a controlling tty. That's currently done by the X server. This explains why -keeptty does not work and also why loginctl doesn't show vt7. sddm only calls setsid for the user session, but as there's no X server in the user session it doesn't get a controlling terminal either. While looking at lightdm to check how it's done properly I noticed that it has the exact same issue. What does sddm need to do to work with -keeptty? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c18 --- Comment #18 from Fabian Vogt --- (In reply to Dr. Werner Fink from comment #17)

(In reply to Fabian Vogt from comment #16)

...

I tried to debug this further, the issue is that sddm doesn't actually create a session and set a controlling tty. That's currently done by the X server. This explains why -keeptty does not work and also why loginctl doesn't show vt7.

sddm only calls setsid for the user session, but as there's no X server in the user session it doesn't get a controlling terminal either.

While looking at lightdm to check how it's done properly I noticed that it has the exact same issue.

What does sddm need to do to work with -keeptty?

How does gdm solve this problem? AFAICR the -keeptty option should avoid deteaching the controlling terminal by the X server. But here it is not connectted to the tty7 anymore:

ps aux | grep bin/ root 2176 0.5 0.8 499472 70108 ? Sl Jul02 60:21 /usr/bin/X -nolisten tcp -keeptty -auth /run/sddm/{ac43390f-4fcf-4711-b111-99f6c749eb82} -background none -noreset -displayfd 17 -seat seat0 vt7

somehow strange. It seems that the option -keeptty does not work here. The question rises if this is how sddm/lightdm are starting the X server and how this differs from the method used by gdm.

gdm starts the X server rootless by default while lightdm and sddm don't. So gdm has: gdm -> greeter-helper -> greeter \ \ \ > X \ > user-helper -> user-session \ > X I assume here greeter-helper and user-helper are session leaders and have a controlling tty each. While sddm and lightdm don't start it rootless: sddm/lightdm -> greeter |\ \ > X > user-session sddm/lightdm can manage more than one tty, so they can't have a single controlling tty, by design. The user-session and X are siblings, so they can't be session leaders of their own session. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c20 --- Comment #20 from Fabian Vogt --- I monitored the dbus traffic - the VTs are still assigned to the session and "loginctl activate" works as expected. So I assume this is not actually an issue? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c22 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msrb@suse.com) | --- Comment #22 from Michal Srb --- AFAIK the systemd-logind integration in X server is only meaningful when the X server runs with the regular user's permissions inside the user's session. This is currently only the case with GDM. SDDM starts the X server as root. In this case you can consider the X server as a system process. It is not tied to the user session that it displays - the same X server may display the greeter and later the user session as well. That's why X shows the error:

[ 840.157] (EE) systemd-logind: failed to get session: PID 2837 does not belong to any known session

It tries to find session that belongs to its own PID and that fails. If -keeptty is not set, X server doesn't even try to use the systemd-logind integration. If it is set, it tries and fails. What is actually the motivation for adding the -keeptty parameter? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c24 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | --- Comment #24 from Dr. Werner Fink --- (In reply to Stefan Dirsch from comment #23)

(In reply to Michal Srb from comment #22)

...

What is actually the motivation for adding the -keeptty parameter?

Werner?

The explicit warning of the login manager of systemd about missing -keeptty -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sndirsch@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1089287 http://bugzilla.suse.com/show_bug.cgi?id=1089287#c27 --- Comment #27 from Dr. Werner Fink --- (In reply to Michal Srb from comment #26)

(In reply to Dr. Werner Fink from comment #24)

...

The explicit warning of the login manager of systemd about missing -keeptty

Can you please quote it and help me where I can find it? I have a Tumbleweed machine with SDDM here, but can't find such warning in any logs so far.

The X server throws this: systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration -- You are receiving this mail because: You are on the CC list for the bug.

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.