https://bugs.kde.org/show_bug.cgi?id=449163
Méven Car <meve...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |meve...@gmail.com
--- Comment #37 from Méven Car <meve...@gmail.com> ---
(In reply to David Chmelik from comment #35)
> It's NOT originally a Wayland bug but has been happening since KDE Plasma 4
> started, and into Plasma 5. The panel used to stay frozen for as long as a
> half-hour or hour until I maybe killed plasmashell or KDE. Sometimes it
> worked to restart/fork plasmashell in a screen session in a xterm. Now it
> might still sort of work except your minimized system tray programs won't
> reappear there, only on taskbar (and some in background, have to kill them)
> which will no longer be in the order you moved programs to.
> This bug for the last 10 or 12+ years is why I initially switched
> back to KDE3.5 for a few major versions of Slackware until KDE3.5 stopped
> working, then tried to switch to TDE KDE3.5 fork and simpler (less
> power-hungry, even though I don't use many effects) desktop environments and
> still will try to switch. I still love KDE and will report bugs, but I
> haven't seen the panel freeze bug ever stop. Sometimes at the same time,
> some/most/all other things stop responding too.
> People suggested turn off indexing, which I did, which didn't
> improve situation. If I leave KDE on for days the panel is probably bound
> to stop responding.
There are a lot of other possible causes for a process to freeze like Plasma.
For this bug, we addressed one of the causes we could precisely identify.
> One thing that did seem to exacerbate it is if I start
> 10 or 15+ GUI programs immediately on starting KDE, which sometimes
> permanently slowed it down. If I start one program then another after a
> minute or two or after disc activity died down (though my OS is on SSD,
> /home is on HDD) and continue in that fashion, usually it doesn't slow down.
> The thing is, even if I start 15+ programs at once, it might just be 10% CPU
> resources of my 32 threads is even being used, so the parallel processing
> might need to improve (unless that situation is only a HDD access problem.)
You are describing a Xorg bug and contention due its protocol design. (If you
run a recent distro did you compare with wayland?)
Or at least a different issue.
We need bugs reports to be focused on a single issue or they become
unmanageable.
Feel free to open new bugs or find those that correspond more closely to your
symptoms.
Maybe one of the duplicates was wrongfully marked to duplicate this one, then
comment on the duplicated one.
--
You are receiving this mail because:
You are watching all bug changes.
