Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: lxpanel --profile LXDE comment: When laptop resume from suspend, abrt shows this error. crash_function: strcasecmp_l executable: /usr/bin/lxpanel kernel: 3.1.4-1.fc16.x86_64 pid: 1410 pwd: /home/masami reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV) time: Sun 04 Dec 2011 10:38:56 PM JST uid: 1000 username: masami backtrace: Text file, 94527 bytes build_ids: Text file, 2952 bytes dso_list: Text file, 7122 bytes maps: Text file, 32565 bytes smolt_data: Text file, 2739 bytes environ: :XDG_VTNR=1 :XDG_SESSION_ID=1 :SSH_AGENT_PID=1399 :SAL_USE_VCLPLUGIN=gtk :HOSTNAME=rune :IMSETTINGS_INTEGRATE_DESKTOP=yes :XDG_MENU_PREFIX=lxde- :TERM=dumb :SHELL=/bin/zsh :HISTSIZE=1000 :XDG_SESSION_COOKIE=66d14eb7fd2a237abe07b48700000017-1322997214.363883-74335027 :SYSFONT=latarcyrheb-sun16 :GNOME_KEYRING_CONTROL=/tmp/keyring-TDonTo :IMSETTINGS_MODULE=IBus :USER=masami :SSH_AUTH_SOCK=/tmp/ssh-NhxKfSSN1299/agent.1299 :MAIL=/var/spool/mail/masami :PATH=/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/masami/bin :DESKTOP_SESSION=LXDE :QT_IM_MODULE=xim :PWD=/home/masami :XMODIFIERS=@im=ibus :LANG=en_US.UTF-8 :GNOME_KEYRING_PID=1231 :SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass :HISTCONTROL=ignoredups :KEYTABLE=us :SHLVL=0 :HOME=/home/masami :XDG_SEAT=seat0 :XDG_CONFIG_HOME=/home/masami/.config :BOOT_IMAGE=/vmlinuz-3.1.4-1.fc16.x86_64 :LOGNAME=masami :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-TvtM0GaorA,guid=083a00a2eb326b664dbf78c900000012 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :PREFERRED=/usr/bin/startlxde :DISPLAY=:0 :XDG_RUNTIME_DIR=/run/user/masami :GTK_IM_MODULE=ibus :XAUTHORITY=/home/masami/.Xauthority :_LXSESSION_PID=1299 :XDG_CURRENT_DESKTOP=LXDE var_log_messages: :Dec 4 18:51:44 rune kernel: [23259.806545] lxpanel[1437]: segfault at 0 ip 0000003df732fb14 sp 00007fff08e9a6a8 error 4 in libc-2.14.90.so[3df7200000+1aa000] :Dec 4 18:51:44 rune abrt[9201]: Saved core dump of pid 1437 (/usr/bin/lxpanel) to /var/spool/abrt/ccpp-2011-12-04-18:51:44-1437 (37543936 bytes) :Dec 4 22:38:56 rune kernel: [ 8730.075362] lxpanel[1410]: segfault at 0 ip 00007f7f860b31e4 sp 00007fff6da2c6e8 error 4 in libc-2.14.90.so[7f7f85f83000+1ab000] :Dec 4 22:38:56 rune abrt[6116]: Saved core dump of pid 1410 (/usr/bin/lxpanel) to /var/spool/abrt/ccpp-2011-12-04-22:38:56-1410 (33546240 bytes)
Created attachment 540325 [details] File: dso_list
Created attachment 540326 [details] File: build_ids
Created attachment 540327 [details] File: smolt_data
Created attachment 540328 [details] File: maps
Created attachment 540329 [details] File: backtrace
Please try the update from https://admin.fedoraproject.org/updates/lxpanel-0.5.9-1.fc16
Hmm, sorry, I am using Fedora 17 so I couldn't test it. But I checked that lxpanel-0.5.10-1.fc17 didn't reproduce this bug.
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.