Bug 701158

Summary: [abrt] gnome-disk-utility-2.30.1-1.fc13: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joe Robinson <joe_underscore>
Component: gnome-disk-utilityAssignee: David Zeuthen <davidz>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: davidz, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d254418af1ffe49dc327785c53e993ef71b19e49
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 11:46:28 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 Joe Robinson 2011-05-01 17:32:43 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: palimpsest
component: gnome-disk-utility
crash_function: gdu_device_get_device_file_presentation
executable: /usr/bin/palimpsest
kernel: 2.6.34.8-68.fc13.i686.PAE
package: gnome-disk-utility-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/palimpsest was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1304269774
uid: 500

comment
-----
I'll try going back to command-line and ...

mdadm --create /dev/md1 --level=1 --metadata=0.90 --raid-devices=3 /dev/sd[abc]2

How to reproduce
-----
1. I was in the disk-utility gui, deleting components of an unsuccessfully-assembled software RAID array
2. this was a three-partition RAID1 (/dev/sda2, /dev/sdb2, /dev/sdc2) intended as swap
3. it was created by:
[root@fireball whacker]# mdadm --create /dev/md1 --level=1 --raid-devices=3 /dev/sd[abc]2
mdadm: Note: this array has metadata at the start and
    may not be suitable as a boot device.  If you plan to
    store '/boot' on this device please ensure that
    your boot-loader understands md/v1.x metadata, or use
    --metadata=0.90
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
====================================
--- formatted as swap space, under GUI, showing as metadata version 1.2 
-- other two arrays md0 for /boot and md2 for / show metadata version 0.90.0
-- system would not pick md1 as swap, (I think calling it /dev/md127)
-- had deleted (under gui) two components, but could go no further with third "because it was in use"
-- clicked on "stop RAID array", and CRASH!

Comment 1 Joe Robinson 2011-05-01 17:32:46 UTC
Created attachment 496084 [details]
File: backtrace

Comment 2 Bug Zapper 2011-05-30 10:36:44 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 11:46:28 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.