Bug 105871

Please include also Xorg version. This seems very much like bug #103699.

My apologies for not including X.org version. The x.org version is 1.19.5
name of display:    :0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    11905000
X.Org version: 1.19.5

Seeing exactly the same on kubuntu 17.10 with the padoka ppa (bringing mesa 18.0.0) and the kde ppa on a haswell laptop.

Many gray items now are much darker.

Disabling compositing, all colors go back to normal. The issue seems to be realated to translucent elements.

In my case:

KDE Frameworks 5.44.0
Qt 5.9.1 (built against 5.9.1)
KDE Plasma 5.12.4
kernel 4.13.0-38-generic (ubuntu)
Xorg 1.19.5
libdrm 2.4.91 + git
mesa Version: 18.0.0
intel driver 2.99.917 + git @ 2017/03/09 (used with DRI3 and sna)

Integrated Graphics Chipset: Intel(R) Iris(TM) Pro Graphics 5200 that is haswell mobile Crystal Well Integrated Graphics Controller (rev 08).

Pretty sure this is the same bug, I'm not sure if the Xorg patch is in place since 32bit visual seems to be srgb capable (see 's'), it shouldn't be like this with the patch:

--- 8< ---
0x086 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 24  8  0  0  0  0  0 0 None

I see the patch in "server-1.19-branch" but it looks like there has not been a release which would include the fix :/ Release 1.19.7 will have it.

I do not know if the following information is relevant, but in doubt I am providing it:

I was the original reporter of https://bugs.freedesktop.org/show_bug.cgi?id=103699. The issue with the firefox menus has been fixed for a while on my system and even with mesa 18, I get the firefox menus fine.

It is unclear to me if the issue is with something that should not happen with the opengl visuals or with something that happens but is then mismanaged by kwin. To assure that the kwin developers are aware of the issue, I have cross posted on their bug repo as https://bugs.kde.org/show_bug.cgi?id=392716

A quick question... the patch being mentioned is related to the part of xorg that usually gets packaged as xserver-xorg-core, right? Not to the individual video drivers such as those packaged in xserver-xorg-video-intel, correct?

I am asking because ubuntu has various PPAs providing updated graphic stacks, but all of them appear to be currently shipping the updated video-xxx packages but no updated core package for xorg.

Hi,
Same bug here after upgrading today to mesa 18.0 on both Broadwell and Skylake mobile.

mesa 18.0.0 from padoka PPA stable
X.Org version: 1.19.5
KDE Neon
KDE Frameworks 5.44.0
Qt 5.10
KDE Plasma 5.12.4
kernel 4.13.0-38-generic (ubuntu) (tested also with 4.15 and 4.16)
intel driver 2.99.917 + git

For info, no problem on ivybridge and ironlake mobile with the same config.

(In reply to sergio.callegari from comment #9)
> A quick question... the patch being mentioned is related to the part of xorg
> that usually gets packaged as xserver-xorg-core, right? Not to the
> individual video drivers such as those packaged in xserver-xorg-video-intel,
> correct?
> 
> I am asking because ubuntu has various PPAs providing updated graphic
> stacks, but all of them appear to be currently shipping the updated
> video-xxx packages but no updated core package for xorg.

Yes, it would be the xore package. The change is not in individual driver but the server glx code.

Tapani Pälli's suggestion that the bug was the same as in the other case was 100% correct!

Having been notified about this thread, Paulo Dias has very quickly put up on his padoka stable ppa an xserver-xorg-core package for ubuntu artful including the patch mentioned in this thread. With this the issue is gone.

As an alternate/complement solution to the patched xserver-xorg-core on the Padoka ppa, for those using kde plasma, there is now also a patch to kwin to fix the visuals selection.

https://phabricator.kde.org/D11758

Unfortunately, for shortage of time, I am unable to test that too right now. However, I wonder if someone reading here may be able to do so.

(In reply to sergio.callegari from comment #13)
> As an alternate/complement solution to the patched xserver-xorg-core on the
> Padoka ppa, for those using kde plasma, there is now also a patch to kwin to
> fix the visuals selection.
> 
> https://phabricator.kde.org/D11758
> 
> Unfortunately, for shortage of time, I am unable to test that too right now.
> However, I wonder if someone reading here may be able to do so.

It seems that patch tackles separate issue related to 10bpc visuals, these are currently disabled for Intel (since caused issues) and enabled for gallium drivers.

The issue does appear to be fixed with the xserver update in the padoka ppa

(In reply to sergio.callegari from comment #13)
> As an alternate/complement solution to the patched xserver-xorg-core on the
> Padoka ppa, for those using kde plasma, there is now also a patch to kwin to
> fix the visuals selection.
> 
> https://phabricator.kde.org/D11758
> 
> Unfortunately, for shortage of time, I am unable to test that too right now.
> However, I wonder if someone reading here may be able to do so.

I tried that patch, without succes,he doesn't fix this bug.

Resolving as a duplicate, thanks for testing.

*** This bug has been marked as a duplicate of bug 103699 ***

(In reply to Tasev from comment #16)
> (In reply to sergio.callegari from comment #13)
> > As an alternate/complement solution to the patched xserver-xorg-core on the
> > Padoka ppa, for those using kde plasma, there is now also a patch to kwin to
> > fix the visuals selection.
> > 
> > https://phabricator.kde.org/D11758
> 
> I tried that patch, without succes,he doesn't fix this bug.

This is understandable, because I only fixed kwin_wayland session with that, and I only have amd hardware to test with.

If you can point me to which config attribute kwin should/should not be using to avoid this, we can at least try to fix kwin_x11 too.

(In reply to Alexey Min from comment #18)
> (In reply to Tasev from comment #16)
> > (In reply to sergio.callegari from comment #13)
> > > As an alternate/complement solution to the patched xserver-xorg-core on the
> > > Padoka ppa, for those using kde plasma, there is now also a patch to kwin to
> > > fix the visuals selection.
> > > 
> > > https://phabricator.kde.org/D11758
> > 
> > I tried that patch, without succes,he doesn't fix this bug.
> 
> This is understandable, because I only fixed kwin_wayland session with that,
> and I only have amd hardware to test with.
> 
> If you can point me to which config attribute kwin should/should not be
> using to avoid this, we can at least try to fix kwin_x11 too.

I'am just a average user, i can test a patch but i cannot help more
than that.

(In reply to Alexey Min from comment #18)
> (In reply to Tasev from comment #16)
> > (In reply to sergio.callegari from comment #13)
> > > As an alternate/complement solution to the patched xserver-xorg-core on the
> > > Padoka ppa, for those using kde plasma, there is now also a patch to kwin to
> > > fix the visuals selection.
> > > 
> > > https://phabricator.kde.org/D11758
> > 
> > I tried that patch, without succes,he doesn't fix this bug.
> 
> This is understandable, because I only fixed kwin_wayland session with that,
> and I only have amd hardware to test with.
> 
> If you can point me to which config attribute kwin should/should not be
> using to avoid this, we can at least try to fix kwin_x11 too.

Problem is that kwin_x11 cannot easily avoid this because there is only one 32bit visual exposed and without the patch mentioned in bug #103699 it always has sRGB capability which makes things go bad. It is likely that somewhere we are missing a sRGB->linear conversion in that case. With that patch for Xorg I wanted to restore previous behaviour back.

(In reply to Tapani Pälli from comment #20)
> Problem is that kwin_x11 cannot easily avoid this because there is only one
> 32bit visual exposed and without the patch mentioned in bug #103699 it
> always has sRGB capability which makes things go bad. It is likely that
> somewhere we are missing a sRGB->linear conversion in that case. With that
> patch for Xorg I wanted to restore previous behaviour back.

Thank you for clarification, that's what I suspected after reading various bug reports and mail list archives today. Well, hope it will be fixed then :)