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 577227 - gdm does not run multiple X servers
gdm does not run multiple X servers
Status: RESOLVED DUPLICATE of bug 536355
Product: gdm
Classification: Core
Component: general
2.26.x
Other All
: Normal major
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-29 20:16 UTC by Dobai Balint
Modified: 2010-04-26 17:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Dobai Balint 2009-03-29 20:16:50 UTC 
Please describe the problem:
<=gdm-2.20.9 was able to interpret the following custom.conf part:
[servers]
0=Standard
1=2nd

[server-Standard]
name=Standard server
command=/usr/bin/X -ac -br

[server-2nd]
name=Second server
command=/usr/bin/X :1 -ac -br -layout Second -sharevts -novtswitch

just upgraded to 2.26 and there is no second login on my second monitor
and my fist X is not run by the parameters i specified.
there is no documentation about the config changes.
i found on google, gdm 2.24/2.26 still respects custom.conf

Steps to reproduce:
1. upgrade gdm

Actual results:
missing functionality

Expected results:
bugfixes, new features

Does this happen every time?


Other information:
Comment 1 Brian Cameron 2009-03-30 17:55:27 UTC 
Although GDM 2.22 and later does support some configuration from custom.conf, it doesn't have multi-display support.  We are currently working to address this regression, but the fix isn't yet in 2.26.

Note bug #536355.  By patching GDM to support gdmdynamic, you can get multi-display support to work by calling the gdmdynamic interface.  That might be a workaround for now.
Comment 2 André Klapper 2009-03-30 19:41:57 UTC 
Not a blocker.
Comment 3 Brian Cameron 2010-04-26 17:48:11 UTC 
Marking as a duplicate of 536355.

*** This bug has been marked as a duplicate of bug 536355 ***