Bug 573760 - [abrt] crash in Thunar-1.0.1-3.fc12: Process /usr/bin/Thunar was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in Thunar-1.0.1-3.fc12: Process /usr/bin/Thunar was killed by si...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Thunar
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:08fcad480240c4a4fc330e42138...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-15 17:57 UTC by Santiago Lunar
Modified: 2010-07-04 19:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-04 19:24:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (32.62 KB, text/plain)
2010-03-15 17:57 UTC, Santiago Lunar 		no flags Details
View All

Description Santiago Lunar 2010-03-15 17:57:37 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/Thunar --daemon
component: Thunar
executable: /usr/bin/Thunar
kernel: 2.6.32.9-70.fc12.i686.PAE
package: Thunar-1.0.1-3.fc12
rating: 4
reason: Process /usr/bin/Thunar was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Open Thunar window
2. Open a second Thunar windows with Pen Drive on it
3. Transfer files from window 1 to Pen Drive window
Comment 1 Santiago Lunar 2010-03-15 17:57:40 UTC 
Created attachment 400278 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-03-21 03:27:10 UTC 
What were you doing when this happened?

Can you duplicate it?
Comment 3 Kevin Fenzi 2010-07-04 19:24:45 UTC 
Greetings.

This bug has been waiting for info for several months.
I am going to go ahead and close it now.

If you are able to provide information that will help me
track this issue down, please feel free to open a new bug
or just re-open this one with the new information.

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