You are not logged in.
I'm not sure where the right place for such a question would be, but since this is a forum about the package manager and updates, I thought it might be a good place to start...
Recently (as of 2 days ago), Compiz started to depend on x11-xcb (via pkg-config), which would normally be installed by the libx11 package. But Arch currently supplies a version of libX11 without XCB support and hence, without x11-xcb.pc or libX11-xcb.so.
Some Googling suggests that XCB support may be omitted in order to lighten the dependencies of a base X server installation. Is that right?
I can't say how many projects are using or plan to use x11-xcb, but it would be nice to be able to build Compiz without also building my own version of libX11 --with-xcb.
Offline
Submit a feature request on the bugtracker.
Offline
We had a two versions of libx11 in testing with libxcb support enabled, it broke quite some applications. One of them were the ATI OpenGL drivers which we had to workaround by patching libxcb (and no, it's still not fixed in their drivers, yay to closed source software)
Offline
I get this error
[anonymo@james ~]$ fusion-icon
* Using the Qt4 Interface
* No module named PyQt4
... Trying another interface
* Using the Qt3 Interface
* No module named qt
... Trying another interface
* Using the GTK Interface
* libX11-xcb.so.1: cannot open shared object file: No such file or directory
... Trying another interface
* Error: All interfaces failed, aborting!
[anonymo@james ~]$
Edit: using KdeMod.
Last edited by Anonymo (2007-08-13 06:24:10)
Offline
Anonymo, that's because you do not have libx11 compiled with xcb, get my libx11-xcb package from the compiz fusion repo.
Offline
It seems that the package is not recognized by pacman. It doesn't appear anywhere after a pacman -Sy. But files are on the server. Seems strange uh
Offline
I just fixed that, the package was missing from the database.
Offline
Thanks works great now.
Offline