Bug 598770 - [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)
Summary: [abrt] crash in Thunar-1.0.1-7.fc13: exo_icon_view_item_hit_test: Process /us...
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Thunar   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1613aac95a4d7a0af3502fd6e05...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 02:06 UTC by Konstantin Svist
Modified: 2010-06-27 00:48 UTC (History)
3 users (show)

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: ---


Attachments (Terms of Use)
File: backtrace (35.23 KB, text/plain)
2010-06-02 02:06 UTC, Konstantin Svist
no flags Details

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?


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