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.008392
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 .. 23 24 25 26 27 28 29 30 31 32 33 .. 55 Next › Last »

<deleted-account> commented on 2016-08-12 19:43 (UTC)

Thanks korrode :) I've added fix-expo-offset.patch. The delay was due to me being away on holiday.

korrode commented on 2016-08-01 19:56 (UTC)

Hi Chazza, i noticed that Expo now gets offset for what i'd think is the panels in Ubuntu/Unity. I've adjusted it back in the manjaro-defaults.patch in compiz-manjaro, but here it is broken out if you want to change it back also: http://paradoxcomputers.com.au/arch/misc/fix-expo-offset.patch

<deleted-account> commented on 2016-07-14 11:28 (UTC)

@talessx No worries. Glad it's working for you now.

talessx commented on 2016-07-13 18:14 (UTC)

Thanks a lot Chazza, everything works fine now. I dont' know how also conky and cairo-dock are ok. I'm sure I updated all the system.

<deleted-account> commented on 2016-07-12 10:39 (UTC)

@kinoru Excellent. Glad the problem is solved. Note to all. Please do make doubly sure before posting here with a problem that your system is fully up to date (that includes this package). If you're holding back an update on some important piece of infrastructure (like gtk3 for instance) then mention that in your post. I'm quite happy to answer people's questions where I'm able but it really helps me (and others who might want to help as well) if we're starting with the assumption that the system is up to date. Thanks folks

kinoru commented on 2016-07-12 09:36 (UTC)

@Chazza You're right! I thought I upgraded compiz to the latest, but it wasn't really 0.9.13. Upgrading to the latest AUR release solved the problem. Thanks a lot!

<deleted-account> commented on 2016-07-12 07:44 (UTC)

@talessx expo does work, it's just that the edge binding has been set to none in the latest update. You can change it back yourself to the top left corner (or wherever) in the expo settings. Looking into this, it seems that what's happened is that there were some Ubuntu patches for Compiz that were applied downstream prior to 0.9.13. Now the patches are applied upstream which is why a bunch of default settings have changed. http://bazaar.launchpad.net/~compiz-team/compiz/0.9.13/revision/3981 As for cairo-dock and conky, I have no idea. I don't use those things. I'm afraid you'll have to figure that one out yourself unless somebody else chimes in. @kinoru Are you using Compiz 0.9.13? "org.gnome.metacity theme" is the old key. The new key is "org.gnome.metacity.theme name" (as has already been mentioned). If it's asking for the old key, that makes me think you haven't updated.

kinoru commented on 2016-07-12 03:48 (UTC)

The issue is the former - gtk-window-decorator is not running. The windows have no shadows they used to have, and nothing like "gtk-window-decorator" shows up in the result of `ps aux`. Running gsettings set org.gnome.metacity.theme name "Adwaita" and gsettings set org.gnome.metacity.theme type metacity did not help. gtk-window-decorator won't launch, and the only message it prints out is: (gtk-window-decorator:14913): GLib-GIO-ERROR **: Settings schema 'org.gnome.metacity' does not contain a key named 'theme' Trace/breakpoint trap (core dumped) Downgrading metacity to 3.18.4-1 solves the issue; gtk-window-decorator will launch fine. Any idea? BTW, thanks for your help and patience.

talessx commented on 2016-07-11 18:37 (UTC)

I have encountered 3 problems with last upgrade: 1) with cairo-dock: when windows cover the dock it becomes unavailable even trying to go on the appropriate zone with the mouse (the bottom for me) 2) "expo" effect doesn't work (show desktops effetc, for me, moving mouse on the left top corner of the screen) 3) while whatching full-screen flash videos (e.g. youtube) conky applets appear over the screen toghether with non-minimized windows Recompiling and downgrading the packages every works fine. Bye bye Alessandro

<deleted-account> commented on 2016-07-11 08:22 (UTC)

The gsettings command: gsettings set org.gnome.metacity.theme name "theme-name" changes which theme metacity uses. The idea is that gtk-window-decorator can read that setting and then also use that theme. This a throwback to the days of GNOME 2 where Compiz could be used as a drop in replacement for Metacity in a GNOME session. A user would want to be able to change the window decoration theme in the GNOME control center and have that setting take effect, no matter whether they were using Compiz or Metacity. That's why gtk-window-decorator reads Metacity's settings. The gsettings command: gsettings set org.gnome.metacity.theme type metacity makes Metacity use Metacity themes instead of GTK+ themes. Since GNOME (3.16?) Mutter stopped using Metacity themes and decided to use GTK+ themes for the window decoration. If I'm reading muktupavels' comment correctly then current Metacity supports both and gtk-window-decorator supports GTK+ themes in GNOME Flashback only and needs Metacity themes in any other session. I hope this clears things up. Now you need to tell us what your problem actually is. Is the problem that you have no window borders whatsoever - in which case gtk-window-decorator probably isn't running - or is the problem that the window borders are not using the theme that you like?