Red Hat Bugzilla – Bug 1000664
[abrt] gnome-shell-3.8.4-2.fc19: unpack_ARGB8888: Process /usr/bin/gnome-shell was killed by signal 7 (SIGBUS)
Last modified: 2015-02-17 11:54:00 EST
Description of problem:
System is booting but gnome-shell gdm fails to display and instead an error screen appears.
The crash seems to be related to a problem with the video driver. Here is the relevant lines from /var/log/messages:
Aug 23 22:15:21 host gnome-session: JS LOG: GNOME Shell started at Fri Aug 23 2013 22:15:21 GMT-0500 (CDT)
Aug 23 22:15:22 host gnome-session: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Aug 23 22:15:22 host gnome-session: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
Aug 23 22:15:22 host gnome-session: (gnome-shell:1295): Cogl-WARNING **: ./driver/gl/cogl-pipeline-opengl.c:872: GL error (1280): Invalid enumeration value
Aug 23 22:15:22 host kernel: [ 85.079962] nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 2 [gnome-shell] get 0xbeef0200 put 0x00a5ac04 state 0xc000418c (err: MEM_FAULT) push 0x00000000
Aug 23 22:15:22 host kernel: [ 85.080677] nouveau E[ PGRAPH][0000:01:00.0] ERROR nsource: PROTECTION_ERROR nstatus: INVALID_STATE PROTECTION_FAULT
Aug 23 22:15:22 host kernel: [ 85.080701] nouveau E[ PGRAPH][0000:01:00.0] ch 2 [gnome-shell] subc 2 class 0x0062 mthd 0x0184 data 0x00003b02
Version-Release number of selected component:
cmdline: gnome-shell --mode=gdm
runlevel: N 5
Thread no. 1 (10 frames)
#0 unpack_ARGB8888 at ../../../src/mesa/main/format_unpack.c:123
#1 _mesa_unpack_rgba_row at ../../../src/mesa/main/format_unpack.c:2504
#2 slow_read_rgba_pixels at ../../../src/mesa/main/readpix.c:531
#3 read_rgba_pixels at ../../../src/mesa/main/readpix.c:574
#4 _mesa_readpixels at ../../../src/mesa/main/readpix.c:848
#5 _mesa_ReadnPixelsARB at ../../../src/mesa/main/readpix.c:1042
#6 _mesa_ReadPixels at ../../../src/mesa/main/readpix.c:1050
#7 shared_dispatch_stub_256 at ../../../src/mapi/shared-glapi/glapi_mapi_tmp.h:14683
#8 _cogl_framebuffer_gl_read_pixels_into_bitmap at driver/gl/cogl-framebuffer-gl.c:1440
#9 _cogl_framebuffer_read_pixels_into_bitmap at ./cogl-framebuffer.c:1482
Potential duplicate: bug 754765
Created attachment 789772 [details]
Created attachment 789773 [details]
Created attachment 789774 [details]
Created attachment 789775 [details]
Created attachment 789776 [details]
Created attachment 789777 [details]
Created attachment 789778 [details]
Created attachment 789779 [details]
Created attachment 789780 [details]
Created attachment 789781 [details]
Created attachment 789782 [details]
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.