Gnome-settings-deamon fails to start.

Bug #56890 reported by PingunZ on 2006-08-19
This bug report is a duplicate of:  Bug #59217: [Edgy] gnome-settings-daemon acting up. Edit Remove
10
Affects Status Importance Assigned to Milestone
bonobo (Ubuntu)
Undecided
Unassigned
control-center (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: bonobo

I'm on Ubuntu Edgy.
My theme fails to start cause of gnome-settings-deamon. I cant change icons or gtk-themes.
here is my console output.

kristof@Edgy:~$ gnome-settings-daemon --gdk-debug=FLAGS

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'

(gnome-settings-daemon:17195): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80afda0'
,C4C[1155983636,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
kristof@Edgy:~$

Changed in bonobo:
importance: Untriaged → Medium
joostruis (joostruis) wrote :

This happens after loging out and in again.

my output:

joost@joost-desktop:~$ gnome-settings-daemon --gdk-debug=FLAGS
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'
(gnome-settings-daemon:6154): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80b7bd0'

Michael B. Trausch (mtrausch) wrote :

I am experiencing the same problem. However, sometimes, the problem goes away after attempting to restart the process a few times. So far, it seems about as unpredictable as a roll of D20, whether it will run or not... :-P

Yup, same here.
When you reboot the first time it works, second time maybe, third time it
crashes.

Cheers

2006/9/3, Michael Trausch <email address hidden>:
>
> I am experiencing the same problem. However, sometimes, the problem
> goes away after attempting to restart the process a few times. So far,
> it seems about as unpredictable as a roll of D20, whether it will run or
> not... :-P
>
> --
> Gnome-settings-deamon fails to start.
> https://launchpad.net/bugs/56890
>

Allen Ibara (uce-launchpad) wrote :

Same Issue Here

Current Edgy, PPC (32Bit Apple iBook G3)

I've discovered after some futzing that if I disable a gstreamer
plugin via:

sudo chmod a-r /usr/lib/gstreamer-0.10/libgstlibvisual.so

That it works around the problem. Possibly this means that this gstreamer plugin is causing it to crash (maybe miscompiled on ppc?). Notably gst-inspect-0.10 crashes too (until libgstlibvisual.so is disabled). Therefore it seems this may be a gstreamer (or gcc) bug.

Joseph Price (pricechild) wrote :

I can reproduce this behaviour with a restart of X

It is fixed with a reboot

Joseph Price (pricechild) wrote :

Sorry for making two posts, forgot to mention i'm running a k7 kernel so its not a problem with just the ppc compile Allen

saads (shakhshir) wrote :

I can confirm this bug as well. When I log off and log in again I get a gnome-settings-daemon error and my gtk/icon themes are gone. I've attached a screenshot.

jsage (jsage) wrote :

Confirming, same details as saads above, including error dialog and theme problems. Using edgy, theme engine is Murrine .10.

Can fix with ctrl-alt-backspace. Happens on every boot.

jsage : This bug is different
When you boot, it all goes well. When you restart x it fails.

Is that a typo you made or just another bug ?

Cheers

2006/9/9, jsage <email address hidden>:
>
> Confirming, same details as saads above, including error dialog and
> theme problems. Using edgy, theme engine is Murrine .10.
>
> Can fix with ctrl-alt-backspace. Happens on every boot.
>
> --
> Gnome-settings-deamon fails to start.
> https://launchpad.net/bugs/56890
>

jsage (jsage) wrote :

PingunZ,

Same error dialog as you, same error dialog as saads (see comment above mine), same affect on themes.

The only difference appears to be in boot behavior. I can fix mine with ctrl-alt-backspace. Can you?

thanks,
john

No. When I restart X everything goes wrong and can't be fixed.

Cheers

2006/9/9, jsage <email address hidden>:
>
> PingunZ,
>
> Same error dialog as you, same error dialog as saads (see comment above
> mine), same affect on themes.
>
> The only difference appears to be in boot behavior. I can fix mine with
> ctrl-alt-backspace. Can you?
>
> thanks,
> john
>
> --
> Gnome-settings-deamon fails to start.
> https://launchpad.net/bugs/56890
>

On Sat, 2006-09-09 at 21:31 +0000, PingunZ wrote:

> No. When I restart X everything goes wrong and can't be fixed.
>
> Cheers
>

You can restart it manually. It has taken me as many as five attempts
to get it to run and stay running. Other than that, the best solution
is a complete restart. I haven’t the faintest idea why it is behaving
this way, though.

To restart it manually, just press Alt+F2 to bring up the “Run” dialog,
and type “gnome-settings-daemon”. If it stays running, you do not have
to try again. :-P

    — Mike

--
The fd0man™—The Magical Floppy Man!
<email address hidden> or <email address hidden> — http://trausch.us/
"One world, one web, one program" —Microsoft promotional ad
"Ein Volk, ein Reich, ein Fuehrer" —Adolf Hitler

Sebastien Bacher (seb128) wrote :

Thanks for your bug. Reassigning to control-center which is the correct package and marking as duplicate of bug #59217 which already has a discussion running on the topic too. Allen, yourcomment about the libvisual gst plugin is interesting. Could you describe the gst-inspect issue and maybe open a gstreamer0.10 bug about it?

Changed in bonobo:
assignee: nobody → desktop-bugs
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers