After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 787943 - force a session bus for non-seat0 session
force a session bus for non-seat0 session
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2017-09-20 13:51 UTC by Ray Strode [halfline]
Modified: 2017-09-20 20:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdm-x-session: force a session bus for non-seat0 session (9.29 KB, patch)
2017-09-20 13:51 UTC, Ray Strode [halfline] 		rejected Details | Review
session-worker: only jump to VT on seat0 (5.64 KB, patch)
2017-09-20 18:47 UTC, Ray Strode [halfline] 		committed Details | Review
gdm-sessions: force a session bus for non-seat0 session (4.01 KB, patch)
2017-09-20 18:47 UTC, Ray Strode [halfline] 		none Details | Review
gdm-sessions: force a session bus for non-seat0 session (4.01 KB, patch)
2017-09-20 19:28 UTC, Ray Strode [halfline] 		committed Details | Review

Description Ray Strode [halfline] 2017-09-20 13:51:03 UTC 
Eventually, our software should become "multi-seat aware",
where it takes into account multiple seats at a time
for the user (even if it's just putting up a dialog saying
"user is busy" on all but one seat).

We're not there yet. And user bus currently breaks XDMCP
(which should really spawn session with it's own separate user,
 but again, we're not there yet).

This commit changes GDM to start a session bus for all non-seat0
displays, as a near-term workaround.
Comment 1 Ray Strode [halfline] 2017-09-20 13:51:10 UTC 
Created attachment 360132 [details] [review]
gdm-x-session: force a session bus for non-seat0 session
Comment 2 Ray Strode [halfline] 2017-09-20 18:46:56 UTC 
Review of attachment 360132 [details] [review]:

we don't use gdm-x-session for non-seat0 sessions, duh.
Comment 3 Ray Strode [halfline] 2017-09-20 18:47:51 UTC 
Created attachment 360149 [details] [review]
session-worker: only jump to VT on seat0

seat0 is the only seat that supports VTs, so don't ever try to
change VTs if not on seat0.
Comment 4 Ray Strode [halfline] 2017-09-20 18:47:55 UTC 
Created attachment 360150 [details] [review]
gdm-sessions: force a session bus for non-seat0 session

Eventually, our software should become "multi-seat aware",
where it takes into account multiple seats at a time
for the user (even if it's just putting up a dialog saying
"user is busy" on all but one seat).

We're not there yet. And user bus currently breaks XDMCP
(which should really spawn session with it's own separate user,
 but again, we're not there yet).

This commit changes GDM to start a session bus for all non-seat0
displays, as a near-term workaround.
Comment 5 Ray Strode [halfline] 2017-09-20 19:28:47 UTC 
Created attachment 360151 [details] [review]
gdm-sessions: force a session bus for non-seat0 session

Eventually, our software should become "multi-seat aware",
where it takes into account multiple seats at a time
for the user (even if it's just putting up a dialog saying
"user is busy" on all but one seat).

We're not there yet. And user bus currently breaks XDMCP
(which should really spawn session with its own separate user,
 but again, we're not there yet).

This commit changes GDM to start a session bus for all non-seat0
displays, as a near-term workaround.
Comment 6 Ray Strode [halfline] 2017-09-20 20:07:33 UTC 
Attachment 360149 [details] pushed as 85d23a4 - session-worker: only jump to VT on seat0
Attachment 360151 [details] pushed as 2b52d89 - gdm-sessions: force a session bus for non-seat0 session