https://bugs.kde.org/show_bug.cgi?id=418403
slartibar...@gmail.com changed:
What|Removed |Added
Ever confirmed|1 |0
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=418403
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #15 from slartibar...@gmail.com ---
good news... the psr (panel self refresh) disabling fixes the problem!!!
Questions:
- what changes in kwin/plasma since 5.16.x caused this problem? I mean,
according to the solutions i found on the net,
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #14 from slartibar...@gmail.com ---
after looking at similar reports of laptop screen problems i found the advice,
to add
i915.enable_psr=0
to the kernel-commandline.
This seems very promising, i continue testing...
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #13 from slartibar...@gmail.com ---
nah, blinking is still there.
I'm out of ideas right now, any help?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #12 from slartibar...@gmail.com ---
I'm currently testing with disabled TLP, this seems promising
Anyone else with this blink-problem had tlp active?
Is tlp necessary at all any more? (esp. since fedora31 and following did
improve energy
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #11 from slartibar...@gmail.com ---
just one more thing (i know, this quote is 'stolen' :-)
Something that looks quite similar to my 'blink' event is for example attaching
a second monitor to the displayPort (miniDP). There you also get a
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #10 from slartibar...@gmail.com ---
dmesg is attached as well, starting yesterday.
Nothing really interesting in there regarding the blink event
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #9 from slartibar...@gmail.com ---
Created attachment 128850
--> https://bugs.kde.org/attachment.cgi?id=128850=edit
dmesg
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #8 from slartibar...@gmail.com ---
Created attachment 128849
--> https://bugs.kde.org/attachment.cgi?id=128849=edit
log with blink event
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #7 from slartibar...@gmail.com ---
i recently captured on 'blink' event (see attached file)
In comparison to the other file i have written (unsuccessfully), the only thing
standing apart is this line:
org.kde.kactivities.lib.core: Killing
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #6 from Vlad Zahorodnii ---
My guess is that a graphics reset occurs from time to time. It would be really
helpful if you run `env QT_LOGGING_RULES="*.debug=true" kwin_x11 --replace` and
post the output after the screen turned black. You
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #5 from slartibar...@gmail.com ---
after a longer testing... sadly, the kwin-lowlatency doesn't help. Laptop
screen still 'blinks'
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #4 from slartibar...@gmail.com ---
i'm currently testing with KWin-lowlatency, up to now it seems to have stopped
the irregular blinking.
If this holds true (i continue testing), then maybe we have a bug to report to
kwin/composer?
--
You
https://bugs.kde.org/show_bug.cgi?id=418403
--- Comment #3 from slartibar...@gmail.com ---
at least i'm not allone or hallucinating...
Still happens on 5.18.4
I already did a fresh install of fc31 on the laptop, assuming it was caused by
all those updates coming since fc27.
But the problem
https://bugs.kde.org/show_bug.cgi?id=418403
Nate Graham changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Target Milestone|1.0
16 matches
Mail list logo
