https://bugs.kde.org/show_bug.cgi?id=405691
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #13 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=405691
Tiar changed:
What|Removed |Added
CC||tamtamy.tym...@gmail.com
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #11 from M ---
As an update, I changed to a PRIME config for GPU switching on this same
hardware over a year ago, as that is now the much more officially supported and
less hacky way to switch between GPUs. I set Krita to start with prime-ru
https://bugs.kde.org/show_bug.cgi?id=405691
Boudewijn Rempt changed:
What|Removed |Added
Keywords||triaged
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #10 from Boudewijn Rempt ---
I haven't managed to setup a test system, so I haven't been able to investigate
it. It's also not the most urgent bug we've currently got open, since there are
workarounds, I'm sorry.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #9 from M ---
Good reminder, optirun doesn't bypass the issue anymore for me either since an
update several months ago.
My workaround is to start a separate X session with the nvidia-xrun script, in
case I need the Nvidia GPU.
--
You are r
https://bugs.kde.org/show_bug.cgi?id=405691
Mihail Shabunin changed:
What|Removed |Added
Version|nightly build (please |4.2.3
|specify the git hash
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #7 from Boudewijn Rempt ---
Okay, then it's likely not a Qt 5.12 bug, but a regression due the HDR related
refactoring. Thanks again for testing -- I tried to install bumblebee on my
laptop, but it doesn't seem to work at all.
--
You are r
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #6 from M ---
No, the stable appimage seems to be unaffected (4.1.8-9347112). It also doesn't
produce those messages in the terminal.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #5 from Boudewijn Rempt ---
Hm... Another question: if you use the nightly stable build appimage (which
uses Qt 5.12), do you see the same problem:
https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/ ?
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #4 from Boudewijn Rempt ---
Thanks for testing. I'm beginning to suspect that this is Yet Another Qt 5.12.
Bug... I've got a laptop with both nvidia and intel gpu myself, but I haven't
got anything setup to use the nvidia gpu... I'll probabl
https://bugs.kde.org/show_bug.cgi?id=405691
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #2 from M ---
Yes, unfortunately it still is (git f3858d1), with optirun as well as
primusrun. The flickers only become apparent once a document is opened or
created, and only when there is any movement on screen. No issues with 4.1.8.
Anoth
https://bugs.kde.org/show_bug.cgi?id=405691
Boudewijn Rempt changed:
What|Removed |Added
CC||b...@valdyas.org
Status|REPORTED
15 matches
Mail list logo
