Package Details: compiz

Git Clone URL: (read-only)
Package Base: compiz
Description: Composite manager for Aiglx and Xgl, with plugins and CCSM
Upstream URL:
Licenses: GPL, LGPL, MIT
Conflicts: ccsm, compiz-bcop, compiz-core, compiz-fusion-plugins-experimental, compiz-fusion-plugins-extra, compiz-fusion-plugins-main, compiz-gtk, compizconfig-python, libcompizconfig, simple-ccsm
Provides: ccsm=, compiz-bcop=, compiz-core=, compiz-plugins-extra=, compiz-plugins-main=, compizconfig-python=, libcompizconfig=
Submitter: Chazza
Maintainer: Chazza
Last Packager: Chazza
Votes: 137
Popularity: 0.965204
First Submitted: 2014-08-04 13:22
Last Updated: 2017-12-10 19:06

Required by (28)

Sources (6)

Latest Comments

Chazza commented on 2017-12-10 10:25

@japp1egate Hi there. Ah I see, you used a non-standard installer. That explains things. Please would you mention that in the future? I'm still happy to help but that needs to be upfront so that we know where we stand. As for the version number, I sorry I completely forgot to mention. That's a bug that's been there for ages. I think upstream just forgot to update the version reporting function. I could patch it myself but I don't think it's worth making everybody rebuild. So that's nothing to worry about. Anyway, I'm glad you got it working. Let me know if there are further issues.

EDIT: there we go, I fixed the version for you. Looks like upstream already got round to it as well.

japp1egate commented on 2017-12-09 21:29


Solved and sorted! Well...mostly. It would appear that the non-standard repos installed by Zen by default are not properly synchronized with official/AUR, and I was getting a jank-tastic compiz version where ccsm didn't work as a result.

I've just finished rebuilding compiz from AUR, but --version still shows This leaves me mildly befuddled, but at least (in all other ways so far) it's working.

Any ideas why I might still be seeing the old version number?

Sorry for being bothersome.

japp1egate commented on 2017-12-09 21:17


I'm operating under the assumption that I've done something fantastically moronic in using this Zen installer for Arch. There were a couple of questionable repositories in my pacman.conf which I've now commented out (revenge_repo and spooky_aur). I've removed my previous compiz install (which showed --version as being and am now rebuilding from AUR. Will update here with results once the process is complete.

japp1egate commented on 2017-12-09 19:42


1) You are correct, and I apologize for not communicating clearly where my compiz came from. This is a fresh "compiz" install/build from AUR.

2) I'm afraid that "compiz --version" is reporting, even though I see on the AUR that the compiz that I apparently have installed should be

3) To the best of my knowledge, has never been on this machine. As I mentioned before, this is a fresh Arch install, but it has installed. I'm not sure whether it makes any real difference, but I used the Zen installer (used to be OBRevenge). Where/how might I either get the previous version of or make compizconfig look for

I really appreciate your help, @Chazza!

Chazza commented on 2017-12-09 09:43

Hi @japp1egate. A couple of quick things:

1) ''I've gotten past the issue I'd reported by installing the package "compiz" from the repo, rather than "compiz-manjaro"''

You mean you installed compiz from the AUR, right? Neither compiz (this package), nor compiz-manjaro nor any other compiz packages are in the Arch repositories. It would actually be against policy for this package to be in the AUR and the official repositories at the same time.

2) ''Now that I have compiz running''

You should have installed, not I updated this PKGBUILD to point to in November 2016. Was this a typo or are you actually trying to use the older version??

3) ''I cannot launch ccsm.''

So what you've got there is a dynamic linking issue. The compiz you've installed is linked against a particular version of the libprotobuf library. The version it's linked against is no longer on your machine because it was replaced by a newer version in an update. The correct way to resolve this is simply to rebuild compiz against the newer version of libprotobuf.

japp1egate commented on 2017-12-09 09:15


You were correct in that this was not an actual Compiz problem. I've gotten past the issue I'd reported by installing the package "compiz" from the repo, rather than "compiz-manjaro" (installed due to sleep-deprivation). This led me to installation of proper nVidia graphics driver, as something had somehow hosed my display. Solved that (not related here).

Now that I have compiz running, I cannot launch ccsm.

$ ccsm Traceback (most recent call last): File "/usr/bin/ccsm", line 93, in <module> import compizconfig ImportError: cannot open shared object file: No such file or directory</module>

Is the compizconfig that it's trying to import a file I can edit, wherein I might change the entry from to, which actually resides on my machine?


japp1egate commented on 2017-12-08 23:12


I'll investigate those links, but this is a fresh install of Arch, and I did not conciously install Python to any non-standard location.

Let me see what I can find at those links you provided. If/when I come to a conclusion, I will post here again to update, in case anyone else has the same problem and thinks it's a Compiz issue.

Thanks for helping, @Chazza!

Chazza commented on 2017-12-08 08:31


I've rebuilt Compiz and it builds fine. I couldn't reproduce the error you mentioned. So unless someone else can confirm, I don't think there's a problem with the Compiz PKGBUILD. Looking at that error, I'm wondering whether perhaps you've installed python to a non-standard location? There are a couple of bug reports for this:

Chazza commented on 2017-12-06 21:02


Hiya. Nope, never seen that before. Or not that I remember anyway. Yes, you've raised this in the right place. Build issues should be reported to the package maintainer. I'm very, very busy at the moment unfortunately but I will try and fix this tomorrow if I have time, otherwise it might have to wait until the weekend.

japp1egate commented on 2017-12-06 20:35

/usr/src/compiz-$ sudo mkdir build

/usr/src/compiz-$ cd build

/usr/src/compiz-$ sudo cmake ..

. . .

CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: PYTHON_LIBRARY_LOCAL linked by target "compizconfig_python_module" in directory /usr/src/compiz-

From /usr/src/compiz-

CMakeFiles/cmTC_84d35.dir/CheckSymbolExists.c.o: In function main': CheckSymbolExists.c:(.text+0x1b): undefined reference topthread_create' collect2: error: ld returned 1 exit status make[1]: [CMakeFiles/cmTC_84d35.dir/build.make:98: cmTC_84d35] Error 1 make[1]: Leaving directory '/usr/src/compiz-' make: [Makefile:126: cmTC_84d35/fast] Error 2

... and further toward the bottom of the log:

/usr/bin/ld: cannot find -lpthreads collect2: error: ld returned 1 exit status make[1]: [CMakeFiles/cmTC_b3337.dir/build.make:98: cmTC_b3337] Error 1 make[1]: Leaving directory '/usr/src/compiz-' make: [Makefile:126: cmTC_b3337/fast] Error 2

As this is my first time attempting to compile Compiz, I am uncertain as to whether I am bringing this issue to the correct folks. @Chazza - since you are the package maintainer, have you encountered this failure in the past?

(edited to clean up formatting a bit.)

All comments