Version-Release number of selected component: gnome-shell-3.5.91-1.fc18 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _gdk_x11_display_error_event kernel: 3.6.0-0.rc4.git2.1.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #2 _gdk_x11_display_error_event at gdkdisplay-x11.c : #6 handle_error at xcb_io.c : #8 DRI2GetMSC at dri2.c : #9 dri2DrawableGetMSC at dri2_glx.c : #10 __glXGetVideoSyncSGI at glxcmds.c : #11 _cogl_winsys_wait_for_vblank at winsys/cogl-winsys-glx.c : #12 _cogl_winsys_onscreen_swap_region at winsys/cogl-winsys-glx.c : #13 cogl_onscreen_swap_region at ./cogl-onscreen.c : #14 clutter_stage_cogl_redraw at cogl/clutter-stage-cogl.c : #15 clutter_stage_do_redraw at ./clutter-stage.c
Created attachment 612601 [details] File: core_backtrace
Created attachment 612602 [details] File: environ
Created attachment 612603 [details] File: backtrace
Created attachment 612604 [details] File: limits
Created attachment 612605 [details] File: cgroup
Created attachment 612606 [details] File: maps
Created attachment 612607 [details] File: dso_list
Created attachment 612608 [details] File: var_log_messages
Created attachment 612609 [details] File: open_fds
unlocked screen backtrace_rating: 4 Package: gnome-shell-3.5.92-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
closed and opened lid backtrace_rating: 4 Package: gnome-shell-3.5.92-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
closed and opened lid backtrace_rating: 4 Package: gnome-shell-3.6.0-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
I tried to create a Virtual Machine using Boxes and the computer start a unistable behavior and folling down. I tried 2 times have the same result. backtrace_rating: 4 Package: gnome-shell-3.6.2-6.fc18 Architecture: i686 OS Release: Fedora release 18 (Spherical Cow)
Suspend on lid close of the notebook. gnome-shell-3.6.2-6.fc18.x86_64
The way I can repeat this in F18 is while both screens are blank & locked I remove the HDMI cable to my laptop's external monitor (which shows asleep). It doesn't seem to occur if I log in, then remove the HDMI cable. This exception just occurred again and I have seen it ~7 times since upgrading to F18. Currently all packages are up to date (yum update) and specifically gnome-shell-3.6.2-6.fc18.i686
Opening and closing lid of notebook triggers this bug for me as well. If stacktrace is required let me know and I'll upload it.
I'm seeing this if I disconnect VGA while the laptop is in suspend.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.