Bug 614311

Summary: [abrt] crash in qtoctave-0.9.1-2.fc13: QIODevice::isOpen: Process /usr/bin/qtoctave_pkg was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Durai <b.durai>
Component: qtoctaveAssignee: nucleo <alekcejk>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: alekcejk, chitlesh, gbrault, kevin, msdeleonpeque
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:5da40d9299c590d1a01b039e392a29eda8ae2bee
Fixed In Version: 0.10.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-29 13:33:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description Durai 2010-07-14 06:09:17 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/qtoctave_pkg
comment: select the "Install Octave Packages" option in "config" menu
component: qtoctave
crash_function: QIODevice::isOpen
executable: /usr/bin/qtoctave_pkg
global_uuid: 5da40d9299c590d1a01b039e392a29eda8ae2bee
package: qtoctave-0.9.1-2.fc13
rating: 4
reason: Process /usr/bin/qtoctave_pkg was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Durai 2010-07-14 06:09:21 UTC
Created attachment 431672 [details]
File: backtrace

Comment 2 nucleo 2010-10-24 09:09:35 UTC
*** Bug 623558 has been marked as a duplicate of this bug. ***

Comment 3 nucleo 2010-10-24 09:09:48 UTC
*** Bug 623557 has been marked as a duplicate of this bug. ***

Comment 4 nucleo 2010-10-24 09:13:36 UTC
*** Bug 646004 has been marked as a duplicate of this bug. ***

Comment 5 nucleo 2011-03-10 00:05:50 UTC
Please test qtoctave-0.10.1 from updates-testing is it fixes problem?

Comment 6 Bug Zapper 2011-06-01 13:58:05 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: 

Comment 7 Bug Zapper 2011-06-29 13:33:57 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.

Comment 8 Kevin Kofler 2011-10-06 17:02:37 UTC
AFAICT, this is indeed fixed in 0.10.1 (see also comment #5), which was also pushed to F13 before it went EOL.