Bug 597559

Summary: [abrt] crash in gnome-commander-2:1.2.8.5-3.fc13: raise: Process /usr/libexec/gnome-commander/gnome-commander was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Alexander Osipenko <sipych>
Component: gnome-commanderAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: epiotr, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:10434d9f2bb94821c8819b8126f270ec0ea58b9a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 17:00:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description Alexander Osipenko 2010-05-29 15:06:55 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-commander
component: gnome-commander
crash_function: raise
executable: /usr/libexec/gnome-commander/gnome-commander
global_uuid: 10434d9f2bb94821c8819b8126f270ec0ea58b9a
kernel: 2.6.33.4-95.fc13.i686
package: gnome-commander-2:1.2.8.5-3.fc13
rating: 4
reason: Process /usr/libexec/gnome-commander/gnome-commander was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
Just the same crash when pressing "OK" after editing existing app entry.

Crash doesn't depends on the contents of the fav-apps configuration  file.

Crash also present uder Ubuntu-10.4 with the same gcmd release.

How to reproduce
-----
1. Open "Settings/Options" dialog
2. Select "Programs" tab
3. Press "Add" button near "Other favorilte apps" section
4. Fill "Label" field with any name
5. Press "OK" button

Comment 1 Alexander Osipenko 2010-05-29 15:06:58 UTC
Created attachment 417873 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-02 12:54:59 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 3 Bug Zapper 2011-06-27 17:00:37 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.