You are not logged in.
Hi.
I usually have testing repo disabled, and I didn't have any package installed from that repo.
I enabled it in /etc/pacman.conf, and did
$ pacman -S gnome gnome-extraAfter upgrading, when I started a GNOME sessiong by logging into my account, the settings daemon wouldn't start, and the following dialog boxes appeared:
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 (timeout by message bus)
GNOME will still try to restart the Settings Daemon next time you log in.GStreamer failed to initialized
Error re-scanning registry, child terminated by signalWhen I tried to start it in a terminal, I got:
$ gnome-settings-daemon
gnome-settings-daemon: symbol lookup error: /usr/lib/gio/modules/libgvfsdbus.so: undefined symbol: dbus_watch_get_unix_fd
[1206926985,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationCould not initialize GStreamer: Error re-scanning registry , child terminated by signalThe problem got "solved" by downgrading back to the packages from the extra repo.
Last edited by Nuwanda (2008-03-31 10:11:31)
Offline
Was the forum the right place to post this?
I also thought about the bug tracker, but it seemed kind of arrogant to assume it was a bug ![]()
Offline
I'm using gnome 2.22, and I'm not having any problems with gnome-settings-daemon. Have you updated other packages from [testing] or just gnome? From what I understand, it creates problems to enable only a few packages from testing. http://bbs.archlinux.org/viewtopic.php? … 25#p339825
Offline
I'm using gnome 2.22, and I'm not having any problems with gnome-settings-daemon. Have you updated other packages from [testing] or just gnome? From what I understand, it creates problems to enable only a few packages from testing. http://bbs.archlinux.org/viewtopic.php? … 25#p339825
I enabled the testing repository in /etc/pacman.conf before doing "pacman -S gnome gnome-extra", so the dependencies which its version was not satisfied, should have been updated with the ones from testing. That was the point of my post, to notify that the dependencies or dependency versions of some of the gnome packages might be wrong.
The link does shed some light on the issue. Thanks.
Offline
This was fixed when the packages were moved to extra. Thanks.
Offline
This is still broken on ppc gnome 2.24 in extra. Was there a fix that the ppc port could implement?
Offline