You are not logged in.
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The last error message was:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GNOME will still try to restart the Settings Daemon next time you log in.
$ gnome-settings-daemon
bash: gnome-settings-daemon: command not found
Are more people seeing this after upgrading from testing? Ideas how to resolve this?
Offline
I would suggest downgrading gnome-session to the version from extra again. If that fixes your problem, I will make some changes to the code that launches dbus in 2.18 (the code in 2.16 that we use is slightly different)
Offline
Downgrading gnome-session works like a charm. Thanks JGC.
Offline
I had the same problem. Downgrading worked like a charm.
Stefan Nitsche
stefan_at_nitsche_dot_se
Offline
After downgrading gnome-session package (with the one in extra) it's working fine.. Except a few more things:
1) There's an item in Applications->Accessories called Panel. When I click on it, it says that there's already a panel working..
2) GNOME Control Center is somehow hidden.. Typing gnome-control-center in the console is fine. It works.. But I don't know why it's not coming but default.. We still have the big old System menu..
Quis custodiet ipsos custodiet?
Offline
the reason it says there is a panel already running is because there is .. u clicked don a link to the actual gnome-panel ..
the control center menu option has always been hidden afaik .. there really is no need for it imho as the menus it is in has links to every control-center button.
The.Revolution.Is.Coming - - To fight, To hunger, To Resist!
Offline
The control-center shell is not completely done yet. They enabled it during the 2.17 series, to disable it for the 2nd beta or 1st RC again and switch back to the system -> preferences layout. It's possible to change some menu settings and unhide the control-center shell though.
About the panel: found that one too. Don't know why it's there, but it's a bug. I guess it's a .desktop file that should autostart the gnome panel, but somehow it got picked up by the menu structure.
Offline
issue with the settings daemon should be fixed with gnome-session 2.18.0-2, I reverted it to the unofficial 2.16.2 method we used.
The panel launcher is also explained: the .desktop file is added to /opt/gnome/share/applications for bug-buddy to pick up. It contains a NoDisplay=True, but True is not a valid boolean, it should be lowercase. I'll fix this in a later upload.
Offline
I guess it's good to try to keep all gnome 2.18 annoyances to this thread, so I'll add one to the heap: the gnome-power-manager icon in the status field is never there when I log in. Only way to get it to show is to killall gnome-power-manager, and then start it.
By the way, JGC, thanks a lot for the quick packaging! And quick fixing of all these issues!
Offline
The gnome-power-manager thing is something that appeared after switching to the GtkStatusIcon API. This bug appears because gnome-power-manager starts before the notification area is placed on the panel.
How's gnome-session doing now btw, does it still fail to startup the dbus daemon correctly, or does it work fine as it was with 2.16.2?
Offline
gnome-session is working just fine now. Thanks for that.
Weird thing with gpm. Is it an upstream bug?
Offline
How's gnome-session doing now btw, does it still fail to startup the dbus daemon correctly, or does it work fine as it was with 2.16.2?
Works perfect.
Offline