Bug 694859

Summary:	GDM sometimes resets the gnome-session language to English (United States)
Product:	[Fedora] Fedora	Reporter:	Jean-François Fortin Tam <nekohayo>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15	CC:	abetakehiko, jmccann, rstrode, vaughn.jayson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-06 16:19:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jean-François Fortin Tam 2011-04-08 16:08:19 UTC

Initially filed at https://bugzilla.gnome.org/show_bug.cgi?id=645478


In the "Region and Language" panel in gnome-control-center, I selected "French (Canada)" as my language.

However, after restarting the computer completely, it is reset back to "English (United States)". In addition, the xdg user dirs gtk helper thingy will ask you to update the XDG folder names everytime the locale changes...

Note that I am not using autologin.


There are two types of scenarios:
1) [bad]  gdm doesn't present me with a list of users, it only shows "Other" allowing me to type the user name and password; and that's when it forces the English localization and keyboard layout.

2) [good] gdm does show my user account with its associated image. At those times, the Canadian French locale and Canada French Dvorak keyboard layout seem to be correctly set at login.



Steps to Reproduce: 
- You can toggle between the two scenarios simply by logging in/out multiple times.
- This bug can also be reproduced semi-randomly at reboot.

I'm suspecting a race condition of some sort in gdm (or maybe in Fedora's boot process, but I think it sometimes happen on user logout, so it might not be systemd's fault).

Comment 1 Fedora Admin XMLRPC Client 2011-06-21 15:30:30 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2011-06-21 15:32:24 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2011-06-21 15:35:07 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2011-06-21 15:38:22 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2011-06-21 15:48:03 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora Admin XMLRPC Client 2011-06-21 15:50:28 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora Admin XMLRPC Client 2011-06-21 15:52:45 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 8 Fedora Admin XMLRPC Client 2011-06-21 15:53:57 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 9 Jayson Vaughn 2011-07-03 05:19:51 UTC

Hello,
Thank you for your bug report.  Can you please provide us with the following info to help us troubleshoot this issue further:

1) Current rpm version of gdm (rpm -q gdm)
2) /var/log/gdm/:0-greeter.log after you produce the problem
3) /var/log/gdm/:0.log after you produce the problem
4) /etc/X11/xorg.conf.d/00-system-setup-keyboard.conf after your produce the problem

Thanks.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 10 Jean-François Fortin Tam 2011-07-06 16:19:10 UTC

I haven't experienced this bug in a while, so I can't really reproduce it now. I guess it must have been fixed somewhere along the way.