Bug 541775 - [abrt] crash detected in Thunar-1.0.1-3.fc12
Summary: [abrt] crash detected in Thunar-1.0.1-3.fc12
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:2028f458ab2d6c8bff901692f2a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-27 02:27 UTC by Ataliba Teixeira
Modified: 2010-02-03 21:24 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-03 21:24:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (10.58 KB, text/plain)
2009-11-27 02:27 UTC, Ataliba Teixeira
no flags Details

Description Ataliba Teixeira 2009-11-27 02:27:42 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. I put my pendrive on my notebook
2.
3.

Comment: I put my pendrive on my notebook . When Thunar is going to show my files ... a crash is showed to me. 
Attached file: backtrace
cmdline: /usr/bin/Thunar --daemon
component: Thunar
executable: /usr/bin/Thunar
kernel: 2.6.31.6-145.fc12.i686.PAE
package: Thunar-1.0.1-3.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Ataliba Teixeira 2009-11-27 02:27:45 UTC
Created attachment 374113 [details]
File: backtrace

Comment 2 Kevin Fenzi 2009-11-27 03:23:48 UTC
Sadly, there doesn't seem to be debuginfo to make this useful. ;( 

Can you do a 'debuginfo-install Thunar' and 'debuginfo-install exo' and then see if you can duplicate it again and get another backtace?

Comment 3 Kevin Fenzi 2009-12-04 21:30:10 UTC
Oops. Accidentally got this re-assigned. Assigning it back to Thunar.

Comment 4 Christoph Wickert 2010-02-03 21:24:48 UTC
No response from submitter for two months. Closing because there is nothing we can do without a proper backtace. Just file a new bug if Thunar crashes again. The bug reporting is much more reliable now, so this should be trivial.


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