Bug 712612
Summary: | [abrt] gnome-shell-3.0.2-1.fc15: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | gabicr | ||||||||
Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 30 | CC: | andrea.vai, boost113, brian, bugzilla, chris, cunio, fedora, fran, gab-redhat, gael, jakob, jkonecny, jonathan.eidsness, j.stienlet, kaf.laarous, komusubi, louis, maxamillion, otaylor, samkraju, sjcchaochn, tarcisio.surdi, ttys3.rust, ultrabyte, walters | ||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||
Target Release: | --- | ||||||||||
Hardware: | i686 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:6b2078f60dbccd3f894fcb7ee591715b23505943 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2020-05-26 17:50:43 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
gabicr
2011-06-11 19:03:32 UTC
Created attachment 504265 [details]
File: event_log
Created attachment 504266 [details]
File: maps
Package: gnome-shell-3.0.2-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- i'm not remomber Clicked on "applications" and quickly clicked on a program in the sidebar rating: 4 Package: gnome-shell-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Abrt is showing this bug as a duplicate of F28 gnome-shell crashes! The coredump is 1.6GB so it is not getting uploaded to the retrace server. Hello, Just got "this" bug in gnome-shell too (problem N°1), and same problem as Jens with Abrt wrongly assigning gnome's crash on fedora 28 to this 6(!) year old thread (problem N°2)...(perhaps abrt could check the fedora version before deciding a bug is a duplicate of another bug?) Anyway I'm willing to upload a core dump, but it seems the bug reporting system has another problem too (problem N°3)(screenshot https://drive.google.com/open?id=1oHRfgZBrNIbmJ-L4APu4BqK7pa_LcoZk ). If you want to I can send a copy of gnome shell's core dump on a USB key to somebody. Or I can keep the data until Abrt's problems are solved, and upload it? (In reply to Joel Stienlet from comment #7) > Hello, > Just got "this" bug in gnome-shell too (problem N°1), and same problem as > Jens with Abrt wrongly assigning gnome's crash on fedora 28 to this 6(!) > year old thread (problem N°2)...(perhaps abrt could check the fedora version > before deciding a bug is a duplicate of another bug?) > Anyway I'm willing to upload a core dump, but it seems the bug reporting > system has another problem too (problem N°3)(screenshot > https://drive.google.com/open?id=1oHRfgZBrNIbmJ-L4APu4BqK7pa_LcoZk ). > If you want to I can send a copy of gnome shell's core dump on a USB key to > somebody. Or I can keep the data until Abrt's problems are solved, and > upload it? You may want to use `coredumpctl gdb` on the crash and export it from the console. Then create a new bug report against gnome-shell (after checking for duplicates, of course). I recommend you also report a bug against abrt/libreport. I also have this problem on F28 x86_64 running NVidia's current drivers. ABRT behaves as below: --- Running report_uReport --- ('report_uReport' completed successfully) --- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings Retrace server can not be used, because the crash is too large. Try local retracing. The size of your crash is 1.7 GiB, but the retrace server only accepts crashes smaller or equal to 1.2 GiB. Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES' Analyzing coredump 'coredump' Missing build id: libnvidia-glcore.so.390.77 Missing build id: libnvidia-tls.so.390.77 Missing build id: libGLX_nvidia.so.0 Missing build id: libnvidia-egl-wayland.so.1 Missing build id: libnvidia-glsi.so.390.77 Missing build id: libEGL_nvidia.so.0 All debuginfo files are available Generating backtrace Backtrace is generated and saved, 93624 bytes --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla Duplicate bugzilla bug '#712612' was found Searching for updates No updates for this package found Still getting it I aslo getting it journalctl -r 9月 20 01:42:31 fedora gnome-shell[1896]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 17871 error_code 3 request_code 18 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Still getting this - Fedora 28 and NVidia 3.90 driver --- Running report_uReport --- ('report_uReport' completed successfully) --- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings Retrace server can not be used, because the crash is too large. Try local retracing. The size of your crash is 1.5 GiB, but the retrace server only accepts crashes smaller or equal to 1.2 GiB. Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES' Analyzing coredump 'coredump' Missing build id: libnvidia-glcore.so.390.87 Missing build id: libnvidia-tls.so.390.87 Missing build id: libGLX_nvidia.so.0 Missing build id: libnvidia-egl-wayland.so.1 Missing build id: libnvidia-glsi.so.390.87 Missing build id: libEGL_nvidia.so.0 All debuginfo files are available Generating backtrace Backtrace is generated and saved, 89443 bytes --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla Duplicate bugzilla bug '#712612' was found Searching for updates No updates for this package found Almost ever time I enter my password to unlock the lock screen I Gnome Shell crashes and I get this report generated. When my gnome session crasher, ABRT told me it was a duplicate of this bug. At the time of the crash I was trying to save a file on a network share. I am running Fedora 29. Fedora 31, also ABRT pointing me here. Re open it and set it to F30, because I get an crash which will point to it. In my case it was happens changing the font Hinting. This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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. Could this bug be reopened for Fedora 36? Over the past month I've been getting random gnome-shell crashes sometimes when my monitors come back after being off when an email notification or something like that is attempted to be displayed. I now tried to report this through ABRT but it said it produced non-useful stacktrace, but it said "abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#712612' was found" which is why I'm commenting here. Here's another link ABRT gives me: https://retrace.fedoraproject.org/faf/reports/484644/ This issue didn't seem to happen when I picked older kernels, but I've now updated so many times after this issue first happened that I can no longer go back to a kernel version that doesn't cause this crash. F37 user here. got the same bug F37, hit this bug again --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#712612' was found Searching for updates https://retrace.fedoraproject.org/faf/reports/544997/ F37 user here, getting appear to be hitting this issue whenever I attempt to wake the displays. Attempted to report, but getting the same Duplicate bug / non-informational message as above. Same here, but from https://retrace.fedoraproject.org/faf/reports/630445/ and can't change the status for reopen or change version. F37 user. got this issue. F38 user. again ... --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#712612' was found Searching for updates No updates for this package found User Logs: --work gnome-shell[734942]: Failed to lock front buffer on /dev/dri/card0: gbm_surface_lock_front_buffer failed work gnome-shell[734942]: Failed to lock front buffer on /dev/dri/card0: gbm_surface_lock_front_buffer failed work gnome-shell[734942]: ** work gnome-shell[734942]: libmutter:ERROR:../src/backends/native/meta-onscreen-native.c:196:meta_onscreen_native_notify_frame_complete: assertion failed: (!cogl_onscreen_peek_head_frame_info (onscreen)) work gnome-shell[734942]: Bail out! libmutter:ERROR:../src/backends/native/meta-onscreen-native.c:196:meta_onscreen_native_notify_frame_complete: assertion failed: (!cogl_onscreen_peek_head_frame_info (onscreen)) work gnome-shell[734942]: == Stack trace for context 0x557a45a00d10 == -- hit this today, F38 just after upgrade form F37, multi-display setup, resume from suspend to RAM Fedora 38, just had this issue when joining a Zoom meeting in fullscreen... Still present in F38 ! How to raise this issue : 1. connect airpods 2. select airpods free hands mode from Sound settings in Gnome Settings 3. select airpods headphone from sound volume output selector in top panel No application launched All extentions disabled ABRT report : https://retrace.fedoraproject.org/faf/reports/800969/ F39 is also affected. Happened when I selected bluetooth headphones as sound output from the quick settings https://retrace.fedoraproject.org/faf/reports/882910/ Also seeing this on F39: --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#712612' was found Searching for updates No updates for this package found @otaylor: Please reopen this ticket or find a way for abrt to create new tickets and not keep finding this one. /var/log/messages: Jan 17 18:41:00 pc.interlinx.bc.ca gnome-shell[5567]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x260100f Jan 17 18:41:11 pc.interlinx.bc.ca gnome-shell[5567]: Window manager warning: WM_TRANSIENT_FOR window 0x7000161 for 0x70001b4 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x7000006. Jan 17 18:41:13 pc.interlinx.bc.ca gnome-shell[5567]: Window manager warning: WM_TRANSIENT_FOR window 0x7000161 for 0x70001ba window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x7000006. Jan 17 18:41:15 pc.interlinx.bc.ca gnome-shell[5567]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x7201310 Jan 17 18:41:20 pc.interlinx.bc.ca gnome-shell[5567]: ** Jan 17 18:41:20 pc.interlinx.bc.ca gnome-shell[5567]: libmutter:ERROR:../src/core/window.c:1524:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Jan 17 18:41:20 pc.interlinx.bc.ca gnome-shell[5567]: Bail out! libmutter:ERROR:../src/core/window.c:1524:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Jan 17 18:41:20 pc.interlinx.bc.ca gnome-shell[5567]: == Stack trace for context 0x55e033eac190 == Jan 17 18:41:20 pc.interlinx.bc.ca gnome-shell[5567]: #0 55e033f75ac8 i resource:///org/gnome/shell/ui/init.js:21 (2dc346770ba0 @ 48) Jan 17 18:41:44 pc.interlinx.bc.ca gnome-shell[3250247]: Running GNOME Shell (using mutter 45.3) as a X11 window and compositing manager Jan 17 18:41:47 pc.interlinx.bc.ca gnome-shell[3250247]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7000006 specified for 0x7000211. Jan 17 18:41:50 pc.interlinx.bc.ca gnome-shell[3250247]: Window manager warning: last_user_time (61631178) is greater than comparison timestamp (3011717888). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 17 18:41:50 pc.interlinx.bc.ca gnome-shell[3250247]: Window manager warning: 0x2c006b2 appears to be one of the offending windows with a timestamp of 1151523. Working around... Jan 17 18:41:50 pc.interlinx.bc.ca gnome-shell[3250247]: Window manager warning: 0x3200059 appears to be one of the offending windows with a timestamp of 61631178. Working around... Created attachment 2009634 [details] Backtrace for report in comment 30 This is the backtrace for the report in the previous comment. Yes, I am also seeing this bug on Fedora 39. Also got this bug from the "Problem Reporting" application. Is there a link to a Fedora 39 bug for it? I don't have consistent ways to reproduce this bug, but GNOME shell crashes seem catastrophic since you get instantly logged out and no software prompts you to save your progress. What I have found, though, is that this crash occurs whenever I am using the touchpad gestures to switch between workspaces while having Electron apps open. We now have a second report of this on F39. Could somebody who has permission please reopen this issue and set the Version: to 39? (In reply to Brian J. Murrell from comment #33) > We now have a second report of this on F39. Could somebody who has > permission please reopen this issue and set the Version: to 39? I don't think this is useful as the original report is almost 13 years old and code has changed a lot. The description to reproduce the bug in comment #4 does not apply any more, as the overview sidebar does not exist any more. The other comments have very different steps to reproduce. I recommend to create a new bug report for F39 instead and provide some more detailed steps to reproduce. > I recommend to create a new bug report for F39 instead and provide some more detailed steps to reproduce.
I don't disagree. The problem is though that this is a bug that ABRT it trapping and reporting. It is ABRT that is adding reports to this ticket. As users we have no way to influence that and request a new ticket to be filed instead.
Additionally, it is not practical to manually gather up all of the collateral that ABRT does and create a new ticket for it. And even if somebody does do that, future instances of this bug trapped by ABRT on everyone else's systems are going to continue to be logged to this ticket.
I would suggest that this bugzilla needs to be able to tell ABRT that this ticket is no longer valid and that it should disregard it when looking for existing tickets.
Okay, for the sake of filing a new bug I have done so: https://bugzilla.redhat.com/show_bug.cgi?id=712612 What kind of stack trace should I upload? |