Description of problem: Version-Release number of selected component: gnome-shell-3.13.91-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell kernel: 3.16.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 meta_window_ungrab_all_keys at core/keybindings.c:1616 #1 meta_display_end_grab_op at core/display.c:1914 #2 meta_window_x11_client_message at x11/window-x11.c:2511 #3 handle_other_xevent at x11/events.c:1460 #4 meta_display_handle_xevent at x11/events.c:1727 #5 xevent_filter at x11/events.c:1766 #6 gdk_event_apply_filters at gdkeventsource.c:81 #7 gdk_event_source_translate_event at gdkeventsource.c:195 #8 _gdk_x11_display_queue_events at gdkeventsource.c:338 #9 gdk_display_get_event at gdkdisplay.c:321
Created attachment 939201 [details] File: backtrace
Created attachment 939202 [details] File: cgroup
Created attachment 939203 [details] File: core_backtrace
Created attachment 939204 [details] File: dso_list
Created attachment 939205 [details] File: environ
Created attachment 939206 [details] File: exploitable
Created attachment 939207 [details] File: limits
Created attachment 939208 [details] File: maps
Created attachment 939209 [details] File: open_fds
Created attachment 939210 [details] File: proc_pid_status
Created attachment 939211 [details] File: var_log_messages
Another user experienced a similar problem: During use of Evolution, Firefox and virt-manager. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell kernel: 3.17.0-0.rc5.git5.2.fc22.1.x86_64 package: gnome-shell-3.13.92-1.fc21 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: Occurs when I choose a device for sound input reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell kernel: 3.17.2-300.fc21.x86_64 package: gnome-shell-3.14.2-1.fc21 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Had same problem here during use of VirtualBox, Firefox and some more open applications.
I get this error when I 1. run virtual machine (in virt-manager in qemu user mode). 2. press Super+Tab (maybe alt tab) to get from window with virtual machine to another window Since if mouse is "inside" virtual machine display, alt+tab goes inside, I often have to move mouse outside VM display (usually somewhere near virt-manager menu) and try alt+tab again. Most times it works, but today gnome-shell crashed three times during that.
I got this error after starting a VM through virt-manager and pressing Alt+Tab. I'm not sure if the crash is directly related to running the VM, though. Gnome-shell crashes on occasion when pressing Alt+Tab while the system is under loda.
Another user experienced a similar problem: Played a Video (MP4) in Totem Music Player. Video Runns, but while clicking somewhere or jumping forward in the video, causes the crash reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell kernel: 3.18.3-201.fc21.x86_64 package: gnome-shell-3.14.3-1.fc21 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I've seen this too on F21. I've filed it upstream. If you are able to reproduce the crash easily (in particular while using virt-manager, as several people said), it would be good to state it.
I know it's an upstream bug but it's still not fixed in Fedora, so why is it closed?
See the description of UPSTREAM at https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status
Milan: that is the Red Hat bug workflow (mainly for RHEL development). It does not entirely apply to Fedora. Fedora's (official) bug workflow is https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow , where UPSTREAM is defined thus: "The resolution UPSTREAM can be used by maintainers to denote a bug that they expect to be eventually fixed by upstream development and naturally rolled back into Fedora as part of the update process. Ideally, a comment should be added with a link to the upstream bug report." A *maintainer* can choose to close a Fedora bug as UPSTREAM if they don't think it necessary to track it downstream and are happy with it getting fixed 'organically' as described there, but this is not supposed to be done by anyone else. Since (AFAICT) you're not a maintainer of the Fedora gnome-shell package, I'll take the liberty of re-opening the bug.
Ah, thanks, the Status link is certainly confusing then... (Either way, I don't think it really makes a difference as regards the resolution of the bug, though.)
sadly it's kind of a limitation of sharing a bugzilla :/ There is actually some text right at the top of the fields.html page which says: "Note: Bugs reported against Fedora products have a slightly different life cycle which is described in more detail here. " but when you hit a link with an anchor, that's off the top of the screen and you don't see it...
This often occurs when having an RDP session open to a Windows box using Vinagre in windowed mode and using Alt-Tab to try to switch away from it.
Another user experienced a similar problem: None reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell kernel: 3.17.7-300.fc21.x86_64 package: gnome-shell-3.14.3-1.fc21 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1254074 has been marked as a duplicate of this bug. ***
*** Bug 1182520 has been marked as a duplicate of this bug. ***
Updating version to F23 since it's still occurring with the F23 beta
Another user experienced a similar problem: gitg crashed, and gnome-shell followed him. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell global_pid: 2150 kernel: 4.1.10-200.fc22.x86_64 package: gnome-shell-3.16.3-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1279031 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Apparently leaving the computer turned on for many days doesn't it happy. It hanged and crash report appeared after I poke the upper left corner to access folders. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_ungrab_all_keys executable: /usr/bin/gnome-shell global_pid: 1939 kernel: 4.2.6-200.fc22.x86_64 package: gnome-shell-3.16.4-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.