Bug 601844 - [abrt] crash in Thunar-1.0.1-7.fc13: strcoll: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in Thunar-1.0.1-7.fc13: strcoll: Process /usr/bin/Thunar was kil...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: thunar-vcs-plugin
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d150720d87747854f9378fd627e...
: 601845 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-08 18:29 UTC by carlos.rca185
Modified: 2010-12-19 00:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-19 00:34:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (19.01 KB, text/plain)
2010-06-08 18:29 UTC, carlos.rca185
no flags Details

Description carlos.rca185 2010-06-08 18:29:26 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/Thunar --daemon
component: Thunar
crash_function: strcoll
executable: /usr/bin/Thunar
global_uuid: d150720d87747854f9378fd627e47a96e7d17627
kernel: 2.6.33.5-112.fc13.i686.PAE
package: Thunar-1.0.1-7.fc13
rating: 4
reason: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 carlos.rca185 2010-06-08 18:29:30 UTC
Created attachment 422310 [details]
File: backtrace

Comment 2 Kevin Fenzi 2010-06-27 00:21:00 UTC
Can you duplicate this? 

Please update to Thunar-1.0.2 thats available as an update now and see if that fixes it. If not, try removing thunar-vcs-plugin and see if that helps.

Comment 3 Christoph Wickert 2010-12-11 21:54:42 UTC
Reassigning to thunar-vcs-plugin.

Comment 4 Christoph Wickert 2010-12-19 00:30:01 UTC
*** Bug 601845 has been marked as a duplicate of this bug. ***

Comment 5 Christoph Wickert 2010-12-19 00:34:04 UTC
This is likely a backtrace of the other bugs you filed, but without feedback from you we cannot be 100% sure. In addition to that, the backtrace is corrupt. 

"Backtrace stopped: previous frame inner to this frame (corrupt stack?)"

Feel free to submit a new crash report if you are having problems again. but for now there is nothing we can do for you.


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