Version-Release number of selected component: gnome-shell-3.10.4-8.fc20 Additional info: reporter: libreport-2.2.3 cmdline: /usr/bin/gnome-shell executable: /usr/bin/gnome-shell kernel: 3.15.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? at /lib64/libGL.so.1 #1 ?? at /lib64/libGL.so.1 #2 ?? at /lib64/libnvidia-glcore.so.343.13 #3 ?? at /lib64/libnvidia-glcore.so.343.13 #4 ?? at /lib64/libnvidia-glcore.so.343.13 #5 _cogl_framebuffer_gl_flush_state at driver/gl/cogl-framebuffer-gl.c:324 #6 _cogl_journal_flush at ./cogl-journal.c:1330 #7 _cogl_framebuffer_flush_journal at ./cogl-framebuffer.c:597 #8 _cogl_framebuffer_flush_dependency_journals at ./cogl-framebuffer.c:605 #9 _cogl_journal_flush at ./cogl-journal.c:1319 Potential duplicate: bug 730432
Created attachment 929811 [details] File: backtrace
Created attachment 929812 [details] File: cgroup
Created attachment 929813 [details] File: core_backtrace
Created attachment 929814 [details] File: dso_list
Created attachment 929815 [details] File: environ
Created attachment 929816 [details] File: exploitable
Created attachment 929817 [details] File: limits
Created attachment 929818 [details] File: maps
Created attachment 929819 [details] File: open_fds
Created attachment 929820 [details] File: proc_pid_status
Created attachment 929821 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
This bug needs updated to f24, but I don't have reporter privileges. Please would the reporter update to f24. This seems connected to gnome-shell crashing a lot for a while, see here Bug 1349363 This is the abrt server report: https://retrace.fedoraproject.org/faf/reports/1204117/ abrt reports 'Reporting disabled because the backtrace is unusable', so I'm entering this manually: --- 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 Preparing an archive to upload You are going to upload 10.7 MiB. Continue? 'YES' Uploading 10.7 MiB Uploading 60% Upload successful Retrace job started Preparing environment for backtrace generation ..... Generating backtrace Cleaning environment after backtrace generation Retrace job finished successfully Looking for similar problems in bugzilla Duplicate bugzilla bug '#1133131' was found Searching for updates No updates for this package found
Created attachment 1177042 [details] abrt directory contents
Again, bug report failed: 'Reporting disabled because the backtrace is unusable' So uploading directory here. ABRT Server address: https://retrace.fedoraproject.org/faf/reports/bthash/f9a01891cc21ee4373ba839cd75f10a3e8a2896e --- 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 Preparing an archive to upload You are going to upload 10.7 MiB. Continue? 'YES' Uploading 10.7 MiB Uploading 62% Upload successful Retrace job started Analyzing crash data Preparing environment for backtrace generation ..... Generating backtrace Cleaning environment after backtrace generation Retrace job finished successfully Looking for similar problems in bugzilla Duplicate bugzilla bug '#1133131' was found Searching for updates No updates for this package found
Created attachment 1177359 [details] abrt directory contents for Comment 16
It seems odd that a 2014 f20 bug, closed 2015 and reopened two months ago for no apparent reason is related to Bug 1349363 which only became apparent in f22 a few days before the release of f24 - and continues to be apparent in f24
For completeness, related bugs: Bug 1339328 Bug 1320307 Bug 1326492 Bug 1133131 Bug 1349363
Related bug: Bug 1326494
Bug 1354084
I just had this crash happen in Fedora 25 under Gnome 3.22 I went to add a world clock through the calendar in the top bar, everything crashed and I was back at a login screen. Note: gnome-calendar, gnome-clocks, and Evolution Alarm Notify all show up constantly in ABRT with "unable to report" status. Which will be hiding a lot of these crashes.
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.
Issue got reported by abrt for current Fedora 26 including package gnome-shell-3.24.2-1.fc26, unfortunately with unusable backtrace, but this bug was returned as a duplicate.
Please check your backtrace and see if it's anything like the backtrace on this bug at all; I suspect it isn't. abrt just told me an occurrence of https://bugzilla.redhat.com/show_bug.cgi?id=1446879 was a dupe of this. Given that you're on that bug too, I suspect you had the same thing. If so, let's just close this and follow up there.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
Just happened on Fedora 29
Just happened on Fedora 29. Interestingly enough ABRT did point to this bug, but did not add me to the cc: list.
Just happened to me (Fedora 29 as well) Closed laptop lid Opened laptop lid Plugged in external hdmi monitor and got login screen.
Jun 28 09:12:37 SYSTEM firefox-wayland.desktop[1758]: IPDL protocol Error: Received an invalid file descriptor Jun 28 09:14:54 SYSTEM org.gnome.Shell.desktop[1758]: libinput error: client bug: timer event4 middlebutton: offset negative (-1528ms) Jun 28 09:14:59 SYSTEM torbrowser.desktop[1758]: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Jun 28 09:15:02 SYSTEM torbrowser.desktop[1758]: Launching './Browser/start-tor-browser --detach'... Jun 28 09:15:03 SYSTEM torbrowser.desktop[1758]: Tor Browser Launcher Jun 28 09:15:03 SYSTEM torbrowser.desktop[1758]: By Micah Lee, licensed under MIT Jun 28 09:15:03 SYSTEM torbrowser.desktop[1758]: version 0.3.1 Jun 28 09:15:03 SYSTEM torbrowser.desktop[1758]: https://github.com/micahflee/torbrowser-launcher Jun 28 09:15:03 SYSTEM torbrowser.desktop[1758]: Launching Tor Browser. Jun 28 09:15:03 SYSTEM torbrowser.desktop[1758]: Running /home/trever/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop Jun 28 09:15:13 SYSTEM org.gnome.Shell.desktop[1758]: libinput error: client bug: timer event4 middlebutton: offset negative (-181ms) Jun 28 09:15:13 SYSTEM org.gnome.Shell.desktop[1758]: ** Jun 28 09:15:13 SYSTEM org.gnome.Shell.desktop[1758]: mutter:ERROR:../src/ui/frames.c:1104:meta_frame_left_click_event: code should not be reached Jun 28 09:15:13 SYSTEM org.gnome.Shell.desktop[1758]: == Stack trace for context 0x55dc25f282c0 == Jun 28 09:15:19 SYSTEM org.gnome.Shell.desktop[1758]: (EE) failed to read Wayland events: Connection reset by peer Jun 28 09:15:44 SYSTEM gnome-shell[4616]: g_dir_open_with_errno: assertion 'path != NULL' failed Jun 28 09:15:44 SYSTEM gnome-shell[4616]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed Jun 28 09:15:44 SYSTEM gnome-shell[4616]: g_dir_open_with_errno: assertion 'path != NULL' failed Jun 28 09:15:44 SYSTEM gnome-shell[4616]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed Jun 28 09:15:44 SYSTEM org.gnome.Shell.desktop[4616]: glamor: No eglstream capable devices found Jun 28 09:15:44 SYSTEM org.gnome.Shell.desktop[4616]: The XKEYBOARD keymap compiler (xkbcomp) reports: Jun 28 09:15:44 SYSTEM org.gnome.Shell.desktop[4616]: > Internal error: Could not resolve keysym XF86MonBrightnessCycle Jun 28 09:15:44 SYSTEM org.gnome.Shell.desktop[4616]: > Internal error: Could not resolve keysym XF86RotationLockToggle Jun 28 09:15:44 SYSTEM org.gnome.Shell.desktop[4616]: Errors from xkbcomp are not fatal to the X server Jun 28 09:15:48 SYSTEM org.gnome.Shell.desktop[4616]: The XKEYBOARD keymap compiler (xkbcomp) reports: Jun 28 09:15:48 SYSTEM org.gnome.Shell.desktop[4616]: > Warning: Unsupported maximum keycode 569, clipping. Jun 28 09:15:48 SYSTEM org.gnome.Shell.desktop[4616]: > X11 cannot support keycodes above 255. Jun 28 09:15:48 SYSTEM org.gnome.Shell.desktop[4616]: > Internal error: Could not resolve keysym XF86MonBrightnessCycle Jun 28 09:15:48 SYSTEM org.gnome.Shell.desktop[4616]: > Internal error: Could not resolve keysym XF86RotationLockToggle Jun 28 09:15:48 SYSTEM org.gnome.Shell.desktop[4616]: Errors from xkbcomp are not fatal to the X server Jun 28 09:15:50 SYSTEM gnome-shell[4616]: GNOME Shell started at Fri Jun 28 2019 09:15:44 GMT-0600 (MDT) Jun 28 09:15:50 SYSTEM gnome-shell[4616]: STACK_OP_ADD: window 0x1600001 already in stack Jun 28 09:15:50 SYSTEM gnome-shell[4616]: STACK_OP_ADD: window 0x1600001 already in stack
The above was from Fedora 30, current as of the date/time shown.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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.
This needs to be closed and stay closed. The initial crash was something in the NVIDIA driver in Fedora 20 (the backtrace runs through libnvidia-glcore.so.343.13 into libGL.so.1). None of the crashes posted since then have anything to do with the original. If ABRT tells you your bug is a dupe of this, it is lying: please ignore it (or maybe file a bug against ABRT) and file a new bug for your crash.