[Bug 59217] [Edgy] gnome-settings-daemon acting up
Toby Smithe
toby.smithe at gmail.com
Thu Sep 7 02:52:58 UTC 2006
Public bug reported:
Sometimes it starts, others it doesn't. Here is the output on the
terminal of one time it didn't:
toby at leopard:~$ gnome-settings-daemon &
[1] 6430
toby at leopard:~$
(gnome-settings-daemon:6430): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80a3c90'
(gnome-settings-daemon:6430): GLib-GObject-WARNING **: gsignal.c:2269:
signal name `new-toplevel_window' is invalid for instance `0x80a3c90'
(gnome-settings-daemon:6430): GLib-GObject-WARNING **: gsignal.c:2269:
signal name `new-toplevel_window' is invalid for instance `0x80a3c90'
(gnome-settings-daemon:6430): GLib-GObject-WARNING **: gsignal.c:2269:
signal name `new-toplevel_window' is invalid for instance `0x80a3c90'
(gnome-settings-daemon:6430): GLib-GObject-WARNING **: gsignal.c:2269:
signal name `new-toplevel_window' is invalid for instance `0x80a3c90'
(gnome-settings-daemon:6430): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80a3c90'
#&'([1157562290,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationCould not initialized GStreamer: unknown error occurred
** Affects: control-center (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
[Edgy] gnome-settings-daemon acting up
https://launchpad.net/bugs/59217
More information about the desktop-bugs
mailing list