You are not logged in.
when i start X /opt/gnome/bin/gnome-session error while loading shared libraries libdus-1.so.2 cannot open shared object file no such file or directory
waiting for x server to shut down freefontpath: FPE "user/shared/fonts/misc" refcount is 2 should be 1 fixing
can any one help me ?
Linux can run on any thing...
look at me
[img]http://img53.imageshack.us/img53/8413/indexol8.png[/img]
Offline
It seems the last update of dbus is "incompatible" with previous builds, which means that you should `ln -s /usr/lib/libdbus-1.so.3 /usr/lib/libdbus-1.so.2` to get everything compiled against the previous build of dbus to work.
Offline
Thanks a lot mate i got my Gnome back Ye
Linux can run on any thing...
look at me
[img]http://img53.imageshack.us/img53/8413/indexol8.png[/img]
Offline
You shouldn't symlink libs like that. You risk running into problems.
entvex: Make sure that you system is up-to-date (pacman -Syu). Maybe your mirror hasn't fully synced yet.
Offline
I had the same problem, caused by dbus 0.93's appreance into Current.
I had to fix it by manually loading dbus 0.62-3 like so:
pacman -S extra/dbus
I notice that dbus 0.62 is not listen in the online package database, so I don't promise you'll have it available (maybe it's only on my system by fluke?)
I keep seeing dbus 0.93 mentioned along with Gnome 2.16, and was wondering if perhaps the dbus update was prematurely put into current when Gnome 2.16 was moved to extra?
Offline
The gaim in current requires dbus version 0.93, but the gnome and xfce stuff apparently requires dbus version 0.62. I can't think of any way to run both without symlinking the library until the all the stuff that uses dbus is recompiled and blown out to the mirrors. Is there a better way to do this?
Offline
I ran into the exact same problem, with gnome-session 2.14.3-1, and fixed it the same way, with a symlink. I just mention this because this was on a fresh install of arch I just did.
p-Lo
Offline
Oh yeah and I also have dbus 0.93-1, which makes sense, i guess.
Offline
I keep seeing dbus 0.93 mentioned along with Gnome 2.16, and was wondering if perhaps the dbus update was prematurely put into current when Gnome 2.16 was moved to extra?
It's probably a mirror syncronisation issue. A lot of packages were moved from testing to current/extra. Probably users either didn't fully updated their system (pacman -Syu) or are using a mirror which haven't sync yet.
Also, make sure that you don't use a different mirror for current and extra. If you use an up-to-date mirror for current and a less up-to-date mirror for extra, you might get this kind of problem. You can temporarily switch to a more up-to-date mirror or to the main server to make this big update.
Offline
i use the arch mirror ? this must be up 2 date
Linux can run on any thing...
look at me
[img]http://img53.imageshack.us/img53/8413/indexol8.png[/img]
Offline
i use the arch mirror ? this must be up 2 date
You mean ftp.archlinux.org ? Maybe you tried to do the update when packages were still being moved from testing to current/extra. Also, there seems that at one point gnome and kde were in both the current and extra repo. It is fixed now but it might have done strange thing. Try doing a 'pacman -Syu' now to see if it will fix it (i.e. work without symlink).
Offline
My gnome and xfce packages work now without the symlink.
Offline
Upon checking the mirror lists, I found that some of the mirrors were ordered differently in the current and extra lists.
One had ftp.archilinux.org listed first, while the other put ftp.nethat.com at the top. Putting ftp.archlinux.org at the top of both lists solved my problems.
Should it be of concern that the mirror list did not match?
Offline
Yeah it certainly was the mirror lists for me too, I just had to make sure the same mirror was at the top of all the lists.
Perhaps /usr/bin/sortmirrors should not do every list separately, and should rather attempt to order at least the first half of current and extra the same. The fix was easy (reorder mirrors, or just wait a while...) but it seems to me like this whole issue is a sort of bug...
Offline