Bug 663516 - [abrt] xfwm4-4.6.2-2.fc14.1: handleSignal: Process /usr/bin/xfwm4 was killed by signal 6 (SIGABRT)
Summary: [abrt] xfwm4-4.6.2-2.fc14.1: handleSignal: Process /usr/bin/xfwm4 was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xfwm4
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a3bd3af95b6db280b3efdf49877...
: 711220 747454 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-16 02:10 UTC by Porter Smith
Modified: 2012-08-16 22:18 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 22:03:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (13.69 KB, text/plain)
2010-12-16 02:10 UTC, Porter Smith
no flags Details

Description Porter Smith 2010-12-16 02:10:56 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: xfwm4 --display :0.0 --sm-client-id 23885ccbb-1e6b-4dac-aace-83ed647273d7
component: xfwm4
crash_function: handleSignal
executable: /usr/bin/xfwm4
kernel: 2.6.35.9-64.fc14.i686
package: xfwm4-4.6.2-2.fc14.1
rating: 4
reason: Process /usr/bin/xfwm4 was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1292464339
uid: 500

How to reproduce
-----
1.
2.n/a

3.

Comment 1 Porter Smith 2010-12-16 02:10:59 UTC
Created attachment 469014 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-12-16 04:29:23 UTC
What were you doing when this happened? Can you duplicate it? 

Can you attach your ~/.xsession-errors file ?

Comment 3 Konstantin Svist 2011-03-11 22:02:54 UTC
Package: xfwm4-4.6.2-2.fc14.1
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Crash happened when I pressed alt+space to pop up window menu, possibly followed by 'C' to close the window.
Definitely doesn't happen every time but happened twice in the last two days

Comment 4 Kevin Fenzi 2011-03-12 19:58:58 UTC
Can you capture/attach ~/.xsession-errors from after a crash like this? 

It's segfaulting in something, but I can't see what...

Comment 5 Konstantin Svist 2011-03-12 21:43:36 UTC
will try to capture it. Any extra debug modes I should enable meanwhile?

Comment 6 Kevin Fenzi 2011-03-12 23:22:21 UTC
Not that I can think of, no.

Comment 7 Christoph Wickert 2011-11-19 09:02:55 UTC
*** Bug 711220 has been marked as a duplicate of this bug. ***

Comment 8 abrt-bot 2012-03-20 16:45:22 UTC
*** Bug 747454 has been marked as a duplicate of this bug. ***

Comment 9 Fedora End Of Life 2012-08-16 22:03:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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

Comment 10 Konstantin Svist 2012-08-16 22:18:10 UTC
Still happens from time to time


Note You need to log in before you can comment on or make changes to this bug.