Results 1 to 2 of 2

Thread: Ubuntu GNOME ubiquity bug

  1. #1
    Join Date
    Apr 2008

    Ubuntu GNOME ubiquity bug

    Both Jeremy Bicha and I encountered a new ubiquity bug while testing the Beta 2 candidates:

    As you can see there it really only effects the "install alongside" option, but it's kind of hard to explain, and it's already been suggested that it may be a duplicate of this:

    I'm fairly certain that it's not a dupe so I'm stealing some electronic ink to post some screenshots for comparison with Lubuntu RR Beta 2 images. In both cases I started with a very simple setup:

    lubuntu@lubuntu:~$ sudo parted -l
    Model: ATA WDC WD800JB-00JJ (scsi)
    Disk /dev/sda: 80.0GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Number  Start   End     Size    Type      File system     Flags
     1      1049kB  77.9GB  77.9GB  primary   ext4            boot
     2      77.9GB  80.0GB  2137MB  extended
     5      77.9GB  80.0GB  2136MB  logical   linux-swap(v1)
    Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
    has been opened read-only.
    Error: Can't have a partition outside the disk!
    In both cases you need to simply select "Install alongside":


    Then with Lubuntu things work as expected, you're presented with the option to resize as you wish, and Install now is active:


    Then after clicking on Install now you're asked to confirm:


    But with Ubuntu GNOME only the Quit button appears to be active and you're not able to advance beyond that screen:


    After waiting and waiting for a long time clicking on Quit does not even appear to do anything but if I click on the X in the upper right-hand corner I do get this:


    Hopefully my pics will be worth a few thousand words.

  2. #2
    dino99's Avatar
    dino99 is offline Ubuntu addict and loving it
    Join Date
    Jun 2006
    Nux Jam
    Ubuntu Development Release

    Re: Ubuntu GNOME ubiquity bug

    could it that Ubiquity be disturbed by /dev/sr0 ? Maybe set the cdrom off inside the bios (if possible) or unplug it to see if ubiquity react differently.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts