Bug 600734

Summary: [abrt] crash in xcdroast-1:0.98-0.3.alpha16.fc12: draw_scsi_scan_devs: Process /usr/bin/xcdroast was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: TL <bugzilla>
Component: xcdroastAssignee: Roman Rakus <rrakus>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: rrakus, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:a621fe0c63a7f2416b97342748fe6d003e0eb024
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:01: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 TL 2010-06-05 19:48:51 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: xcdroast
component: xcdroast
crash_function: draw_scsi_scan_devs
executable: /usr/bin/xcdroast
global_uuid: a621fe0c63a7f2416b97342748fe6d003e0eb024
kernel: 2.6.32.12-115.fc12.i686.PAE
package: xcdroast-1:0.98-0.3.alpha16.fc12
rating: 4
reason: Process /usr/bin/xcdroast was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Try to scan for cd/dvd drives anew
2.
3.

Comment 1 TL 2010-06-05 19:48:53 UTC
Created attachment 421485 [details]
File: backtrace

Comment 2 Roman Rakus 2010-06-07 07:35:49 UTC
Thanks for the report. Is it 100% reproducible? Can you please try the latest xcdroast from rawhide?

Comment 3 TL 2010-06-09 03:28:40 UTC
Hi,

Sorry that evening when I was getting the bug -- I decided to upgrade my whole system from Fedora 12 -> Fedora 13, so I wiped out everything and rebuilt the machine.

However, I do remember more precise details on the circumstances when it happens.

Apologies I don't have it installed again yet, and so don't have it front of me; so from memory it's something like this: It happens in the setup screen when one selects 'Rescan' for devices/drives.  Then, there is a pop-up window that says something informational, like 'this will erase your current settings, are you sure' or something. 

It is when one hits 'OK' from this informational screen -- that is the exact point when it core dumps/crashes.  It doesn't scan; just crashes.

Hope that helps.

Comment 4 Bug Zapper 2010-11-03 13:32:06 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 2010-12-03 14:01:27 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.