Bug 553100 - [abrt] crash in xfce4-appfinder-4.6.1-2.fc12
Summary: [abrt] crash in xfce4-appfinder-4.6.1-2.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-appfinder
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:be851aeb7a63d9e1184939df5a3...
: 585760 590314 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-07 04:15 UTC by mdmpsyd@gmail.com
Modified: 2010-12-04 00:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:45:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (5.70 KB, text/plain)
2010-01-07 04:15 UTC, mdmpsyd@gmail.com
no flags Details

Description mdmpsyd@gmail.com 2010-01-07 04:15:08 UTC
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: xfce4-appfinder
component: xfce4-appfinder
executable: /usr/bin/xfce4-appfinder
kernel: 2.6.31.9-174.fc12.i686.PAE
package: xfce4-appfinder-4.6.1-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 mdmpsyd@gmail.com 2010-01-07 04:15:10 UTC
Created attachment 382144 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-01-07 18:52:42 UTC
What were you doing when this crash happened? 
Can you duplicate it?

Comment 3 mdmpsyd@gmail.com 2010-01-07 20:13:39 UTC
1. What was I doing? I was searching for an application. Actually, the search was over and I had moved on to do other things when some time later I noticed the ABRT icon flashing (I hide the taskbar). So I do not know what was happening when the crash occurred.

2. Can I reproduce it? I don't know. Since I don't know what was going on when it happened, I doubt it.

Comment 4 Kevin Fenzi 2010-01-09 03:37:24 UTC
ok. Please do update this bug if you can determine a way to get it to crash again. 

I'll see what I can make of the backtrace. 

Thanks for the report.

Comment 5 Karel Klíč 2010-05-25 10:34:26 UTC
*** Bug 585760 has been marked as a duplicate of this bug. ***

Comment 6 Kevin Fenzi 2010-08-24 02:39:07 UTC
*** Bug 590314 has been marked as a duplicate of this bug. ***

Comment 7 Bug Zapper 2010-11-04 01:39:48 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 8 Bug Zapper 2010-12-04 00:45:51 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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