Created attachment 659490 [details] The relevant login is at +6470.19s and the relevant language selection log is at +6514.97s Description of problem: selecting any language different than the system-wide locale in the lightdm greeter fails to set that language on the desktop. Version-Release number of selected component (if applicable): lightdm.i686 1.4.0-2.fc18 @updates-testing lightdm-gobject.i686 1.4.0-2.fc18 @updates-testing lightdm-gtk.i686 1.3.1-1.fc18 @fedora How reproducible: tried only once after knowing that Debian had this issue. Steps to Reproduce: 1. set 'show-language-selector=true' in /etc/lightdm/lightdm-gtk-greeter.conf 2. choose some language other than the one set in /etc/locale.conf in the greeter 3. login Actual results: desktop (tried only with Xfce yet) is using system-wide language Expected results: desktop using the language selected in the greeter Additional info: /var/log/lightdm.log does log the language selection but for some reason it isn't applied.
The attached lightdm.log had a previous login then a logout/lightdm restart at +6470.19s
I'll speculate a bit as the PAM thing is way beyond my knowledge but it seems here is the most appropriate place to discuss the issue. Today I was testing the Xfce spin and while running it I replaced lightdm for lxdm. LXDM has a language selector and it worked just fine. So it may be some un-related code bug but since lightdm.log actually logs the language change and it doesn't work then I thought that maybe it 'could' be some permission issue. Also we get this errors in /var/log/messages: Dec 11 11:17:38 fedora dbus-daemon[461]: dbus[461]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.15" (uid=43 pid=693 comm="/usr/sbin/lightdm-gtk-greeter ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.13" (uid=0 pid=628 comm="/usr/sbin/console-kit-daemon --no-daemon ") Dec 11 11:17:38 fedora dbus[461]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.15" (uid=43 pid=693 comm="/usr/sbin/lightdm-gtk-greeter ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.13" (uid=0 pid=628 comm="/usr/sbin/console-kit-daemon --no-daemon ") I'll attach /etc/pam.d/[lightdm/lxdm/lightdm-greeter] just for comparison convenience. If all this is complete nonsense then just disregard it :-)
Created attachment 661606 [details] /etc/pam.d/lxdm
Created attachment 661609 [details] /etc/pam.d/lightdm
Created attachment 661610 [details] /etc/pam.d/lightdm-greeter
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.