Package Details: compiz 0.9.14.2-5

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
Keywords: ccsm
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.74
First Submitted: 2014-08-04 13:22 (UTC)
Last Updated: 2024-03-24 22:06 (UTC)

Required by (27)

Sources (6)

Pinned Comments

<deleted-account> commented on 2018-09-14 14:00 (UTC)

When library names like libprotobuf.so.XX change you just need to rebuild compiz. It's not a problem with the PKGBUILD. This is normal for AUR packages. Packages in the official repos also get rebuilt when libraries are updated.

Note that you shouldn't symlink new library names to old. This will create problems for you further down the line.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 53 Next › Last »

robson commented on 2021-05-10 10:54 (UTC) (edited on 2021-05-10 11:11 (UTC) by robson)

I too have never had a problem with compiz working, I recently rebuilt it after updating protobuf, i.e. April 19 and everything worked very well. I think this is due to the changes made 9 days ago https://git.launchpad.net/compiz

AndyM48 commented on 2021-05-10 10:33 (UTC)

I normally have to rebuild after a linux update, but apart from that I never seem to have any problems. I use compiz stand-alone.

robson commented on 2021-05-10 09:52 (UTC) (edited on 2021-05-10 09:53 (UTC) by robson)

What is going on with compiz? Because after building it often crashes, well the screen jumps. At first I thought it was the fault of the new protobuf, but this problem also occurs on the current version of protobuf.

<deleted-account> commented on 2021-04-05 21:09 (UTC)

I'm dropping compiz and compiz-git. I don't use them anymore so it makes more sense that an active user continue maintenance.

lectrode commented on 2021-03-15 21:24 (UTC) (edited on 2021-03-15 21:49 (UTC) by lectrode)

@robson @Chazza Thank you for checking. Glad to know it doesn't affect everyone. I'll keep digging. Maybe I did something weird in my bash environment

EDIT: Ended up being my version of glib2. Does not affect the version included in the arch repos.

<deleted-account> commented on 2021-03-15 21:22 (UTC)

Just rebuilt compiz and I'm unable to reproduce this one. Sorry.

robson commented on 2021-03-15 20:54 (UTC)

I rebuilt compiz yesterday after the protobuf update, and the build went without any problems.

lectrode commented on 2021-03-15 20:23 (UTC)

Still investigating, but currently I cannot compile this or compiz-git for the protobuf update. Getting this repeating error during the build:

Package >= was not found in the pkg-config search path.
Perhaps you should add the directory containing `>=.pc'
to the PKG_CONFIG_PATH environment variable
Package '>=', required by 'glib-2.0', not found
Package '3.38.0', required by 'glib-2.0', not found

On first glance it seems like a build dependency update introduced a bug, as it's reading '>=' as a package name)

So far I've tried * downgrading cmake to 3.18.4 * downgrading cython to 0.29.21

Anyone else running into this issue?

Autodidaddy commented on 2021-03-03 01:58 (UTC) (edited on 2021-03-09 20:03 (UTC) by Autodidaddy)

Tnx. I'll try workarounds next. I noticed enabling 'Animations Plus' was causing compiz to crash completely at random times. Then I disabled all animations and I haven't had any issues so far.

edit; keep having issues. I have the workarounds enabled now. I was also having issues with the screenshot plugin (very important to me) in that the shots were now faded. Workaround was to disable the selection indicator. Not acceptable.

edit; turns out to be the kernel!! see https://bbs.archlinux.org/viewtopic.php?id=263401

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 53 Next › Last »