Description of problem: Had Thunderbird open and right clicked to correct a spelling mistake but no menu box showed up. After a few more right clicks to try and get the menu to show up, GNOME Shell crashed. Version-Release number of selected component: gnome-shell-3.15.91-1.fc22 Additional info: reporter: libreport-2.4.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 4.0.0-0.rc1.git0.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 _g_log_abort at gmessages.c:315 #3 x_io_error at wayland/meta-xwayland.c:344 #4 _XIOError at XlibInt.c:1498 #5 _XEventsQueued at xcb_io.c:366 #6 XPending at Pending.c:55 #7 gdk_check_xpending at gdkeventsource.c:266 #8 gdk_event_source_prepare at gdkeventsource.c:284 #9 g_main_context_prepare at gmain.c:3410 #12 meta_run at core/main.c:437
Created attachment 1000638 [details] File: backtrace
Created attachment 1000639 [details] File: cgroup
Created attachment 1000640 [details] File: core_backtrace
Created attachment 1000641 [details] File: dso_list
Created attachment 1000642 [details] File: environ
Created attachment 1000643 [details] File: limits
Created attachment 1000644 [details] File: maps
Created attachment 1000645 [details] File: open_fds
Created attachment 1000646 [details] File: proc_pid_status
Created attachment 1000647 [details] File: var_log_messages
Another user experienced a similar problem: I was just starting Mozilla Firefox and it logged out. I was faced with the log in screen and even though I had already logged in, what I had opened previously were not open. reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 1864 kernel: 4.0.4-301.fc22.x86_64 package: gnome-shell-3.16.2-1.fc22 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
I experienced the Gnome under Wayland crash also when Firefox window was active trying to see active downloads by clicking the button to the right from the search input.
starting rhythmbox reliably crashes gnome on wayland
*** Bug 1249523 has been marked as a duplicate of this bug. ***
This issue is still present on F23, see bug #1259649
Another user experienced a similar problem: I started a GNOME session on Rawhide (F24) under Wayland, connected to an OpenVPN virtual private network, then attempted to launch the Google Chrome browser. GNOME Shell crashed back to GDM. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 2980 kernel: 4.4.0-0.rc8.git0.1.fc24.x86_64 package: gnome-shell-3.19.3-1.fc24 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 13041
Another user experienced a similar problem: Unclear what exactly caused it, but it was triggered when launching Thunderbird (but this is not repeatable). reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 3200 kernel: 4.4.0-1.fc24.x86_64 package: gnome-shell-3.19.3-1.fc24 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 13041
Another user experienced a similar problem: This problem appeared after I logged in and started to drag and drop applications from the side panel onto the workspace. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 2574 kernel: 4.5.0-0.rc1.git0.1.fc24.x86_64 package: gnome-shell-3.19.4-1.fc24 reason: gnome-shell killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.