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 779338 - provide a way to turn off the user run display server
provide a way to turn off the user run display server
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-02-27 22:04 UTC by Ray Strode [halfline]
Modified: 2017-09-18 05:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdm-session: change how session search path is computed (3.72 KB, patch)
2017-02-27 22:04 UTC, Ray Strode [halfline]
committed Details | Review
daemon: add knob to disable starting X server as user (13.71 KB, patch)
2017-02-27 22:04 UTC, Ray Strode [halfline]
committed Details | Review
session: honor ignore-wayland flag (2.71 KB, patch)
2017-03-03 18:35 UTC, Ray Strode [halfline]
committed Details | Review

Description Ray Strode [halfline] 2017-02-27 22:04:13 UTC
Running the X server as a user is a great step forward, but it's not completely
backward compatible.  This bug is to track adding a configure option to force
the old way in situations where that's important.
Comment 1 Ray Strode [halfline] 2017-02-27 22:04:27 UTC
Created attachment 346872 [details] [review]
gdm-session: change how session search path is computed

The current mechanism of assuming the wayland-sessions path is
the first element of the array isn't very conducive to reprioritizing
wayland sessions.  This commit changes the code to use a GArray instead.
Comment 2 Ray Strode [halfline] 2017-02-27 22:04:31 UTC
Created attachment 346873 [details] [review]
daemon: add knob to disable starting X server as user

Some deployments need to be able to turn off running X servers as a
user for backward compatibility.

This commit adds some #ifdef goop to that end.

Note wayland requires running as the user, so this option, merely
deprioritizes wayland sessions under X sessions.
Comment 3 Ray Strode [halfline] 2017-02-27 22:05:24 UTC
Attachment 346872 [details] pushed as 5b1e625 - gdm-session: change how session search path is computed
Attachment 346873 [details] pushed as 22de251 - daemon: add knob to disable starting X server as user
Comment 4 Maxim 2017-03-03 15:43:12 UTC
(In reply to Ray Strode [halfline] from comment #1)
> Created attachment 346872 [details] [review] [review]
> gdm-session: change how session search path is computed
> 
> The current mechanism of assuming the wayland-sessions path is
> the first element of the array isn't very conducive to reprioritizing
> wayland sessions.  This commit changes the code to use a GArray instead.

After that commit I can't login anymore. If I change GNOME Xorg instead of GNOME, then login normal. But after restart it is always selected GNOME in GDM and I have only black screen.

Booting with NVIDIA proprietary driver + KMS and uncommented WaylandEnable=false.

Only helpы for me is pressing Alt+SysRq+K and changing to GNOME Xorg in GDM.
Comment 5 Ray Strode [halfline] 2017-03-03 18:35:00 UTC
Created attachment 347161 [details] [review]
session: honor ignore-wayland flag

commit 5b1e625417c274823c66a552f37d912986fc34d8 changed how the
default session path was computed. It inadvertently dropped
support for the ignore-wayland flag, breaking fall back to X in
scenarios where wayland doesn't work.

This commit fixes the code to again honor ignore-wayland.
Comment 6 Ray Strode [halfline] 2017-03-03 18:37:18 UTC
Comment on attachment 347161 [details] [review]
session: honor ignore-wayland flag

Sorry about that! Thanks for the quick feedback letting me know.

Attachment 347161 [details] pushed as 0f693f5 - session: honor ignore-wayland flag
Comment 7 Maxim 2017-03-03 20:21:54 UTC
(In reply to Ray Strode [halfline] from comment #6)

> Sorry about that! Thanks for the quick feedback letting me know.

Thanks.Now it's working again. 

Please add this fix to 3.22 branch, because it happend with stable GNOME 3.22.