Red Hat Bugzilla – Bug 11250
Install crashes during disk druid given error
Last modified: 2008-05-01 11:37:55 EDT
Asked for 1.15 TB for var, couldn't find the disk space (expected), clicked
next anyway. Locked up.
Gtk-CRITICAL **: file gtkaccelgroup.c: line 188 (gtk_accel_group_attach):
assertion `g_slist_find (accel_group->attach_objects, object) ==NULL'
Need test lab to verify.
hmm ... trying to reproduce the problem, I am unable to hang the install when
adding a 1.4 Gb /var to an already full disk ... I get the customary error
dialog and can proceed from there ...
what hardware are you using ...? does this behave the same way in text mode
This test was done on a IBM NetFinity 5100 w/ ServeRAID card. Disk space was
probably upwards of 500GB online as a raid-5 array I can recreate it here with
a NetFinity 4500R running at 4GB mem, and 138856 MB on IBM ServeRAID (IPS raid
driver). I created the / and swap partitions at 1000MB and 100MB, and then put
1500000 for /var; The message DOES come up that it couldn't allocate that
space, and I clicked OK. The /var partition was red, but the >NEXT button was
NOT grey, and I pressed that and it died. In text mode, I was given a Nice
warning that some partitions were not allocated, When I hit OK, the install then
got a sig 11.
reassigning these to email@example.com for further review ...
I can successfully reproduce this here in the lab. The "Next" button is not
greyed out, so you may proceed without fixing the unallocatable /var partition.
You must already have a correctly allocated / and swap partition though, or the
button will be greyed out.
Note: effect verified on version 7.0
Think I have a fix for this in our internal tree - needs to be tested.
this issue is handled more gracefully, if not optimally, in the test tree
qa0116.3. Previously, an unallocated partition in ddruid would cause a fatal
error during formatting of partitions; the current behavior is to create
successfully allocated partition, but to NOT create unsuccessfully allocated
However, this issue is not handled optimally, since a user who creates an
unallocated partition is not warned of the unallocated open issue ...thanks for
deferring for a more optimum solution (w/including warning message to the user
when unallocated partitions exist upon exiting disk druid...) ...