[FFe] Ubiquity

I'm in favor of this FFe happening, but considering it is past the freeze date, there are a handful of deficiencies I'd like to point out that should be taken into consideration and/or fixed before uploading.

fixes still needed:
* ubiquity-dm is still busted. The drawing of the background image doesn't work with Gtk3/Gdk3 and still needs to be converted to cairo or the appropriate tool.
* the wireless and webcam pages are not preseedable
* oem-config can't query frontends anymore, meaning it won't start on first boot

important to note:
Any third party ubiquity plugins will also need to still be refreshed for pygi now. I've already handled some of mine in dell-recovery in a local branch, but edubuntu and mythbuntu plugins come to mind too.

> * the wireless and webcam pages are not preseedable

I'd prefer to handle this by skipping them entirely when --automatic is set. Do you have a use case for preseeding either of these pages?

> I'd prefer to handle this by skipping them entirely when --automatic is set. Do you have a use case for preseeding either of these > pages?
No I don't have a usecase for them in automatic mode, I think that's a fine alternative.

And it's a trivial change for the webcam and wireless skip in automatic, i've committed that to bzr.

I've also committed a fix for oem-config -q to test for DISPLAY. The only remaining thing in the list of things to fix that I outlined will be ubiquity-dm then.

The issues from comment 1 are bug fixes, so these seem fine. Which other features will still land aside from the PyGI port? The webcam integration?

Thanks Mario!

Martin,
Webcam integration and the wireless page will land alongside the PyGI port.

Seems ok to me at this point, we are pre UIF still, and we can just disable the new pages again if they don't get ready in time.

This bug was fixed in the package ubiquity - 2.7.15

---------------
ubiquity (2.7.15) oneiric; urgency=low

  [ Colin Watson ]
  * Remove dead code from debian/oem-config.oem-config.upstart.
  * Prefer recent versions of ntfs-3g to ntfsprogs, as ntfsresize has moved
    to ntfs-3g.

  [ Evan Dandrea ]
  * Change the first partitioning page title to 'Installation Type.'
    Thanks Matthew Paul Thomas.
  * Merge PyGI branch. Ubiquity now uses PyGI and GTK+3.
  * Feature Freeze exception (LP: #825274).
  * Automatic update of included source packages: base-installer
    1.119ubuntu4, console-setup 1.57ubuntu23, flash-kernel 2.28ubuntu28,
    netcfg 1.68ubuntu1, partman-auto-loop 0ubuntu20, partman-
    basicfilesystems 71ubuntu1, partman-efi 24ubuntu2, partman-
    partitioning 81ubuntu2, tzsetup 1:0.26ubuntu10, user-setup
    1.28ubuntu18.

  [ Brian Murray ]
  * Instead of sending people to +filebug recommend using apport

  [ Luke Yelavich ]
  * Add support for launching high contrast, screen reader, keyboard modifiers,
    and onscreen keyboard accessibility profiles in maybe-ubiquity mode, high
    contrast and screen reader profiles being launcheable either from an
    indicator, or via keyboard shortcut, the rest of the profiles available
    via the indicator only
  * bin/ubiquity-dm:
    - Start at-spi either when an appropriate accessibility profile is enabled,
      or when maybe-ubiquity mode is enabled
    - Remove references to orbit, as the a11y stack now uses dbus
  * debian/control: Add python-appindicator as a dependency of
    ubiquity-frontend-gtk
  * Play the system-ready sound once accessibility profile support code has
    been run to signal the user that a profile shortcut key can be pressed
  * Enable caret browsing/text cursor movement in the slideshow if the screen
    reader accessibility profile is enabled

  [ Mario Limonciello ]
  * Fix calls to get_size() in ubiquity-dm from pygi transition.
 -- Evan Dandrea <email address hidden> Thu, 18 Aug 2011 17:56:46 +0100

Good news first. I'm sure this fixed bug 743238 and I'm about 95% sure that this fixed bug 766265 but I need to repeat some more specific test cases to be sure.

Now the bad news. I tried a manual/advanced/"something else" install and after selecting "change" no changes are available. Please see the screenshot. Do I need to file a new bug report?

I can confirm the behavior that Erick's screenshot shows.
Aug. 22, 2011 daily/live image.
Tried on various partitions and HDDs on my system.

I filed bug 831649.