https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #36 from Fabian Vogt ---
Git commit 4982dfd5f5ec408a19de48a1ada98f91497db48d by Fabian Vogt.
Committed on 15/10/2019 at 14:07.
Pushed by fvogt into branch 'Plasma/5.17'.
glx: Don't use sRGB configs on llvmpipe with depth 16
Summary:
This
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #35 from David de Cos ---
Thanks, that worked. Although, lowering the noise strength to the minimum is
what did the trick, not blur strength.
I remember this setting did absolutely nothing before updating to 5.16.3, so I
had it at a random
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #34 from Michał Dybczak ---
I just updated to Plasma 5.16.3 on Manjaro Testing and I can confirm that the
issue is gone. Blurred, transparent areas look colorless again.
David de Cos, if what you are describing is about the blur effect, go
https://bugs.kde.org/show_bug.cgi?id=408594
David de Cos changed:
What|Removed |Added
CC||david.de...@ehu.eus
--- Comment #33 from David
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #32 from Fredrik Höglund ---
(In reply to Fabian Vogt from comment #31)
> (In reply to Fredrik Höglund from comment #30)
> > (In reply to Fabian Vogt from comment #27)
> > > > So I'm going to solve this by blacklisting sRGB configs on
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #31 from Fabian Vogt ---
(In reply to Fredrik Höglund from comment #30)
> (In reply to Fabian Vogt from comment #27)
> > > So I'm going to solve this by blacklisting sRGB configs on LLVMPipe
> > > instead.
> >
> > That sounds like a bit
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #30 from Fredrik Höglund ---
(In reply to Fabian Vogt from comment #27)
> > So I'm going to solve this by blacklisting sRGB configs on LLVMPipe instead.
>
> That sounds like a bit too much, everything except cirrus with 16bpp seems to
>
https://bugs.kde.org/show_bug.cgi?id=408594
Fredrik Höglund changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kwi
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #28 from Sawyer Bergeron ---
Since 5.16.3 is tomorrow, I'm guessing https://phabricator.kde.org/D22153 isn't
going to quite make it in?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #27 from Fabian Vogt ---
(In reply to Fredrik Höglund from comment #26)
> (In reply to Roman Gilg from comment #22)
> > The patch lead to a regression in cirrus (default video device of openQA)
> > and possibly needs to be reverted.
>
>
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #26 from Fredrik Höglund ---
(In reply to Roman Gilg from comment #22)
> The patch lead to a regression in cirrus (default video device of openQA)
> and possibly needs to be reverted.
Reverting this patch means having to disable gamma
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #25 from Fabian Vogt ---
(In reply to Fabian Vogt from comment #24)
> (In reply to Fabian Vogt from comment #23)
> > qt.qpa.screen: adding QXcbScreen(0x5630281c1250, name="VGA-1",
> > geometry=1024x768+0+0, availableGeometry=1024x732+0+0,
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #24 from Fabian Vogt ---
(In reply to Fabian Vogt from comment #23)
> kwin_platform_x11_standalone: Choosing GLXFBConfig 0x27e X visual 0x2d5
> depth 32 RGBA 8:8:8:8 ZS 0:0 sRGB: 1
visual x bf lv rg d st colorbuffer sr ax dp st
https://bugs.kde.org/show_bug.cgi?id=408594
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #23 from
https://bugs.kde.org/show_bug.cgi?id=408594
Roman Gilg changed:
What|Removed |Added
CC||subd...@gmail.com
--- Comment #22 from Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #21 from Fredrik Höglund ---
Git commit 3d384f3c90205f35fea445446903661c7c046514 by Fredrik Höglund.
Committed on 29/06/2019 at 11:09.
Pushed by fredrik into branch 'Plasma/5.16'.
glx: Prefer an sRGB capable fbconfig
Prefer an sRGB
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #20 from Tsu Jan ---
> Is it scheduled for 5.16 series I hope?
That's my question too -- I'm just a kwin user. I only know that the patch
isn't applied to kwin 5.16.2.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #19 from Michał Dybczak ---
Ah, didn't know. Thanks for the info. I'll wait for the fix then. Is it
scheduled for 5.16 series I hope?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #18 from Tsu Jan ---
> It's really annoying because
It's already fixed under X11. You could apply the patch or wait for it to come
to your distro.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #17 from Michał Dybczak ---
Created attachment 121192
--> https://bugs.kde.org/attachment.cgi?id=121192=edit
solid-black-instead-of-full-blur-transparency-100%
Looks like some wallpapers could even change the 100% blur to 100% solid
https://bugs.kde.org/show_bug.cgi?id=408594
Vlad Zagorodniy changed:
What|Removed |Added
CC||kailash.sudha...@gmail.com
--- Comment #16
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #15 from Tsu Jan ---
OK, tested and saw the bug was present under Wayland too -- the patch had no
effect there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #14 from Tsu Jan ---
Here, the patch fixed the issue. Thanks a lot!
I haven't tested KWin 5.16.1 under Wayland though.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #13 from Michail Vourlakos ---
(In reply to Fredrik Höglund from comment #12)
> (In reply to Michail Vourlakos from comment #9)
> > (In reply to Fredrik Höglund from comment #5)
> > > There is a way to check that at runtime by calling
> > >
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #12 from Fredrik Höglund ---
(In reply to Michail Vourlakos from comment #9)
> (In reply to Fredrik Höglund from comment #5)
> > There is a way to check that at runtime by calling
> > glGetFramebufferAttachmentParameteriv() with pname set
https://bugs.kde.org/show_bug.cgi?id=408594
Vlad Zagorodniy changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #10 from Michał Dybczak ---
Indeed it's the intel thing. When I switched to nvidia this dark saturation is
gone.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
Michail Vourlakos changed:
What|Removed |Added
CC||mvourla...@gmail.com
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #8 from Vlad Zagorodniy ---
@Fredrik The default framebuffer has GL_LINEAR color encodimng.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #7 from Nate Graham ---
*** Bug 408773 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=408594
Vlad Zagorodniy changed:
What|Removed |Added
CC||michal.dybc...@gmail.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #5 from Fredrik Höglund ---
There is a way to check that at runtime by calling
glGetFramebufferAttachmentParameteriv() with pname set to
GL_FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=408594
Vlad Zagorodniy changed:
What|Removed |Added
CC||fred...@kde.org
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #3 from Sawyer Bergeron ---
(In reply to Vlad Zagorodniy from comment #1)
> Seems like an intel bug. Can you post output of glxinfo?
Gladly, anything else?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
Sawyer Bergeron changed:
What|Removed |Added
CC||sawyerberge...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #1 from Vlad Zagorodniy ---
Seems like an intel bug. Can you post output of glxinfo?
--
You are receiving this mail because:
You are watching all bug changes.
37 matches
Mail list logo
