Bug 669905

Summary: [abrt] exo-0.3.107-2.fc13: exo_icon_view_get_cell_area: Process /usr/bin/exo-desktop-item-edit was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: zeljko <zeljko>
Component: exoAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d62b753b7d901caeceb1192e2ef8a31eed82f8b9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 12:33:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description zeljko 2011-01-15 17:56:59 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: exo-desktop-item-edit --display=:0.0 --create-new --type Application /home/linda/Desktop
component: exo
crash_function: exo_icon_view_get_cell_area
executable: /usr/bin/exo-desktop-item-edit
kernel: 2.6.34.7-66.fc13.i686.PAE
package: exo-0.3.107-2.fc13
rating: 4
reason: Process /usr/bin/exo-desktop-item-edit was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1295113938
uid: 500

How to reproduce
-----
1.Copied an icon into $HOME/.local/share/icons while launcher editor icon chooser was open
2.
3.

Comment 1 zeljko 2011-01-15 17:57:01 UTC
Created attachment 473656 [details]
File: backtrace

Comment 2 Kevin Fenzi 2011-01-16 01:28:37 UTC
Can you duplicate this every time? 

I'll look and see what I can make of the backtrace.

Comment 3 zeljko 2011-01-16 09:35:41 UTC
Haven't tried. Abrt daemon started that time and I've sent this to bugzilla.
Detailed info:
1.I've installed playonlinux for wine
2.Installed Starcraft II
3.Now I wanted to set icon on desktop launcher.
Icon wasn't visible since original icon had spaces in it's name (Starcraft II.png), so I've opened terminal and cd into .local/share/icons and there cp Starcraft\ II.png StarcraftII.png .
At that time launcher properties were open, and icon chooser.So generally, something should happen every time when something's changed in some directory and chooser for that dir is open.Don't know is it xfce or gtk2 bug ... no time to investigate ...

Comment 4 Bug Zapper 2011-05-30 11:53:10 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-27 12:33:02 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.