You are not logged in.
I've just had to make a quick fix for an issue with Awesome wm crashing at X start up over the xcb-util package, and I'm trying to work out who, if anyone, I should submit a bug report to. While awesome was in the AUR I was using a third party repository to install the awesome and cairo-xcb packages. This evening I did a package upgrade, and noticed that awesome 3.4.11-5 was in community and extra/cairo 1.12.2-1 now apparently provided cairo-xcb through extra/xcb-util 0.3.9-1, so I decided to change to the official packages. After the upgrade finished though, awesome had an error on start-up:
awesome: error while loading shared libraries: libxcb-util.so.0: no such file or directoryAs a quick fix to the problem I added a symlink to libxcb-util.so, and awesome runs fine now. However, I'm stuck on where I should report this. I couldn't find any reports of this problem happening recently on the forums, so it could just be my system. If not, is it the packager's responsibility to make sure that the cairo package actually does provide the dependencies awesome needs? Or is this an upstream issue with how the cairo devs are naming their library files?
Kinda confused here, so any advice is appreciated.
Last edited by sunghail (2012-06-07 01:40:38)
Offline
Your system is not up-to-date. As you can see, awesome 3.4.11-5 is linked against libxcb-util.so.1.
readelf -d /usr/bin/awesome | grep xcb-util
0x0000000000000001 (NEEDED) Shared library: [libxcb-util.so.1]So it must be another library that depends on this old library.
Offline
I have the same problem, but apparently on my system, awesome 3.4.11-5 is linked against libxcb-util.so.0, which doesn't exist.
readelf -d /usr/bin/awesome | grep xcb-util
0x0000000000000001 (NEEDED) Shared library: [libxcb-util.so.0]find / -name "libxcb-util.so*"
/usr/lib32/libxcb-util.so.0
/usr/lib32/libxcb-util.so
/usr/lib32/libxcb-util.so.0.0.0
/usr/lib/libxcb-util.so.1.0.0
/usr/lib/libxcb-util.so
/usr/lib/libxcb-util.so.1Symlinking libxcb-util.so to libxcb-util.so.0 fixed it for me as well, awesome appears to work just fine.
Offline
Symlinking is absolutely not the appropriate way to solve such problems since it can lead to very strange behaviour. I guess the real issue is that you are not using the official package from community (check packager in pacman -Qi awesome; it's not seblu for you). Supposely, you have installed awesome originally from the archlinux.fr repository and since the maintainer did not mind to keep the package version in sync with the AUR package you are left with a broken package. Their package awesome-3.4.11-5 is from 6 February while the official package was updated to 3.4.11-5 just 6 days ago.
Lesson learnt: When you encounter such missing library issues and you are using unofficial repositories (especially archlinux.fr), always check if packages from there are involved.
Offline
Lesson learnt indeed. Thanks very much for your help.
Offline