Bug 617852 - [abrt] crash in pcmanfm-0.9.7-1.fc13: raise: Process /usr/bin/pcmanfm was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in pcmanfm-0.9.7-1.fc13: raise: Process /usr/bin/pcmanfm was kil...
Status: CLOSED DUPLICATE of bug 640969
Alias: None
Product: Fedora
Classification: Fedora
Component: pcmanfm (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d237ee6b5d44ae3b736a090bd6b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-24 12:57 UTC by Terry Wallwork
Modified: 2010-11-08 18:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-08 18:30:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (9.92 KB, text/plain)
2010-07-24 12:58 UTC, Terry Wallwork
no flags Details

Description Terry Wallwork 2010-07-24 12:57:02 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pcmanfm --desktop --profile lxde
component: pcmanfm
crash_function: raise
executable: /usr/bin/pcmanfm
global_uuid: d237ee6b5d44ae3b736a090bd6b505fafdbceb54
kernel: 2.6.33.6-147.fc13.i686
package: pcmanfm-0.9.7-1.fc13
rating: 4
reason: Process /usr/bin/pcmanfm was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Middle clicked on a file
2.
3.

Comment 1 Terry Wallwork 2010-07-24 12:58:39 UTC
Created attachment 434137 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:30:28 UTC

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

Comment 3 Karel Klíč 2010-11-08 18:30:28 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #640969.

Sorry for the inconvenience.


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