Red Hat Bugzilla – Bug 875537
[abrt] gnome-shell-3.6.1-3.fc18: g_return_if_fail_warning: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
Last modified: 2012-11-12 13:00:28 EST
Description of problem:
1. Install Fedora 18 Beta TC8 with GNOME desktop+development utilities on VMware ESXi 5.0 server (use RHEL 6 container for chosen architecture; I've done both x86 and x64).
2. As soon as you reboot and finish the final firstboot steps you will be told "Oh No! Something has gone wrong!" similar to #860886. The logs indicate that gnome-shell.desktop kept respawning to the point something stops trying to restart it.
This issue has not been seen with a F18 Alpha system upgraded over time (which should have pretty much the same RPMs).
The issue seems to be related to permissions & GNOME. Using KDM/KDE does not hit the "Oh no" problem; starting GNOME via "startx" as root works but not as a normal user (who also sees "Oh no!").
If this is an unrelated crash reported by ABRT to the above I apologize in advance.
Version-Release number of selected component:
libreport version: 2.0.18
:Thread no. 1 (10 frames)
: #5 g_return_if_fail_warning at gmessages.c:1012
: #6 g_str_has_prefix at gstrfuncs.c:2780
: #7 default_log_handler at main.c:272
: #10 dconf_shm_open at dconf-shm.c:63
: #11 dconf_engine_source_user_reopen at dconf-engine-source-user.c:76
: #12 dconf_engine_source_refresh at dconf-engine-source.c:57
: #13 dconf_engine_acquire_sources at dconf-engine.c:201
: #14 dconf_engine_get_state at dconf-engine.c:311
: #15 dconf_engine_watch_fast at dconf-engine.c:762
: #16 g_settings_backend_subscribe at gsettingsbackend.c:886
Potential duplicate bug: 841844
Created attachment 643117 [details]
Created attachment 643118 [details]
Created attachment 643119 [details]
Created attachment 643120 [details]
Created attachment 643121 [details]
Created attachment 643122 [details]
Created attachment 643123 [details]
Created attachment 643124 [details]
Created attachment 643125 [details]
Created attachment 643126 [details]
Created attachment 643163 [details]
gdm :0-greeter.log with errors/exceptions
Watching the blocker review meeting today I discovered this is a duplicate of #810040, and is dependent on if there is a USB bus enabled for the VM or not (which ESXi does not provide by default).
*** This bug has been marked as a duplicate of bug 810040 ***