Description of problem: Version-Release number of selected component: gnome-shell-3.13.4-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell :0 --wayland --display-server crash_function: meta_clutter_init executable: /usr/bin/gnome-shell kernel: 3.16.0-0.rc6.git3.1.fc21.x86_64 runlevel: 5 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #2 meta_clutter_init at /lib64/libmutter.so.0 #3 meta_wayland_init at /lib64/libmutter.so.0 #4 meta_init at /lib64/libmutter.so.0
Created attachment 921824 [details] File: backtrace
Created attachment 921825 [details] File: cgroup
Created attachment 921826 [details] File: core_backtrace
Created attachment 921827 [details] File: dso_list
Created attachment 921828 [details] File: environ
Created attachment 921829 [details] File: limits
Created attachment 921830 [details] File: maps
Created attachment 921831 [details] File: open_fds
Created attachment 921832 [details] File: proc_pid_status
Created attachment 921833 [details] File: var_log_messages
I guess my system misses some packages but gnome-shell should exit gracefully. And I believe the following journal lines are related to this crash: Jul 28 18:07:00 dhcp-24-107.brq.redhat.com gdm[14891]: GLib-GObject: g_object_set_data: assertion 'G_IS_OBJECT (object)' failed Jul 28 18:07:00 dhcp-24-107.brq.redhat.com gdm[14891]: GLib-GObject: g_object_get: assertion 'G_IS_OBJECT (object)' failed Jul 28 18:07:00 dhcp-24-107.brq.redhat.com gdm[14891]: GLib-GObject: g_object_set_data_full: assertion 'G_IS_OBJECT (object)' failed Jul 28 18:07:00 dhcp-24-107.brq.redhat.com gdm-Xorg-:0[14901]: (II) VMWARE(0): VMMOUSE DEVICE_OFF/CLOSE Jul 28 18:07:00 dhcp-24-107.brq.redhat.com gnome-session[15362]: gnome-session[15362]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed Jul 28 18:07:00 dhcp-24-107.brq.redhat.com gnome-session[15362]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed Jul 28 18:07:01 dhcp-24-107.brq.redhat.com gnome-session[15362]: pci id for fd 10: 1b36:0100, driver (null) Jul 28 18:07:01 dhcp-24-107.brq.redhat.com gnome-session[15362]: pci id for fd 10: 1b36:0100, driver (null) Jul 28 18:07:01 dhcp-24-107.brq.redhat.com gnome-session[15362]: (gnome-shell:15380): Clutter-CRITICAL **: Unable to initialize Clutter: Failed to connected to any renderer: Jul 28 18:07:01 dhcp-24-107.brq.redhat.com gnome-session[15362]: Couldn't create gbm device Jul 28 18:07:01 dhcp-24-107.brq.redhat.com gnome-session[15362]: (gnome-shell:15380): mutter-ERROR **: Unable to initialize Clutter. Jul 28 18:07:01 dhcp-24-107.brq.redhat.com kernel: traps: gnome-shell[15380] trap int3 ip:7fbfc42e3c20 sp:7fff4083c670 error:0
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.