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.47
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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 53 Next › Last »

<deleted-account> commented on 2019-02-18 18:10 (UTC)

@ector, that looks like a bug and you need to report it upstream. Techman35 reported something very similar in compiz-git a few days ago, about ccsm struggling with unicode characters. Python 2 and 3 handle unicode differently and CCSM was ported to Python 3 for this release so that could have something to do with it - I can't reproduce this myself. In the meantime,I suggest you downgrade to 0.9.13.1-5.

ector commented on 2019-02-18 16:51 (UTC) (edited on 2019-02-20 12:53 (UTC) by ector)

hi, chazza ccsm not start whit new version compiz

[code] ector ~ $ ccsm compizconfig - Info: Backend : ini compizconfig - Info: Integration : true compizconfig - Info: Profile : default Traceback (most recent call last): File "/usr/bin/ccsm", line 122, in <module> mainWin = ccm.MainWin(context, plugin, category) File "/usr/lib/python3.7/site-packages/ccm/Window.py", line 55, in init self.MainPage = MainPage(self, self.Context) File "/usr/lib/python3.7/site-packages/ccm/Pages.py", line 1209, in init pluginWindow = PluginWindow(self.Context) File "/usr/lib/python3.7/site-packages/ccm/Widgets.py", line 1642, in init category_box = CategoryBox(context, category, plugins, i) File "/usr/lib/python3.7/site-packages/ccm/Widgets.py", line 1506, in init self._plugins.sort(key=PluginKeyFunc) File "src/compizconfig.pyx", line 943, in compizconfig.Plugin.ShortDesc.get UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 12: ordinal not in range(128) [/code]

<deleted-account> commented on 2019-02-17 15:32 (UTC)

@nfishr The reason that error message appeared at the end of the build was because the Compiz build system tries to call glib-compile-schemas on /usr/share/glib-2.0/schemas at the end of the build. This fails because Arch packages are built as an ordinary user, not root, so glib-schemas-compile does not have write permissions on that directory, hence the permission denied error.

But it's a completely harmless error as I said earlier, because we don't need the Compiz build system to trigger a glib schemas recompile as that's handled by a pacman hook at install time. And before we had pacman hooks we had those ${pkgname}.install scripts which did the same thing.

The error has been at the end of every Compiz build since before I was maintainer. I never looked into what precisely caused it because it was a non-issue (one can verify that the Compiz gschemas are installed correctly by opening the dconf editor and looking for the org.compiz entries) and nobody ever complained until now.

As to why your build failed earlier, I can only guess because you never showed me the terminal output. But my assumption would be that you're using some sort of AUR helper that somehow picked up on the non-zero exit code of glib-compile-schemas and and interpreted that to mean that the entire packaging process had failed, thus stopping it in its tracks. But that's just a blind guess.

nfishr commented on 2019-02-17 11:33 (UTC)

@Chazza thanks for the quick reply. Indeed the error is now gone, and the compilation went through flawlessly. Since you're saying that the error I encountered was not critical, I'm now not sure what caused it to fail the other day.

<deleted-account> commented on 2019-02-16 23:56 (UTC)

Ok, seeing as people lately have been complaining about the permission denied error when glib-schemas-compile is called during the make install process, I've added a patch which will silence this error. The error isn't actually of any importance - glib schemas automatically get compiled by a pacman hook on installation/upgrade/removal so there's no need for them to be compiled during the package build process. But anyway, its fixed now.

<deleted-account> commented on 2019-02-16 23:08 (UTC)

@nfishr The "Failed to create file “/usr/share/glib-2.0/schemas/gschemas.compiled.QDJCXZ”: Permission denied" error message has been around for ever. It shouldn't halt compilation.

Seeing as a people lately have been complaining about this error, I've added a patch which will silence it. The error isn't actually of any importance - glib schemas automatically get compiled by a pacman hook on installation/upgrade/removal so there's no need for them to be compiled during the package build process. But anyway, its fixed now.

nfishr commented on 2019-02-16 23:03 (UTC)

Does not compile for me.

Failed to create file “/usr/share/glib-2.0/schemas/gschemas.compiled.QDJCXZ”: Permission denied

not sure how to fix this

<deleted-account> commented on 2019-02-16 22:50 (UTC)

Corrected, cheers!

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 53 Next › Last »