Bug 643388
| Summary: | [abrt] lxpanel-0.5.6-1.fc14: IA__gtk_widget_show: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Masami Ichikawa <masami256> | ||||
| Component: | lxpanel | Assignee: | Christoph Wickert <christoph.wickert> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | christoph.wickert, dagmowi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| URL: | https://sourceforge.net/tracker/?func=detail&aid=3088793&group_id=180858&atid=894869 | ||||||
| Whiteboard: | abrt_hash:3b6ecd4a4eeaa9fe49ee0f00cc595f8817f6aa45 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-10-16 18:12:57 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Masami Ichikawa
2010-10-15 13:31:14 UTC
Created attachment 453729 [details]
File: backtrace
I used F14 TC1.1 LXDE LiveCD and I was doing these tests. https://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_TC1_Desktop Does this happen every time? oops, sorry. I should have written it. After the crash, I tried to reproduce it more than 10 times, but I haven't reproduced it yet. I did login/logout about 20 times, and I saw a crash just one time which is I reported. Thanks for your feedback. I have forwarded this bug report to the LXDE bugtracker at https://sourceforge.net/tracker/?func=detail&aid=3088793&group_id=180858&atid=894869 From now on, further investigation of this crash should take place upstream. I will get back to you if I need more info and inform you once this bug is resolved in Fedora. *** Bug 693128 has been marked as a duplicate of this bug. *** |