https://bugs.kde.org/show_bug.cgi?id=384660
David Edmundson changed:
What|Removed |Added
Status|RESOLVED|REPORTED
CC|
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #23 from zccrs ---
(In reply to Antonio Orefice from comment #20)
> @zccrs
> Is your patch submitted to upstream or maybe rejected?
I'm sorry, because I am not sure my patch is right, to be honest I don't know
what is the root cause, so I
https://bugs.kde.org/show_bug.cgi?id=384660
David Edmundson changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #21 from triffid.hun...@gmail.com ---
After more extensive experimentation, this certainly makes it a lot more
difficult to trigger the underlying bug (my previously reliable trigger methods
failed at first) but doesn't prevent it
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #20 from Antonio Orefice ---
@zccrs
Is your patch submitted to upstream or maybe rejected?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384660
triffid.hun...@gmail.com changed:
What|Removed |Added
CC||triffid.hun...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #18 from zccrs ---
(In reply to Antonio Orefice from comment #17)
> Thanks zccrs, i hope your patch will work and will be accepted upstream, it
> doesn't seem too invasive.
> Finger crossed, anyone?
Thanks, I will upload this patch to
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #17 from Antonio Orefice ---
Thanks zccrs, i hope your patch will work and will be accepted upstream, it
doesn't seem too invasive.
Finger crossed, anyone?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384660
zccrs changed:
What|Removed |Added
CC||zc...@live.com
--- Comment #16 from zccrs ---
I also
https://bugs.kde.org/show_bug.cgi?id=384660
blaueshawaiih...@gmx.de changed:
What|Removed |Added
CC||blaueshawaiih...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #15 from Martin Flöser ---
I guess you simply run out of memory due to the lot of animations from Oxygen.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #14 from Antonio Orefice ---
Unfortunately, after several hours of use, the problem appeared even without
glow; this time it happened using intel driver (in the past i tried nvidia
proprietary on a gtx1050ti and
https://bugs.kde.org/show_bug.cgi?id=384660
Hugo Pereira Da Costa changed:
What|Removed |Added
Product|Oxygen |kwin
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #10 from Antonio Orefice ---
I found a way to reproduce the issue; made a script for that (attached:
flicker.sh).
For it to work on my system, i've found that the following conditions have to
be met:
Use Oxygen
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #9 from Antonio Orefice ---
Created attachment 107869
--> https://bugs.kde.org/attachment.cgi?id=107869=edit
flicker.sh
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #8 from Antonio Orefice ---
I'll probably update you by monday, as i can test only in business days.
I plan to keep using breeze another day, and, if no flicker occurred, i'll
change it to oxygen without restarting the
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #7 from Martin Flöser ---
and switching to Oxygen creates this problem?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #6 from Antonio Orefice ---
I again, in the process of isolating the problem, i reated a new user and was
unable to reproduce my issue, so i tried to replicate one by one the "standard"
plasma setup on the main user.
I
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #5 from Antonio Orefice ---
Hi again Martin, i just saw the following:
https://bugs.kde.org/show_bug.cgi?id=361154
In particular here:
> Opening new Windows causes alternate monitor (dual-monitor setup) to flicker
>
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #4 from Antonio Orefice ---
Yes, the hardware is the same, but memory is good according to memtest, and the
system is stable, i played resource intensive games without observing any
issue.
Is there something i can do to
https://bugs.kde.org/show_bug.cgi?id=384660
--- Comment #3 from Martin Flöser ---
Is the hardware the same except for the graphics card? If yes I strongly
suggest to do a test of the hardware.
What you experience is not normal. It might be driver specific, but that we see
https://bugs.kde.org/show_bug.cgi?id=384660
Martin Flöser changed:
What|Removed |Added
Summary|Parto of the screen(s) |Part of the screen(s)
22 matches
Mail list logo