When g-s-d is started by DBus, you need to call
org.gnome.SettingsDaemon.Awake to get it to load any plugins
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/854717
Title
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Status: New => Triaged
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Importance: Undecided => High
** Changed in: gnome-settings-daemon (Ubuntu Oneiric)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop
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 spa
** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/854717
Title:
Broken panel icons and dialog style during ubiquity-dm and OEM
install/fi
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.
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,
