abrt 1.0.2 detected a crash. How to reproduce ----- 1. Log in 2. Panel crashes Comment: Doesn't happen often, only rarely. Attached file: backtrace cmdline: lxpanel --profile LXDE component: lxpanel executable: /usr/bin/lxpanel kernel: 2.6.31.6-166.fc12.x86_64 package: lxpanel-0.5.4.1-1.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 381986 [details] File: backtrace
Forwarded upstream as https://sourceforge.net/tracker/?func=detail&aid=2973568&group_id=180858&atid=894869
lxpanel-0.5.5-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/lxpanel-0.5.5-3.fc13
lxpanel-0.5.5-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/lxpanel-0.5.5-3.fc12
lxpanel-0.5.5-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
lxpanel-0.5.5-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 652673 has been marked as a duplicate of this bug. ***
Looks like the bug is not yet fixed. Adjusting resolution from ERRATA to UPSTREAM as further investigation will take place in the LXDE bugtracker.
*** Bug 694966 has been marked as a duplicate of this bug. ***
*** Bug 708286 has been marked as a duplicate of this bug. ***
abrt tells that bug is closed in upstream, but i experience regularly. I have about 10 abrt detected crashes for about 12-13 days.
"Closed upstream" doesn't mean that is fixed but that it's "filed in the upstream bugs tracker or reported to the upstream mailing list." See https://bugzilla.redhat.com/page.cgi?id=fields.html#resolution I have reopened the upstream bug report at sourceforge as soon as I got the first reports that it is not fixed as upstream said. So far nothing has happened though because lxpanel is basically unmaintained after it's developer left LXDE.