Bug 598770

Summary: [abrt] crash in Thunar-1.0.1-7.fc13: exo_icon_view_item_hit_test: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Konstantin Svist <fry.kun>
Component: ThunarAssignee: Kevin Fenzi <kevin>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert, kevin, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:1613aac95a4d7a0af3502fd6e0589cbe4d393d52
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-27 00:48:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Konstantin Svist 2010-06-02 02:06:13 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: Thunar --daemon
comment: opened a directory from XFCE desktop
component: Thunar
crash_function: exo_icon_view_item_hit_test
executable: /usr/bin/Thunar
global_uuid: 1613aac95a4d7a0af3502fd6e0589cbe4d393d52
kernel: 2.6.33.5-112.fc13.i686
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 Konstantin Svist 2010-06-02 02:06:15 UTC 
Created attachment 418877 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-06-27 00:21:13 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 Konstantin Svist 2010-06-27 00:41:02 UTC 
haven't seen the crash since
running 1.0.2 already
Comment 4 Kevin Fenzi 2010-06-27 00:48:27 UTC 
ok, I will go ahead and close this. Please re-open or file a new one if it happens again?