| Summary: | [abrt] xfce4-panel-4.8.6-3.fc16: launcher_plugin_item_load: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gajdos Tamás <gajdipajti> | ||||||
| Component: | xfce4-panel | Assignee: | Kevin Fenzi <kevin> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | cwickert, kevin, maxamillion | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:851a35ea1c71ceab6d6fd0b8221d50d6f7045953 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-02-13 15:51:21 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Gajdos Tamás
2011-12-11 13:47:02 UTC
Created attachment 545255 [details]
File: event_log
Created attachment 545256 [details]
File: dso_list
*** Bug 766293 has been marked as a duplicate of this bug. *** *** Bug 766298 has been marked as a duplicate of this bug. *** Thanks for submitting this crash report. What did you do when the panel crashed? Are you able to reproduce the crash reliably? If so, how? This is a testing host in our environment. It is a default fedora 16 setup, with a major difference. There is no local home folder, only a user based nis+nfs+autofs mount. (when someone logs in, the aufs mounts the accessed folder from the nfs server. I dont know how to reproduce, I think the problem came up when the machine went to standby. The other hosts are fedora 14, w/o the nfs+nis+aufs. So I dont know if this is a global problem, a local problem or just a single machine problem. If you need more info, or tests needed to be done, dint hesitate to ask. I will provide the required information when I will time. This also occured at the same time https://bugzilla.redhat.com/show_bug.cgi?id=766294 This error occures at boot. FYI, my xfce Desktop buggued on my current user, so I repaired it backtrace_rating: 4 Package: xfce4-panel-4.8.6-3.fc16 OS Release: Fedora release 16 (Verne) 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. |