Bug#900259: mate-tweak: Colors in marco-compton are weird
Package: mate-tweak
Version: 18.04.16-1
Severity: normal
Dear Maintainer,
Had been experiencing some flakiness in my video display and then the
mounse and keyboard locked up. I sshed in from another machine and tried
'sudo init 6', but that lock up the terminal session. Finally I resorted
to a hard reset.
On reboot, the lightdm login screen was fine, but when I logged in all
the mate components (top bar, mate terminal etc) were being dimplayed
in weird colours (reds and yellows, it looked like an indexed 256 colour
pallete).
After some considerable debugging I found that switching from the
marco-compton window manager back to just marco fixed everything. To make
sure this is what it was, I switched back to the compton version which
again had weird colours and then back to marco which fixed the issue.
IMHO, marco-compton should either be fixed or deprecated.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mate-tweak depends on:
ii dconf-cli 0.28.0-2
ii gir1.2-gtk-3.0 3.22.29-3
ii gir1.2-notify-0.7 0.7.7-3
ii mate-panel 1.20.1-3
ii mesa-utils 8.4.0-1
ii python3 3.6.5-3
ii python3-gi 3.28.2-1
ii python3-pkg-resources 39.1.0-1
ii python3-psutil 5.4.2-1
ii python3-setproctitle 1.1.10-1+b1
ii x11-xserver-utils 7.7+8
Versions of packages mate-tweak recommends:
ii compton 0.1~beta2+20150922-1
ii mate-indicator-applet 1.20.0-1
Versions of packages mate-tweak suggests:
pn indicator-application <none>
pn indicator-messages <none>
pn indicator-power <none>
pn indicator-session <none>
pn indicator-sounds <none>
-- no debconf information
Reply to: