Bug Report Xcomposite colours all wrong

TyMiles2012

New Member
That worked for me too! I've always had driconfig installed, I didn't think about tinkering with that! lol Definitely a MESA issue. I just added the tags to my own drirc file and rebooted. It didn't fix it at first, but then the colors suddenly fixed themselves while previewing. Went into driconfig and toggled the retoggled that same setting in the gui and now it works with every reboot. Thanks!

That's awesome because now I can just keep the Gallium Nine MESA drivers. For me, it was either no OBS, or no Final Fantasy XIV. lol
 

shaolin

Member
Ok. Thanks for your time to get to the bottom of it. I wouldn't have found it.

Can some of you guys go to our discord server an we follow up it there? I don't have the hardware to proper test this and will need your help to test a possible fix.
 

Luke A. Guest

New Member
That worked for me too! I've always had driconfig installed, I didn't think about tinkering with that! lol Definitely a MESA issue. I just added the tags to my own drirc file and rebooted. It didn't fix it at first, but then the colors suddenly fixed themselves while previewing. Went into driconfig and toggled the retoggled that same setting in the gui and now it works with every reboot. Thanks!

I didn't even need a reboot, just whacked it in and it worked, thanks.
 

shaolin

Member
As stated by the Mesa developer on the thread linked here, Its a new behavior in mesa that triggered an OBS issue. Mesa now supports more fbconfigs.

To run the test repo you should remove any work arounds from the dirrc file.
 
Last edited:
just a heads up, there is already a bug report on this. it's a problem with obs:
https://obsproject.com/mantis/view.php?id=1157
https://bugs.freedesktop.org/show_bug.cgi?id=104597

the problem is that mesa now supports and exposes 10bpc color, and obs isn't able to handle it correctly. this is why xcomposite window colors show up all funky, and why the /etc/dri code fixes it. (the /etc/dri entry disables 10bpc rendering for obs)

as mentioned above, this is the fix for it:
https://bugs.freedesktop.org/show_bug.cgi?id=104597#c12

at least until obs is able to handle it correctly
 
Top