https://bugs.kde.org/show_bug.cgi?id=406180
Martin Droessler changed:
What|Removed |Added
CC||m...@martindroessler.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #20 from Jeffery Patton ---
(In reply to Peter Eszlari from comment #18)
> (In reply to Pieter-Jan Briers from comment #17)
> > Could it be that the issue is exclusive to people using PRIME on laptops?
>
> My tests are based on a discrete
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #19 from Jeffery Patton ---
(In reply to Peter Eszlari from comment #16)
> (In reply to Jeffery Patton from comment #14)
> > (In reply to Peter Eszlari from comment #13)
> > > I cannot reproduce this:
> > >
> > > kwin 5.15.4
> > > Qt
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #18 from Peter Eszlari ---
(In reply to Pieter-Jan Briers from comment #17)
> Could it be that the issue is exclusive to people using PRIME on laptops?
My tests are based on a discrete graphics card (GTX 960).
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=406180
Jonathan Liu changed:
What|Removed |Added
CC||net...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #17 from Pieter-Jan Briers ---
Could it be that the issue is exclusive to people using PRIME on laptops? I
Noticed in the Reddit thread that all the people who had the issue were using
laptops (like me).
I could try to verify this by
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #16 from Peter Eszlari ---
(In reply to Jeffery Patton from comment #14)
> (In reply to Peter Eszlari from comment #13)
> > I cannot reproduce this:
> >
> > kwin 5.15.4
> > Qt 5.11.1
> > nvidia 390.116
>
> Could it be the Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #15 from Pieter-Jan Briers ---
Here's some of the info about my system. I marked all the individual config/log
dumps with +++ so you can ctrl+f around it easily.
https://pastebin.com/g2REWCc3
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #14 from Jeffery Patton ---
(In reply to Peter Eszlari from comment #13)
> I cannot reproduce this:
>
> kwin 5.15.4
> Qt 5.11.1
> nvidia 390.116
Could it be the Nvidia driver version as well?
I have 418.x, maybe if I went back to the
https://bugs.kde.org/show_bug.cgi?id=406180
Peter Eszlari changed:
What|Removed |Added
CC||peter.eszl...@gmail.com
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=406180
Honghao Li changed:
What|Removed |Added
CC||i...@rasphino.cn
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #12 from David Edmundson ---
This comment I think is important:
>I downgraded back to KWin 5.15.3 [..] and it seems like KWin 5.15.3 has the
>exact same behavior as KWin 5.15.4 when render loop is set to basic.
It implies that it's a
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #11 from David Edmundson ---
Maybe for stable. Especially 5.12 as that isn't out yet.
But I don't think it's a hugely widespread issue. We would have way more than a
handful of reports if it was.
Can I have the following:
- output of
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #10 from Vlad Zagorodniy ---
I suggest to revert 22a441e071515e9c630f3bdac743c678052f88be if this problem is
not fixed by 5.15.5 tar date.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406180
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #9 from Jeffery Patton ---
(In reply to Jeffery Patton from comment #8)
> I have this problem too. It happens every time when I do window snapping
> with my mouse. I tested Pieter-Jan Brier's step to reproduce this bug by
> using alt-tab,
https://bugs.kde.org/show_bug.cgi?id=406180
Jeffery Patton changed:
What|Removed |Added
CC||roundduckm...@gmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=406180
Rik Mills changed:
What|Removed |Added
CC||rikmi...@kubuntu.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=406180
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #7 from Pieter-Jan Briers ---
Oh I just noticed something else. I downgraded back to KWin 5.15.3 to try the
render loop basic thing on there, and it seems like KWin 5.15.3 has the exact
same behavior as KWin 5.15.4 when render loop is set
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #6 from Pieter-Jan Briers ---
Setting render loop to basic seemed to have helped slightly but it's still
unusable.
That said, this time if I hold down alt until it stops hanging on its own, KWin
seems to get a graphics reset which at the
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #5 from David Edmundson ---
If you go kcmshell5 qtquicksettings and set render loop to "basic" can you
confirm that the freeze goes away.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #4 from Pieter-Jan Briers ---
Sure: https://pastebin.com/ggLkGjT6
This is a build from master while I am writing this by the way
(1e2a0028c3151cb38f252baa78a5f22b8cd7c7e6)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=406180
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #2 from Pieter-Jan Briers ---
That commit is definitely it. I built KWin from source with and without said
commit reverted and it's definitely the cause of the regression.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=406180
--- Comment #1 from Vlad Zagorodniy ---
Hmm, could it be 22a441e071515e9c630f3bdac743c678052f88be?
--
You are receiving this mail because:
You are watching all bug changes.
26 matches
Mail list logo
