Summary: | most plasma desktop events are delayed (toggling the app launcher, actions applet) | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Matej Starc <matej.starc> |
Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | antkumachev, bugseforuns, dev.bacteriostat, nate |
Priority: | NOR | Flags: | antkumachev:
Wayland+
antkumachev: X11- |
Version: | 5.25.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Manjaro | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=454379 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matej Starc
2022-08-16 11:39:54 UTC
This is the video link (I couldn't upload it as a file, because it is too big). https://cloud.aljaxus.eu/index.php/s/3wEsCoj887AGXGX For some reason, it stopped happening. I didn't even reboot. I just used it normally. (In reply to Matej Starc from comment #2) > For some reason, it stopped happening. I didn't even reboot. I just used it > normally. Nvm. It started lagging again. Now, when I start a program it takes some time to show the window. same symptoms reported as bug 454379 Is there anything using excessive CPU time? (In reply to Nate Graham from comment #5) > Is there anything using excessive CPU time? CPU time or CPU usage ? If you are talking about CPU usage, then there wasn't anything suspicious. Weird. Are you getting anything like this in the journal?
> plasmashell[1756]: QWaylandDataOffer: timeout reading from pipe
> plasmashell[1756]: QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection
(In reply to Bacteria from comment #8) > Are you getting anything like this in the journal? > > > plasmashell[1756]: QWaylandDataOffer: timeout reading from pipe > > plasmashell[1756]: QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection I can't reproduce it. To be honest, I don't know how it even happened (how to trigger it). I will make sure to make a log if I encounter it again. I had the same issue, solved it by re-installing inxi package |