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 577756 - gdm ignores .dmrc for "Other" users
gdm ignores .dmrc for "Other" users
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-02 18:52 UTC by amcnabb
Modified: 2009-07-16 21:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description amcnabb 2009-04-02 18:52:18 UTC
Please describe the problem:
If an "Other" user is logging in, gdm ignores the ~/.dmrc file.  This only affects "Other" users--if a user has previously logged in and appears in the menu, their ~/.dmrc will be processed correctly.

This bug has been stagnating on bugzilla.redhat.com for a long time (bug #449107).

Steps to reproduce:
1. click on "Other"
2. type a username that doesn't appear in the list of previously logged in users and hit enter

Actual results:
The default system desktop/language settings are selected.  The ~/.dmrc file is ignored.  If the user logs in, the ~/.dmrc file will be overwritten with the default settings.

Expected results:
Gdm should check ~/.dmrc after the username is entered and before the password is entered.  Gdm should set the desktop/language settings specified by the user in the ~/.dmrc file.

Does this happen every time?
It only happens for "Other" users.  Users that have been previously logged in will find that their ~/.dmrc is correctly processed.

Other information:
I recently tried the Fedora 11 Beta, and although I wasn't paying very close attention, I'm pretty sure that I ran into this bug again.  In other words, I'm pretty sure that 2.26 is still affected by this bug.
Comment 1 amcnabb 2009-04-15 15:46:45 UTC
Fedora added a patch in gdm-2.26.0-7 that addresses the problem.  Is this patch included upstream?
Comment 2 Ray Strode [halfline] 2009-07-16 21:01:43 UTC
yup.