https://bugs.kde.org/show_bug.cgi?id=306352
Albert changed:
What|Removed |Added
CC||albert.casasgranados@gmail.
|
https://bugs.kde.org/show_bug.cgi?id=306352
a.v.po...@gmail.com changed:
What|Removed |Added
CC||a.v.po...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=306352
Christian Heller changed:
What|Removed |Added
CC||christian.hel...@cybop.org
--- Comment #27
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #26 from Timo Gurr ---
While certainly not a fix by any means I want to share a workaround because I
found myself ever so often not noticing that the cpu spike again kicked in
until I wondered why my machine is loud again and revving up the
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #25 from Robert Nurnberg ---
A simple way to trigger the bug for me is to run:
xmodmap ~/.Xmodmap_manual
I had to rename .Xmodmap to .Xmodmap_manual to avoid the freezing of the
machine upon every login. Now I only invoke xmodmap manually
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #24 from Robin Bankhead ---
I've found a way to trigger the cpu thrash on-demand (when in VNC session). I
noticed one of my custom shortcuts was triggering it every time, but on
investigation it is not the shortcut but this command in the
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #23 from Robin Bankhead ---
Sorry, amendment to the above on further investigation.
The CPU spike is triggered by ANY keyboard input (e.g. typing a letter key,
which opens the quick-launcher, or CTRL on its own which has no UI effect).
--
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #22 from Robin Bankhead ---
Further data point: I just added a systemmonitor plasmoid to my panel to show
CPU usage, and interestingly after first opening my vnc session it actually did
not show any heavy activity.
It started maxing one
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #21 from Frédéric COIFFIER ---
Created attachment 153618
--> https://bugs.kde.org/attachment.cgi?id=153618=edit
perf FlameGraph of the PID with a correct behaviour (0% CPU)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #20 from Frédéric COIFFIER ---
Created attachment 153617
--> https://bugs.kde.org/attachment.cgi?id=153617=edit
perf FlameGraph of the PID
I added a perf FlameGraph of the process when it is stucked at 100% CPU. I
don't know if it could
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #19 from Frédéric COIFFIER ---
I can also confirm the problem with Gentoo and VNC remote X11 session (and I'm
using systemd).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #18 from Robin Bankhead ---
As mentioned above I'm on Gentoo, so no systemd involved here. And being in VNC
I don't see it being graphics stack related either, but that's probably a bit
above my pay-grade to say ;)
I'm not sure either
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #17 from Timo Gurr ---
(In reply to Robin Bankhead from comment #16)
> Just to update on my earlier, I haven't found a way of re-triggering the
> high CPU usage after killing and relaunching kglobalaccel5 at the start of
> my VNC session,
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #16 from Robin Bankhead ---
Just to update on my earlier, I haven't found a way of re-triggering the high
CPU usage after killing and relaunching kglobalaccel5 at the start of my VNC
session, and it has not recurred again during such a
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #15 from Robin Bankhead ---
FWIW, the issue as I outlined my experience of it is still occurring under
kde-frameworks/kglobalaccel-5.97.0, but for the first time I have also
encountered it recurring later in my VNC session. (It is possible
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #14 from Alex ---
Correction:
On first start kglobalaccel5 consumes 100% CPU. If killed and started again, it
will behave properly.
Before I had to kill it regularly. Now it seems I've killed it once and forgot
about it.
--
You are
https://bugs.kde.org/show_bug.cgi?id=306352
Alex changed:
What|Removed |Added
CC||fuant...@gmail.com
--- Comment #13 from Alex ---
I had
https://bugs.kde.org/show_bug.cgi?id=306352
Timo Gurr changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=306352
Frédéric COIFFIER changed:
What|Removed |Added
CC||frederic.coiff...@free.fr
--
You are
https://bugs.kde.org/show_bug.cgi?id=306352
Bo Ørsted Andresen changed:
What|Removed |Added
CC||z...@exherbo.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=306352
Timo Gurr changed:
What|Removed |Added
CC||timo.g...@gmail.com
--- Comment #11 from Timo Gurr
https://bugs.kde.org/show_bug.cgi?id=306352
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=306352
Boltzmann changed:
What|Removed |Added
CC||lizhe0...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=306352
Robert Nurnberg changed:
What|Removed |Added
CC||robert.nurnb...@gmx.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=306352
Nicholas changed:
What|Removed |Added
CC||nicho...@nshiell.com
--- Comment #9 from Nicholas
https://bugs.kde.org/show_bug.cgi?id=306352
Lukas Winkler changed:
What|Removed |Added
CC||k...@lw1.at
--- Comment #8 from Lukas Winkler
26 matches
Mail list logo
