g-s-d crashes on startup under edgy

Bug #60477 reported by Paul Sladen on 2006-09-14
This bug report is a duplicate of:  Bug #59217: [Edgy] gnome-settings-daemon acting up. Edit Remove
2
Affects Status Importance Assigned to Milestone
control-center (Ubuntu)
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

gnome-settings-daemon crashes as soon as it is loaded, consequently everything turns blue or doesn't work.

Paul Sladen (sladen) wrote :

$ gnome-settings-daemon

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

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

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

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

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

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

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

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

(gnome-settings-daemon:9607): GLib-GObject-WARNING **: gsignal.c:2269: signal name `new-toplevel_window' is invalid for instance `0x80bce70'
�%�%[1158273707,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

Paul Sladen (sladen) wrote :

Starting under:

  $ strace -f gnome-settings-daemon

slows things down enough for whatever was causing the race condition(?) to disappear.

Sebastien Bacher (seb128) wrote :

What version of the package do you use? How does "everything turns blue"? Could you make a screenshot? Do you use compiz or spifacity?

Changed in control-center:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Jos Dehaes (jos-dehaes) wrote :

I have the same with up-to-date edgy, and no special effects turned on (no AIGLX, XGL, compiz, just plain GNOME with metacity). The effect is that your theme is gone, and you are stuck with the old hard-edged theme and colours.

Jos Dehaes (jos-dehaes) wrote :

Mostly it works the first time you log on after a boot, and loging out/in causes this. Will try to get some more info with strace or GDB.

Jos Dehaes (jos-dehaes) wrote :

As stated by Paul, I can not reproduce with strace either. So a race condition/timing issue is the most probable cause?

Sebastien Bacher (seb128) wrote :

marking as duplicate of bug #59217

Changed in control-center:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers