Bug 91105 - Installer crashed - non-Linux partition
Summary: Installer crashed - non-Linux partition
Status: CLOSED DUPLICATE of bug 124843
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: parted   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
URL: none
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-18 15:31 UTC by Thomas E. Dickey
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:53:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
trace from failed install (90.78 KB, text/plain)
2003-05-26 14:29 UTC, Thomas E. Dickey
no flags Details

Description Thomas E. Dickey 2003-05-18 15:31:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.2.16 i686)

Description of problem:
After selecting "/" partition (/dev/hda14), the install script popped
up a window stating that it could not obtain characteristics for
/dev/hdb3 (which happens to be OpenBSD).  I clicked on "Ignore",
and got a subsequent popup offering the opportunity to "Debug", or
"Cancel" (citing an exception raised in a python script).
Cancelling of course aborts the install.

I tried this twice, don't have a spare machine to waste, so I
installed Slackware 9.0, which works nicely.  It would be nice
to review Redhat 9.0 (maybe).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. see above	

Actual Results:  install was aborted.

Expected Results:  unknown partition type should have been ignored, as

Additional info:

Comment 1 Jeremy Katz 2003-05-25 17:55:22 UTC
Can you provide the exception?

Comment 2 Thomas E. Dickey 2003-05-25 18:33:50 UTC
You're talking about the trace it offered to write to a floppy?No - Friday's are bad for installs, and I was looking for an early
finish.  I'm considering trying the install (on a different partition)
tomorrow morning.  Unless there's some interaction with the partition
numbers (both are on the first drive, while the problem was against
the second), I'd expect to see the same issue there.
Is there any information that I should record that would not be in
that trace?

Comment 3 Jeremy Katz 2003-05-25 19:07:36 UTC
The backtrace usually has everything needed.   Without it, it's hard to say what

Comment 4 Thomas E. Dickey 2003-05-26 14:29:09 UTC
Created attachment 91970 [details]
trace from failed install

I setup a test using the same configuration as before,
same result.  (Just to be different, I did try "Cancel"
on the first dialog rather than "Ignore", but it made
no difference).

Comment 5 Jeremy Katz 2004-06-25 19:18:51 UTC
Does this happen with newer Fedora releases?

Comment 6 Thomas E. Dickey 2004-06-25 19:51:14 UTC
I don't know (the hardware is no longer a test-machine).

Comment 7 Jeremy Katz 2004-06-25 19:58:45 UTC

*** This bug has been marked as a duplicate of 124843 ***

Comment 8 Red Hat Bugzilla 2006-02-21 18:53:08 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.