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 586777 - Allow specifying how local X server is started
Allow specifying how local X server is started
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on: 536355
Blocks:
 
 
Reported: 2009-06-23 17:29 UTC by Hans Petter Jansson
Modified: 2018-05-24 10:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
0001-Add-LocalXserverCommand-option-which-lets-you-speci.patch (5.67 KB, patch)
2009-06-23 17:30 UTC, Hans Petter Jansson
rejected Details | Review

Description Hans Petter Jansson 2009-06-23 17:29:29 UTC
In some environments, administrators may want to pass extra options to X or run X from a different location from what gets hardcoded in GDM.

The following patch adds an option that can be used thusly:

[daemon]
LocalXserverCommand=/usr/bin/X -br -verbose 9
Comment 1 Hans Petter Jansson 2009-06-23 17:30:47 UTC
Created attachment 137265 [details] [review]
0001-Add-LocalXserverCommand-option-which-lets-you-speci.patch

Add LocalXserverCommand option, which lets you specify how the local X server should be started.
Comment 2 Brian Cameron 2009-06-24 08:22:21 UTC
I think it might make sense to wait until multi-seat is integrated into ConsoleKit and GDM before adding this sort of feature.  It probably makes most sense to provide the ability to modify the Xserver command for any display, not just the local console display.

Refer to bug #536355.

Halton, do you have any comments about this?
Comment 3 Halton Huo 2009-06-24 08:42:31 UTC
Brian is right. With changes of supporting multi-seat and multi-display, administrators can customize the X command in display type files under <etc>/ConsoleKit/displays.d/

More information, please refer the design document http://wiki.genunix.org/wiki/index.php/design_for_newgdm_consolekit_multiseat_multidisplay

So this bug can be depend on bug #536355.
Comment 4 Hans Petter Jansson 2009-06-24 16:44:44 UTC
That makes sense. Withdrawing my patch then.
Comment 5 Leho Kraav (@lkraav :macmaN) 2012-04-21 22:29:46 UTC
Can someone fill me in on how this thing is doing? Right now I'm running an X instance behind xdm like:

:0 local /usr/bin/X :0 -nolisten tcp -config xorg-6600.conf -novtswitch -sharevts -isolateDevice PCI:0:2:0 vt8

But I'd like to switch to gdm for primarily user switching and better looks. I am up on gdm-3.2.1.1 but have not able to figure out at all how to approach this ever since the old server command options disappeared.
Comment 6 Dmitry Bolkhovityanov 2014-01-03 07:57:07 UTC
Guys, is there any progress on this bug?  Or is there any possibility for it to be fixed? :)
This bug is really-really-really VERY irritating.

BTW, why the status is "UNCONFIRMED"?
Comment 7 John Hodrien 2015-12-11 12:12:22 UTC
I want to pass +iglx to the Xorg run by GLX.  Currently I'm doing this with a wrapper for Xorg, which is a horrible way to solve it.  Is there still no way of doing it?

jh
Comment 8 Mark Visser 2016-08-19 21:56:32 UTC
To add to John's comment:

Recently, Xorg changed its behavior to disallow indirect GLX by default. This means that ssh -X no longer works with OpenGL applications, which is a pretty serious problem.

The only way to re-enable indirect GLX is to pass +iglx to Xorg. However, GDM has no way to pass arbitrary flags to Xorg.

The only workaround is to rename Xorg to Xorg.original and replace it with a wrapper that adds +iglx, e.g.:

#!/bin/bash
exec /usr/bin/Xorg.original "$@" +iglx

(for you kids at home, don't forget to sudo chmod +x /usr/sbin/Xorg)

This is, as John mentions, horrible.

Relevant RHEL bug: https://bugzilla.redhat.com/show_bug.cgi?id=1290777

Also, note that adding a ServerFlags section with AllowIndirectGLXProtocol doesn't work, as the default -iglx of Xorg takes precedent.

Relevant section of nVidia docs: ftp://download.nvidia.com/XFree86/Linux-x86_64/352.63/README/xconfigoptions.html
Comment 9 Feng Gao 2016-09-06 11:17:38 UTC
I want to say a very very very very big THANKS to John and Mark. This solution works perfectly for me.

Many thanks,

P.S.: I've been searching for this solution for weeks.
Comment 10 GNOME Infrastructure Team 2018-05-24 10:21:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/4.