Bug 128199 - Installer hangs on disk druid
Summary: Installer hangs on disk druid
Keywords:
Status: CLOSED DUPLICATE of bug 100747
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-19 23:12 UTC by Pedro Fernandes Macedo
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:04:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pedro Fernandes Macedo 2004-07-19 23:12:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Gecko/20040113

Description of problem:
On FC3T1 , doing a network install, clicking on the graphic
representation of the disks in disk druid makes anaconda stop
responding. On the other vt , top shows 99% cpu usage by anaconda.

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


How reproducible:
Always

Steps to Reproduce:
1. Click (or double-click) on the graphic representation of any partition
 

Actual Results:  Anaconda stops responding

Expected Results:  The partition should be selected. If it was a
double-click , the edit window should open.

Additional info:

Comment 1 Jeremy Katz 2004-07-27 03:27:36 UTC
Does just running parted on your disk hang?

Comment 2 Pedro Fernandes Macedo 2004-07-27 03:45:49 UTC
No, it works perfectly without hanging. Using parted-1.6.11-2.
It only complains about the geometry of /dev/hdb and /dev/hdc , but no
complaints about /dev/hda (where fc3t1 is installed).

Comment 3 David Balažic 2004-07-28 12:26:52 UTC
duplicate of bug 100747 ?

Comment 4 Jeremy Katz 2004-09-22 19:52:24 UTC

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

Comment 5 Red Hat Bugzilla 2006-02-21 19:04:30 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.