Broken panel icons and dialog style during ubiquity-dm and OEM install/final user configuration

[Jean-Baptiste Lallement]

Oneiric Alternate 20110920.4 OEM Installation
Oneiric Desktop 20110920

During the configuration of the final user, the icons on the top panel are broken and the style of the dialog is weird (no title and labels, the pink style of the top part of the dialog and panel menus)
Screenshot attached.

Tested on VM and HW with same result.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Tue Sep 20 15:24:53 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110920.4)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Jean-Baptiste Lallement (jibel)]

screenshot of ubiquity welcome screen.

[Carla Sella (carla-sella)]

During test of live usb persistent key I have the same problem of broken icons and a pink dialog.

[Evan (ev)]

After investigating, it looks like gnome-settings-daemon isn't setting the theme, despite running.

[Evan (ev)]

*** (gnome-settings-daemon:1305): WARNING **: Name taken or bus went away - shutting down

[Martin Pitt (pitti)]

I see two processes during the greeter: One which is in state "Z" (zombie), and one running. The zombie one is a child of ubiquity-dm, the running one of init.

A killall -9 gnome-settings-daemon, and restarting it helps. That doesn't clean up the zombie, of course.

So it seems that there are two g-s-d's racing at each other, ubiquity-dm tries to start a second one, but that one fails because the bus name is already taken?

[Martin Pitt (pitti)]

Indeed when I boot the image, I can see the panel being built with the correct icons, and then they change to the broken ones.

[Martin Pitt (pitti)]

I temporarily chmod 0'ed the session, application, sound, and power indicator libs in /usr/lib/indicators3/6/, and that caused g-s-d to start up properly. I still have a gnome-screensaver process running, I don't know where that is coming from (perhaps from g-s-d itself), but that doesn't seem to be the one which triggers the early g-s-d. So I suppose one of the indicators invokes g-s-d as well, races with the other instance, and fails.

[Martin Pitt (pitti)]

It is the loading of libpower.so in src/panel/panel.c which triggers the early gnome-settings-daemon.

As a workaround for beta-2 I suggest to just disable this from indicators[]:

        // Reboot, shut down, ...
        "/usr/lib/indicators3/6/libpower.so",

The comment is misleading, reboot, shutdown etc. are done from the session indicator. The power indicator only shows your battery charge. While that's good to have as well, it's not crucial IMHO.

A more proper fix is probably to start the panel process after the gnome-settings-daemon one. It's not that simple, though, because you actually need to wait until g-s-d has registered to the bus (and time out in case it crashes). It might also be possible to fix the power indicator to not depend on settings-daemon, but that also seems out of scope for beta-2.

[Martin Pitt (pitti)]

Adding g-s-d task, as at the end of the day g-s-d should not fail to set the theme when being dbus activated through indicator-power.

Note that even if this works, ubiquity-dm then doesn't wait() for the g-s-d instance that it spawns, so the zombie process stays around. That's only a minor thing, though, it should not actually hurt.

[Martin Pitt (pitti)]

The early g-s-d spawned by indicator-power just has this to say:

** (gnome-settings-daemon.real:2789): WARNING **: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

Nothing else in the output. I got that by creating a shell wrapper with --debug and >/tmp/gsd.log 2>&1.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubiquity - 2.7.34

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

  * Disable setting the ubiquity/online debconf question for now. We're
    not actually using it for anything yet (LP: #855277).
  * Disable the power indicator as it's causing g-s-d to spawn, which
    races against our own spawning of it (LP: #854717).
 -- Evan Dandrea <email address hidden> Wed, 21 Sep 2011 10:00:45 +0100

[Chris Coulson (chrisccoulson)]

When g-s-d is started by DBus, you need to call org.gnome.SettingsDaemon.Awake to get it to load any plugins

[Martin Pitt (pitti)]

Ah, thanks Chris for pointing this out. So ubiquity-dm could check if it's already running; if so, call .Awake(), if not, launch it by itself.

I just talked to Javier, he'll change indicator-power to not activate g-s-d by itself, but just watch dbus for g-s-d to appear. That will also nicely take care of the problem. However, this isn't an oneiric blocker, so just keeping the floating task.

[Javier Jardón (jjardon)]

Fix committed to indicator-power in http://bazaar.launchpad.net/~jjardon/indicator-power/master/revision/112

[Carla Sella (carla-sella)]

On Oneiric Beta2 20110921.1 image the broken icons aren't there any more, everything seems ok and fixed.

[Jean-Baptiste Lallement (jibel)]

Thanks for verifying the fix Carla. That's much appreciated.

[Launchpad Janitor (janitor)]

This bug was fixed in the package indicator-power - 0.9-0ubuntu1

---------------
indicator-power (0.9-0ubuntu1) oneiric; urgency=low

  * New upstream release.
    - Use correct dgettext and g_dngettext calls (LP: #846895)
    - Ensure we use the same icon for all charge levels if we are in the
      charging status (LP: #824629)
    - Fix gap when the power indicator is not show (LP: #842188)
    - Do not show (charged) in menu title when fully charged (LP: #850011)
    - Do not activate g-s-d, but just watch dbus for g-s-d to
      appear (LP: #854717)
  * po/POTFILES.in
    - Fixed gsettings schema filename
  * debian/copyright
    - Removed an extra line to make dep5 compliant
 -- Ken VanDine <email address hidden> Fri, 23 Sep 2011 13:03:13 -0400