Package Details: compiz-gtk 0.8.18-3

Git Clone URL: https://aur.archlinux.org/compiz-core.git (read-only, click to copy)
Package Base: compiz-core
Description: This is the latest stable release of Compiz without DE deps (Core w/o decorator)
Upstream URL: https://gitlab.com/compiz/compiz-core/
Licenses: GPL, LGPL, MIT
Submitter: ShadowKyogre
Maintainer: ShadowKyogre (isseigx)
Last Packager: ShadowKyogre
Votes: 52
Popularity: 0.029748
First Submitted: 2015-08-13 17:48 (UTC)
Last Updated: 2021-09-25 00:49 (UTC)

Latest Comments

kelvinhbo commented on 2022-02-23 13:51 (UTC)

It's so sad to see one of the things that made Linux so great and unique, get abandoned. I hope someone sometime will continue to develop compiz and make it as great as it used to be.

ShadowKyogre commented on 2021-09-25 00:51 (UTC)

Fixed building against librsvg 2.51.0+

A commit introduced in librsvg 2.51.0+ renamed librsvg/librsvg-features.h to librsvg/rsvg-features.h .

As a result, this broke the SVG plugin compile process. The following patch includes a fix for this, which will be submitted upstream soon.


For the curious, here's the commit in librsvg that caused this.

https://github.com/GNOME/librsvg/commit/b8c8756a0e8148afb2752acb62f06c57c917e4b4

ShadowKyogre commented on 2021-09-25 00:32 (UTC) (edited on 2021-09-25 00:33 (UTC) by ShadowKyogre)

Just inspected the directory the include flags were pulling from. Looks like the equivalent file got renamed.

╰─{($))>-< ls /usr/include/librsvg-2.0/librsvg
total 88K
 20K rsvg-cairo.h  8.0K rsvg-features.h   56K rsvg.h  4.0K rsvg-version.h

will need to fix the package to do a quick sed/patch.

ShadowKyogre commented on 2021-09-18 23:32 (UTC)

@maxkaspar :: Just tested building this and the -git suffixed version today. It affects both. I'll need to inspect what's going on in the build system that's causing it to not detect librsvg .

maxkaspar commented on 2021-09-16 21:30 (UTC)

Doesn't build:

svg.c:35:10: fatal error: librsvg/librsvg-features.h: No such file or directory 35 | #include <librsvg/librsvg-features.h>

axtor commented on 2021-04-19 19:17 (UTC)

@Techman35 I've been using the Compiz since about 2006 with Intel, AMD and NVIDIA. And I disagree that 9 is better than 8 in terms of responsiveness and rendering. 9 version often doesn't immediately draw the contents of windows on cold start.

Techman35 commented on 2021-04-17 01:06 (UTC)

@axtor I've using compiz for years i still see compiz 9 more responsive and smoother without tearing by default then compiz 8, i love compiz 8 cuz all plugin just works like the blur that still don't work on compiz 9, one thing i want to see in compiz 8 is the possibility to see minimize windows preview when scale plugin is active, that feature work on compiz 9, i've been jumping between 8 and 9 and i always end up using version 9, cuz definitely is more smooth and responsive then 8

axtor commented on 2021-03-30 23:52 (UTC) (edited on 2021-04-01 17:35 (UTC) by axtor)

Compiz 0.8 rocks! Compiz 0.9 has lags and other twitching. Many thanks to ShadowKyogre for the maintenance.

If anyone has AMD videocard (I've Vega 10) and there is a wide strip on the screen with artifacts when moving windows, then create a file /etc/X11/xorg.conf.d/20-amdgpu.conf:

Section "Device"
    Identifier "AMD"
    Driver "amdgpu"
    Option "TearFree" "true"
EndSection

PedroHLC commented on 2021-01-06 20:56 (UTC)

Missing some deps for building in a clean chroot:

Package 'xi', required by 'virtual:world', not found
Package 'xcursor', required by 'virtual:world', not found

Please add libxi and libxcursor to dependencies.

ShadowKyogre commented on 2020-06-16 04:20 (UTC)

@slut, @Qubezo - Hey guys. Sorry for the delay. Checked out what was going on and did the following.

  • set _use_marco=2 in the PKGBUILD
  • Installed marco-gtk2 from the AUR since it got moved there
  • Test compiled the window decorator
  • Checked binary links, links to marco-gtk2 installed prior to build

_use_marco=2 uses marco-gtk2 (<- basically for people who have trouble theming w/GTK3 stuff) _use_marco=1 uses marco (<- for people chill with GTK3 theming)

Which package do you guys have? (marco or marco-gtk2)

Qubezo commented on 2020-06-02 16:41 (UTC)

I can't use gtk themes window decorator anymore. Is there a fix for this?

slut commented on 2020-05-26 01:23 (UTC)

_use_marco=2 does not seem to be building gtk-window-decorator anymore since the last update, thus breaking the ability to use gtk themes in compiz.

glitsj16 commented on 2020-01-18 09:11 (UTC)

@spawn Have a look at the 2 messages below yours, they should be informative. Bottomline: download the PKGBUILD to a temporary dir, cd into that and run 'makepkg -rs'. After the build finishes, use 'pacman -U foo bar' to install both packages. I think your AUR helper is either broken or misconfigured.

spawn commented on 2020-01-18 08:21 (UTC)

Compiz-Core is no longer installable, now. Anyone got a fix for this? Getting this annoying error msg all the time: "Can not find package name : [==> Marco theme support enabled with GTK+3". I have tried completely removing mate, but then, same error :(

applebloom commented on 2019-11-24 11:39 (UTC)

@WCBROW01 I hade the same problem and solved it by building without an aur helper (which is yay for me).

WCBROW01 commented on 2019-11-10 17:21 (UTC)

I'm trying to build compiz-core on a system with the MATE desktop. I set _use_marco=1 and the build just fails with "Can not find package name : [==> Marco theme support enabled with GTK+3]" without any other output.

If I remove the line "msg "Using GTK+3 for gtk-window-decorator"" (on line 57), the build starts, but fails while building gtk-window-decorator.

glitsj16 commented on 2019-03-28 12:02 (UTC)

@JPB_9876 compiz-core isn't dependant on protobuf, but libcompizconfig is. You'll need to rebuild that against the updated protobuf to get compiz going again.

JPB_9876 commented on 2019-03-28 08:16 (UTC)

The update of protobuf to 3.7.0-1 seems to have broken compiz:

[user@brix ~]$ compiz --replace compiz (core) - Error: Couldn't load plugin '/usr/lib/compiz/libccp.so' : libprotobuf.so.17: cannot open shared object file: No such file or directory compiz (core) - Error: Couldn't load plugin 'ccp'

Reinstalling compiz-core (0.8.16.1-2) makes no difference. Rolling back to protobuf-3.6.1.3-1 fixes the problem.

Any ideas what needs to be done to fix this permanently?

Thank you!

glitsj16 commented on 2019-01-15 00:56 (UTC)

@ShadowKyogre: Thanks for the speedy fix. Your fix is definately the smarter one.

ShadowKyogre commented on 2019-01-15 00:12 (UTC)

@glitsj16:: After looking at the output of the packaging functions carefully, removing the line deleting "${pkgdir}/usr/share/applications/compiz.desktop" resulted it in only being made in the compiz-core package.

So I updated the PKGBUILD now to remove it from the REMOVE_THESE arrays altogether.

glitsj16 commented on 2019-01-13 21:02 (UTC)

The PKGBUILD for 0.8.16.1-1 errors out while building compiz-gtk. "${pkgdir}/usr/share/applications/compiz.desktop" should be added to the REMOVE_THESE array in package_compiz-core() and removed from that same array in package_compiz-gtk().

bugsmanagement commented on 2018-11-21 05:11 (UTC)

Should compiz-core provide compiz ? https://aur.archlinux.org/packages/compiz-manager/, only looks for 'compiz>=0.8.0' unfortunately.

WCBROW01 commented on 2017-07-27 22:08 (UTC)

@darcn I found a workaround for now. Change the _use_marco flag in PKGBUILD to 1. I'm not sure if you need marco installed for it to work, but my metacity theme works fine with this change.

quequotion commented on 2017-03-25 18:30 (UTC)

Would it be acceptable to add "compiz" to provides()?

Xiaoming94 commented on 2017-03-24 10:13 (UTC)

@ShadowKyogre We might need to update the PKGBUILD to betterfit the current situation of Mate/Marco Right now, it seems like that the GTK3 version of MATE is the one in the upstream repo, and marco-gtk2 is right now in AUR. Just a little heads up :)

PhotonX commented on 2016-11-23 21:17 (UTC)

ShadowKyogre, please add libprotobuf2 as dependency (or make dependency?).

vs220 commented on 2016-11-23 17:26 (UTC)

Fastor install libprotobuf2 https://aur.archlinux.org/packages/libprotobuf2/

Fastor commented on 2016-09-24 14:28 (UTC)

I have a problem. Can't understand why. /usr/lib/gcc/x86_64-pc-linux-gnu/6.2.1/../../../../lib/libcompizconfig.so: undef ined reference to `google::protobuf::Message::InitializationErrorString() const' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:487: gtk-window-decorator] Ошибка 1 make[3]: выход из каталога «/tmp/yaourt-tmp-fastor/aur-compiz-core/src/compiz-0. 8.12.3/gtk/window-decorator» make[2]: *** [Makefile:425: all-recursive] Ошибка 1 make[2]: выход из каталога «/tmp/yaourt-tmp-fastor/aur-compiz-core/src/compiz-0. 8.12.3/gtk» make[1]: *** [Makefile:560: all-recursive] Ошибка 1 make[1]: выход из каталога «/tmp/yaourt-tmp-fastor/aur-compiz-core/src/compiz-0. 8.12.3» make: *** [Makefile:465: all] Ошибка 2 ==> ОШИБКА: Произошел сбой в build(). Прерывание... ==> ОШИБКА: Makepkg не смог собрать compiz-core. ==> Перезапустить сборку compiz-core ? да/Нет [y/N] ==> ----------------------------------------------- ==>

nicman23 commented on 2016-07-16 09:34 (UTC)

Thanks for the addition of the gtk3 option :)

ShadowKyogre commented on 2016-05-07 21:56 (UTC)

Thanks to omnibus on #compiz-reloaded for spotting the core part of the PKGBUILD didn't fail gracefully if gtk-window-decorator wasn't built. The update in the PKGBUILD simply fixes those build problems. The release #'s bumped anyway in case anyone was affected by the non-graceful fallback.

ShadowKyogre commented on 2016-04-12 02:00 (UTC)

Updated w/workaround for mksrcinfo.

ShadowKyogre commented on 2016-04-12 01:45 (UTC)

Updated. For those of you using .SRCINFO parsing only AUR clients, I'll need to do an additional fix for toggling marco. mksrcinfo didn't take the disabled by default like I thought it would when pushing this S:.

ShadowKyogre commented on 2016-04-10 19:21 (UTC)

@twa022: Yeah, that was disabled earlier due to not wanting to build something that was limited to cairo only. On top of getting the error hardyh noticed fixed upstream, I'll be including the decorator again. Enabling Marco theme support will be supported through a variable in the PKGBUILD when this is updated too. The other small change that will come is that this'll be a split PKGBUILD for the decorator that comes bundled with the core. While this seems rather small, it's just in case this gets pulled into the repositories again (( if it's popular enough )). ----- @hardyh: I'm currently in the progress of migrating the tarballs to the ones on github. Furthermore, the errors you're running into are caused by glib 2.48. See https://git.gnome.org/browse/glib/commit/?id=6b57719 for more info. Hold on for a day or two while we get this sorted upstream (( PKGBUILDs for the tarballs on github are ready, I'm just waiting for this )).

twa022 commented on 2016-04-09 19:14 (UTC)

No window decorators are built by the PKGBUILD as is. I think you need --enable-gtk (defaults to 2.0, can override with --with-gtk=3.0). Also should probably add a --disable-schemas-compile flag to ./configure and add an install file to recompile the schema database (https://wiki.archlinux.org/index.php/GNOME_package_guidelines)

hardyh commented on 2016-04-09 17:00 (UTC)

compiz-core 0.8.12-1 is not instalable: ==> Entpacke Quellen... -> Entpacke compiz-core-0.8.12.tar.xz mit bsdtar ==> Beginne build()... m4/glib-gettext.m4:39: error: m4_copy: won't overwrite defined macro: glib_DEFUN m4/glib-gettext.m4:39: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte compiz-core nicht erstellen.

ShadowKyogre commented on 2016-03-27 17:30 (UTC)

http://blog.northfield.ws/compiz-release-announcement-0-8-12/ Hurp, meant to link to that too

ShadowKyogre commented on 2016-03-27 17:20 (UTC)

Sorry for the huge delay everyone. I was waiting for this to appear: http://www.northfield.ws/projects/compiz/releases/0.8.12/ Why? It also has details on where the official git repos are now. Boy this is going to be a loooong Sunday.