Bug 919855

Created attachment 707898 [details]
File: backtrace

Created attachment 707899 [details]
File: cgroup

Created attachment 707900 [details]
File: core_backtrace

Created attachment 707901 [details]
File: dso_list

Created attachment 707902 [details]
File: environ

Created attachment 707903 [details]
File: limits

Created attachment 707904 [details]
File: maps

Created attachment 707905 [details]
File: open_fds

Created attachment 707906 [details]
File: proc_pid_status

Created attachment 707907 [details]
File: smolt_data

Created attachment 707908 [details]
File: var_log_messages

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

While starting GDM, 
[   23.864630] dconf worker[1016]: segfault at 3ed1 ip 00007fb77031f72d sp 00007fb760e6e6a0 error 4 in libc-2.17.so[7fb7702e7000+1b5000]
$ systemctl status gdm.service 
gdm.service - GNOME Display Manager
	  Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
	  Active: active (running) since 토 2013-04-06 09:41:37 KST; 25min ago
	Main PID: 440 (gdm)
	  CGroup: name=systemd:/system/gdm.service
		  ├─ 440 /usr/sbin/gdm
		  ├─ 457 /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0
		  ├─ 492 /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-mmIo08/database -seat seat0 -nolisten tcp vt1
		  └─1254 gdm-session-worker [pam/gdm-password]

 4월 06 09:41:37 localhost systemd[1]: Started GNOME Display Manager.
 4월 06 09:41:41 localhost gdm[440]: Failed to give slave programs access to the display. Trying to proceed.
 4월 06 09:41:43 localhost gdm[440]: GLib: g_variant_compare: assertion `!g_variant_is_container (a)' failed
 4월 06 09:41:43 localhost gdm[440]: GLib: g_variant_compare: assertion `!g_variant_is_container (a)' failed
 4월 06 09:43:45 localhost gdm[440]: Failed to remove slave program access to the display. Trying to proceed.

backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: getenv
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.8.5-201.fc18.x86_64
package:        gnome-settings-daemon-3.8.0-1.fc19
reason:         Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
uid:            42
ureports_counter: 1

Installed a default F19 Beta Live x86_64 installations. First boot was fine. Second boot was just a black screen instead of gdm. Switched to tty2 and found this crash.

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: getenv
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.9.2-301.fc19.x86_64
package:        gnome-settings-daemon-3.8.2-1.fc19
reason:         Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
reported_to:    uReport: BTHASH=1f95e23ce4c9702e2184975f41ca6b01fd92667f
runlevel:       unknown
uid:            42

I saw this twice in 10 reboots in a VM for a freshly installed F19 Beta x86_64. I think that warrants a blocker bug discussion.

I am also hitting this (once in less than 10 reboots so far) on my laptop.

Discussed at 2013-05-30 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-30/f19final-blocker-review-1.1.2013-05-30-16.02.log.txt . We're definitely concerned about this one but we'd like some input from the developers on how widespread it's likely to be before definitely calling it a blocker.

From IRC:

<hadess> #0  __GI_getenv (name=0x38d7b7a989 "NGUAGE", name@entry=0x38d7b7a987 "LANGUAGE") at getenv.c:89
<hadess> adamw, it's memory corruption, the backtrace is unusable
 adamw, and if it isn't, it's crashing in gettext

kparal will try to provide a clean backtrace in an hour or two.

Created attachment 755012 [details]
abrt backtrace

I re-generated all abrt crash data (thank you, gnome-abrt -x), here it is.

We now have a report and a theory about what's going wrong upstream.

From upstream:

"Yeah, set_locale_env() can't be called after gtk_init() (which probably does
gsettings -> dconf -> gdbus -> thread)

See https://bugzilla.gnome.org/show_bug.cgi?id=659326 for more information
about why you can only call setenv() before creating threads."

So it sounds to me like this is a straight up coding error and could fail kind anywhere, anytime. If that's the case I'm +1 blocker.

"anywhere, anytime"

its a race condition, not that easy to hit, but sure, we should fix it

well, I meant it doesn't seem to be tied to some specific hardware/software configuration, but anyone could hit this if they happen to lose the race.

Discussed at 2013-06-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-03/f19final-blocker-review-2.2013-06-03-16.00.log.txt . Accepted as a blocker per https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria#Expected_installed_system_boot_behavior : "After firstboot is completed and on subsequent boots, a graphical install must boot to a log in screen where it is possible to log in to a working desktop as the user created during firstboot."

gnome-settings-daemon-3.8.3-2.fc19, gnome-shell-3.8.3-1.fc19, mutter-3.8.3-1.fc19, control-center-3.8.3-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gnome-shell-3.8.3-1.fc19,mutter-3.8.3-1.fc19,gnome-settings-daemon-3.8.3-2.fc19,control-center-3.8.3-1.fc19

Package gnome-settings-daemon-3.8.3-2.fc19, gnome-shell-3.8.3-1.fc19, mutter-3.8.3-1.fc19, control-center-3.8.3-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-settings-daemon-3.8.3-2.fc19 gnome-shell-3.8.3-1.fc19 mutter-3.8.3-1.fc19 control-center-3.8.3-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-10587/gnome-shell-3.8.3-1.fc19,mutter-3.8.3-1.fc19,gnome-settings-daemon-3.8.3-2.fc19,control-center-3.8.3-1.fc19
then log in and leave karma (feedback).

gnome-settings-daemon-3.8.3-2.fc19, gnome-shell-3.8.3-1.fc19, mutter-3.8.3-1.fc19, control-center-3.8.3-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.