Version-Release number of selected component: firstboot-18.3-1.fc18.x86_64 Additional info: libreport version: 2.0.12 cmdline: /usr/bin/python /usr/sbin/firstboot kernel: 3.6.0-0.rc6.git0.2.fc18.x86_64
Created attachment 617018 [details] File: other involved packages
Created attachment 617019 [details] File: type
Created attachment 617020 [details] File: environ
Created attachment 617021 [details] File: release
Created attachment 617022 [details] File: hashmarkername
Created attachment 617023 [details] File: firstboot-tb
Created attachment 617024 [details] File: description
Discussed at 2012-09-26 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-09-26/f18-beta-blocker-review-1.2012-09-26-16.03.log.txt . We agreed to delay decision on this one till we have more data. Martin, how did you trigger this?
After further investigation, this looks like a side-effect of Bug#858591. I tried to run firstboot from the terminal with LANG=ja_JP.UTF-8. no errors, but with LANG=ja.UTF-8, it happens.
Created attachment 621011 [details] /var/log/messages showing locale-related messages and a traceback Reproduced by selecting Spanish as the language to be used during the install and for the installed system. /var/log/messages shows locale-related messages from firstboot and metacity and a traceback from firstboot. Procedure: 1. In a VM, boot Fedora-18-Nightly-20120930.12-x86_64-Live-desktop.iso. 2. # yum update anaconda # install latest anaconda in live environment 3. Start the installer from the live desktop. 4. Select Spanish as the language to be used during installation and for the installed system. 5. Reboot into the installed system. Results: 1. firstboot fails to start. 2. The locale files show invalid locales: [root@localhost xfr]# cat /etc/sysconfig/i18n LANG="es.UTF-8" [root@localhost xfr]# cat /etc/locale.conf LANG="es.UTF-8" Version info: anaconda-0:18.11-1.fc18.x86_64 firstboot-18.3-1.fc18.x86_64 Fedora-18-Nightly-20120930.12-x86_64-Live-desktop.iso Command-line: $ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/nightly-composes/Fedora-18-Nightly-20120930.12-x86_64-Live-desktop.iso -vga qxl -boot order=dc,menu=on
I confirm this clearly seems to be a consequence of 858591. 'LC_ALL=es.UTF-8 firstboot' crashes, 'LC_ALL=es_ES.UTF-8 firstboot' runs. Closing this as a dupe of 858591. This also gives us a solid basis to accept 858591 as a blocker. *** This bug has been marked as a duplicate of bug 858591 ***
Created attachment 621069 [details] /var/log/messages when installing in English This may be moot, but it appears that if you install in English, you can get through firstboot and to a desktop despite the invalid en.UTF-8 locale. I'm attaching /var/log/messages from a test install with English as the target language in case someone wants to figure out why ...