Package Details: compiz 0.9.14.2-9

Git Clone URL: https://aur.archlinux.org/compiz.git (read-only, click to copy)
Package Base: compiz
Description: Composite manager for Aiglx and Xgl, with plugins and CCSM
Upstream URL: https://launchpad.net/compiz
Licenses: MIT, GPL-2.0-or-later, LGPL-2.1-or-later
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: None
Maintainer: xiota
Last Packager: xiota
Votes: 165
Popularity: 0.009300
First Submitted: 2014-08-04 13:22 (UTC)
Last Updated: 2024-10-31 17:58 (UTC)

Required by (28)

Sources (9)

Latest Comments

« First ‹ Previous 1 .. 38 39 40 41 42 43 44 45 46 47 48 .. 55 Next › Last »

nuc commented on 2014-03-05 15:01 (UTC)

0.9.11 is out

devrs0 commented on 2014-01-26 22:04 (UTC)

Updated to enable GTK/Metacity by default as per compiz-bzr

<deleted-account> commented on 2014-01-26 13:01 (UTC)

@zhqh100 the comments in the compiz-bzr package suggest that you need metacity installed to build compiz even if metacity support is set to off in the PKGBUILD. As a heads up to all users who may not be aware, the window decoration options in this PKGBUILD are all disabled. If you want compiz-decorator-gtk you will need to set the options below to on: # GTK window decorator support GTKWINDOWDECORATOR="off" # Metaciy theme support for GTK window decorator METACITY="off"

zhqh100 commented on 2014-01-26 05:35 (UTC)

fatal error: metacity-1/metacity-private/theme.h: No such file or directory #include <metacity-1/metacity-private/theme.h> ^ How to solve this problem?

korrode commented on 2013-11-01 17:49 (UTC)

in compiz-dev.install, there's a number of references to: usr/share/gconf/schemas/$pkgname.schemas which I assume are working anyway, but to be safe/correct should have a prefixed forward-slash: /usr/share/gconf/schemas/$pkgname.schemas

devrs0 commented on 2013-08-27 16:13 (UTC)

Seems to be an issue with the included libs from your xorg. I'm not sure how compatible this is the latest xorg versions. I built this using xorg 1.13.

<deleted-account> commented on 2013-08-27 14:18 (UTC)

This package fails to build for me with the error: In file included from /var/tmp/yaourt-tmp-rob/aur-compiz-dev/src/compiz-0.9.10.0/src/screen.cpp:55:0: /usr/include/X11/extensions/XInput2.h:173:22: error: conflicting declaration ‘typedef unsigned int BarrierEventID’ typedef unsigned int BarrierEventID; ^ In file included from /usr/include/X11/extensions/XInput2.h:33:0, from /var/tmp/yaourt-tmp-rob/aur-compiz-dev/src/compiz-0.9.10.0/src/screen.cpp:55: /usr/include/X11/extensions/Xfixes.h:274:17: error: ‘BarrierEventID’ has a previous declaration as ‘typedef int32_t BarrierEventID’ typedef int32_t BarrierEventID; Am I the only one with this problem? Compiz-bzr package does the same thing.

nuc commented on 2013-08-12 01:18 (UTC)

Compiz stable might be dropped from the repos but it still exists in the AUR: https://aur.archlinux.org/packages/compiz/ So it is only resonable to mark dev versions as dev and stable as stable, even if only to avoid confusion. I don't see the point in renaming and calling it stable branch if it's an unstable branch. Renaming brings no gain at all, but has only negatigve effects. Keeping the current name does make totally sense here, changing it doesn't.

whynothugo commented on 2013-08-11 16:45 (UTC)

I've used 0.9.x for over two years now, without ever using (or installing) unity, and fail to see any issues. In any case, arch has dropped 0.8, so we can consider it depricated (even though upstream differs).

« First ‹ Previous 1 .. 38 39 40 41 42 43 44 45 46 47 48 .. 55 Next › Last »