libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell comment: when i open my pc i con't find wlan crash_function: compute_image_info executable: /usr/bin/gnome-shell kernel: 3.1.2-1.fc16.x86_64 pid: 2535 pwd: /home/liang reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) time: 2011年11月26日 星期六 22时22分55秒 uid: 1000 username: liang backtrace: Text file, 94486 bytes dso_list: Text file, 21776 bytes event_log: Binary file, 1603 bytes maps: Text file, 82954 bytes smolt_data: Binary file, 3299 bytes var_log_messages: Text file, 14792 bytes environ: :XDG_VTNR=2 :XDG_SESSION_ID=4 :HOSTNAME=liang :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :XDG_SESSION_COOKIE=d86eecee508c22d589e8439a00000011-1322317352.735422-436655301 :GNOME_KEYRING_CONTROL=/tmp/keyring-eUjj6T :IMSETTINGS_MODULE=IBus :USER=liang :USERNAME=liang :MAIL=/var/spool/mail/liang :PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/liang/.local/bin:/home/liang/bin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/liang :XMODIFIERS=@im=ibus :GNOME_KEYRING_PID=2350 :LANG=zh_CN.utf8 :GDM_LANG=zh_CN.utf8 :GDMSESSION=gnome :HISTCONTROL=ignoredups :HOME=/home/liang :XDG_SEAT=seat0 :SHLVL=1 :LOGNAME=liang :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-YYq2mV9rnZ,guid=55881327290fa109f48bdbfe000000ca :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=2 :XDG_RUNTIME_DIR=/run/user/liang :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-liang-pyjmft/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2355,unix/unix:/tmp/.ICE-unix/2355 :GPG_AGENT_INFO=/tmp/keyring-eUjj6T/gpg:0:1 :SSH_AUTH_SOCK=/tmp/keyring-eUjj6T/ssh :DESKTOP_AUTOSTART_ID=10619541b48f637f89132231735334954900000023550000
Created attachment 536780 [details] File: dso_list
Created attachment 536781 [details] File: event_log
Created attachment 536782 [details] File: smolt_data
Created attachment 536783 [details] File: var_log_messages
Created attachment 536784 [details] File: maps
Created attachment 536785 [details] File: backtrace
How did it happen? I logged into the computer. How can it be reproduced? Since this is the first time I guess logging into the computer. rating: 4 Package: gnome-shell-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
*** Bug 757343 has been marked as a duplicate of this bug. ***
Was mousing over the volume, bluetooth and wireless indicators in the upper right "bar" backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 567107 [details] File: backtrace
Backtrace analysis of bugs across components suggests the actual bug is in component cairo or pixman instead of component gnome-shell, reassigning to cairo. Bug #728366 from component evince was found to be similar to this bug. This comment is automatically generated.
*** Bug 728366 has been marked as a duplicate of this bug. ***
Clicked on PDF link on page http://www.redhat.com/resourcelibrary/datasheets/red-hat-hybrid-iaas-solution-datasheet the link being http://www.redhat.com/rhecm/rest-rhecm/jcr/repository/collaboration/jcr:system/jcr:versionStorage/06596de10a0526011868c978f519a834/3/jcr:frozenNode/rh:resourceFile I may have already had another copy of that same PDF open, but I'm not sure. backtrace_rating: 4 Package: evince-3.4.0-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I was tring to uncompact a .rar file. backtrace_rating: 4 Package: gnome-shell-3.4.1-5.fc17 OS Release: Fedora release 17 (Beefy Miracle)
It appeared after first installation. Nothing had been loaded previously. Not dual boot backtrace_rating: 4 Package: gnome-shell-3.4.1-4.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I was looking for a program in the application search bar, then had a flicker, then this crash. backtrace_rating: 4 Package: gnome-shell-3.4.1-6.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to comment #18) > Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. > > Thank you for reporting this bug and we are sorry it could not be fixed. FYI - it looks like I am one of several folks who experienced this issue in Fedora 17 too... I would change the version from 16 to 17 except I don't have permission.