Bug 626564

Summary:

[abrt] lxpanel-0.5.6-1.fc13: flash_window_timeout: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)

Product:

[Fedora] Fedora

Reporter:

muny <muny>

Component:

lxpanel

Assignee:

Christoph Wickert <christoph.wickert>

Status:

CLOSED DUPLICATE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

low

Version:

CC:

andreygeorge, christoph.wickert

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

abrt_hash:85cc59d09ad844d87ad198cfcf902b286878c8c1

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2010-08-27 21:57:25 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	Flags
File: backtrace	none

Description muny 2010-08-23 20:27:50 UTC

abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: lxpanel --profile LXDE
component: lxpanel
crash_function: flash_window_timeout
executable: /usr/bin/lxpanel
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: lxpanel-0.5.6-1.fc13
rating: 4
reason: Process /usr/bin/lxpanel was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282595065
uid: 500

How to reproduce
-----
1. close firefox on other desktop

Comment 1 muny 2010-08-23 20:27:53 UTC

Created an attachment (id=440476)
File: backtrace

Comment 2 Christoph Wickert 2010-08-27 21:57:25 UTC

This was supposed to be fixed in 0.5.6, but obviously it's not. See bug 587430 for more info.

The crash will be tracked in upstream's bugtracker at https://sourceforge.net/tracker/index.php?func=detail&aid=3030538&group_id=180858&atid=894869

Feel free to subscribe to that bug in order to get informed about the latest changes. I will notify you once it is closed in Fedora. Thanks for reporting this problem.

*** This bug has been marked as a duplicate of bug 587430 ***