Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: fetch_texel_2d_f_rgb888 executable: /usr/bin/gnome-shell kernel: 3.2.0-0.rc1.git0.2.fc17.i686.PAE pid: 2040 pwd: /home/jreiser reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) time: Wed 09 Nov 2011 01:26:21 PM PST uid: 1000 username: jreiser backtrace: Text file, 55139 bytes build_ids: Text file, 7011 bytes dso_list: Text file, 20419 bytes maps: Text file, 50471 bytes var_log_messages: Text file, 14192 bytes environ: :XDG_VTNR=2 :XDG_SESSION_ID=5 :HOSTNAME=f17r32.local :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :XDG_SESSION_COOKIE=0072d17adf14ac579c6416b900000014-1320873543.828306-925747208 :GNOME_KEYRING_CONTROL=/tmp/keyring-ho3xbH :IMSETTINGS_MODULE=none :USER=jreiser :USERNAME=jreiser :MAIL=/var/spool/mail/jreiser :PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/jreiser/.local/bin:/home/jreiser/bin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/jreiser :XMODIFIERS=@im=none :GNOME_KEYRING_PID=1851 :LANG=en_US.UTF-8 :GDMSESSION=gnome :HISTCONTROL=ignoredups :HOME=/home/jreiser :XDG_SEAT=seat0 :SHLVL=1 :LOGNAME=jreiser :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-cFzAVOB49c,guid=c636abfe7edf30e7d5eda35700000de5 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=2 :XDG_RUNTIME_DIR=/run/user/jreiser :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-jreiser-AgP667/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1855,unix/unix:/tmp/.ICE-unix/1855 :SSH_AUTH_SOCK=/tmp/keyring-ho3xbH/ssh :GPG_AGENT_INFO=/tmp/keyring-ho3xbH/gpg:0:1 :DESKTOP_AUTOSTART_ID=106fcce88f1a608170132087354787737200000018550000
Created attachment 532857 [details] File: dso_list
Created attachment 532858 [details] File: build_ids
Created attachment 532859 [details] File: maps
Created attachment 532860 [details] File: var_log_messages
Created attachment 532861 [details] File: backtrace
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.