compiz-manjaro's handling of window specific saturation settings is buggy

I've recently switched from xfwm4 to compiz, in order to enable advanced controls over color saturation of my display. I've ran into issues when trying to enable window-specific saturation configuration using the "Opacity, brightness and saturation" plugin.

Rules declared in the window-specific saturation settings only applied to windows that have been opened in the moment when the plugin was enabled. All windows opened after the plugin initialization did receive the default amount of saturation, not the one that was declared in window-specific settings. Only after disabling and reenabling the plugin were the window-specific rules applied again.

After installing compiz from AUR the issue disappeard.

PS. Here's inxi -Fx output for my machine

  Host: laptop Kernel: 4.19.88-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.2.0 Desktop: Xfce 4.14.1 Distro: Manjaro Linux 
  Type: Laptop System: SAMSUNG product: 900X3C/900X4C/900X4D v: 0.1 
  serial: <root required> 
  Mobo: SAMSUNG model: SAMSUNG_NP1234567890 v: FAB1 serial: <root required> 
  UEFI [Legacy]: Phoenix v: P02AAC date: 06/01/2012 
  ID-1: BAT1 charge: 32.6 Wh condition: 32.6/40.3 Wh (81%) 
  model: SAMSUNG Electronics status: Full 
  Topology: Dual Core model: Intel Core i5-3317U bits: 64 type: MT MCP 
  arch: Ivy Bridge rev: 9 L2 cache: 3072 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 13574 
  Speed: 798 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 798 2: 798 
  3: 798 4: 803 
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Samsung Co 
  driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.6 driver: intel unloaded: modesetting 
  resolution: 1600x900~60Hz 
  OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 19.2.7 
  direct render: Yes 
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  vendor: Samsung Co driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k4.19.88-1-MANJARO 
  Device-1: Intel Centrino Advanced-N 6235 driver: iwlwifi v: kernel 
  port: efa0 bus ID: 01:00.0 
  IF: wlp1s0 state: up mac: c4:85:08:60:af:31 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Samsung Co driver: r8168 v: 8.047.05-NAPI port: 2000 
  bus ID: 02:00.0 
  IF: enp2s0 state: down mac: e8:03:9a:dc:02:28 
  Local Storage: total: 223.57 GiB used: 133.83 GiB (59.9%) 
  ID-1: /dev/sda vendor: Kingston model: SMS200S3240G size: 223.57 GiB 
  ID-1: / size: 218.57 GiB used: 133.69 GiB (61.2%) fs: ext4 dev: /dev/dm-0 
  ID-2: /boot size: 487.9 MiB used: 141.8 MiB (29.1%) fs: ext4 
  dev: /dev/sda1 
  System Temperatures: cpu: 53.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
  Processes: 200 Uptime: 16m Memory: 3.56 GiB used: 1.82 GiB (51.2%) 
  Init: systemd Compilers: gcc: 9.2.0 Shell: zsh v: 5.7.1 inxi: 3.0.37

Which exact compiz package from AUR did work for you? Version 8.x or 9.x?

9.x ( to be exact)

That's weird. You can export the settings into a text file from CCSM in both versions (AUR and Manjaro repos) and compare them to find the source of the problem.

In Manjaro repo is 0.9.13 but AUR is 0.9.14

I think a rebuild is required.

You can put in a request in the thread - Manjaro packages needing rebuild.

compiz-manjaro really is a PITA, only misses out very few protobuf updates when it comes to breaking. :smiley: But afaik this time this is not the problem since Compiz wouldn't even have started if it is built against an old protobuf version.

That is also what I remember - generally compiz is ...

In my experience Compiz runs rock stable - besides of the regular breakages due to protobuf updates where Compiz hasn't been rebuilt. Sorry to say, though the Manjaro team does an outstanding job and updates go through very smoothly usually, Compiz seems to be treated like an orphan...

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by