You are not logged in.
I found an old thread from 2016 referencing this situation. https://bbs.archlinux.org/viewtopic.php?id=221169
The solution back then was to roll back llvm. The solution for me was to rollback mesa to 17.3.7. My llvm-libs is just the standard 6.0.0-4. I'm not using any git/svn/aur packages for llvm or mesa.
Is this just another mismatch with llvm and mesa, or am I missing something.
(XFCE, and using radeonsi with mesa)
Offline
Same situation.
The link you provided was also what came up in my searches.
I'm quite new so I'm wary of which packages are fine to rollback, but thought it might be the compositor. It was quite amusing that maybe I was right since I stopped Compton and the red/pink thing went away. However, I really would prefer having the compositor.
ETA: I also believe it's related to mesa since compton wasn't even part of the packages upgraded. It was just a thought of mine to disable compton.
Last edited by ace_ang (2018-04-06 10:25:31)
Offline
Same here. If I launch the compton then there is no error:
allow_rgb10_configs=false compton --backend glx
Offline
https://bugs.freedesktop.org/show_bug.cgi?id=104597
Basically mesa now exposes rgb10 colors and not everything handles that correctly.
No need to downgrade anything , run compton like toga did .
OR use /etc/driconf to set allow_rgb10_configs to false .
Last edited by Lone_Wolf (2018-04-06 11:59:18)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
allow_rgb10_configs=false compton --backend glx
run compton like toga did
Works well, thanks!
Offline