Bug 392825 - Slow startup: "org.kde.plasmaquick: Applet "Clipboard" loaded after 170640 msec", Crash
Summary: Slow startup: "org.kde.plasmaquick: Applet "Clipboard" loaded after 170640 ms...
Status: RESOLVED FIXED
Alias: None
Product: klipper
Classification: Unmaintained
Component: plasma-widget (show other bugs)
Version: 5.12.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-07 11:16 UTC by Gregor Mi
Modified: 2021-03-10 18:05 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
plasmashell output (16.02 KB, text/plain)
2018-04-07 11:16 UTC, Gregor Mi
Details
This is with klipper hanging. (16.96 KB, text/plain)
2018-04-26 10:09 UTC, denixx baykin
Details
This is after I've cleaned klipper history. (14.07 KB, text/plain)
2018-04-26 10:10 UTC, denixx baykin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2018-04-07 11:16:56 UTC
Created attachment 111884 [details]
plasmashell output

I upgraded openSUSE Tumbleweed to Plasma 5.12.4 and I noticed the following:

After login the desktop and panel hangs and it takes a few minutes before they become usable.

I started plasmashell from a console and saw the following:

org.kde.plasmaquick: Delayed preload of  "Clipboard" after 4.4 seconds
org.kde.plasmaquick: Applet "Clipboard" loaded after 170640 msec

(The complete shell output is attached) Between those two lines there was a pause from about 3 minutes. After that Plasma continued to load.

Click on the Clipboard Contents applet makes Plasma crash.
Comment 1 Kai Uwe Broulik 2018-04-09 15:11:04 UTC
Can you get a gdb backtrace of it crashing, please?
Comment 2 Gregor Mi 2018-04-19 14:55:17 UTC
(In reply to Kai Uwe Broulik from comment #1)
> Can you get a gdb backtrace of it crashing, please?

I did not do this before. When I have figured out how to do it, I can provide it.
Comment 3 denixx baykin 2018-04-26 10:07:43 UTC
Seems if something heavy is in klipper, it hangs!
Last time I've worked with 100k rows table in LibreOffice.
plasmashell hanged, and even reboot won't help.
Situation changed after I removed /home/denixx/.local/share/klipper/ with all it's content.
Maybe there should be timeout of klipper loading, and if it can't load in some reasonable time - clean the history and reload it.
Comment 4 denixx baykin 2018-04-26 10:09:34 UTC
Created attachment 112252 [details]
This is with klipper hanging.

Used this instruction twice:
https://forum.kde.org/viewtopic.php?f=289&t=125034#p329742
Comment 5 denixx baykin 2018-04-26 10:10:15 UTC
Created attachment 112253 [details]
This is after I've cleaned klipper history.
Comment 6 denixx baykin 2018-04-26 10:13:20 UTC
One small correction: for me it isn't crashing, it just hangs UI.
Even if I try to do
kbuildsycoca5 && kquitapp5 plasmashell && kstart5 plasmashell
it will do nothing as plasmashell hangs and even can't exit.
But it is terminatable (normal termination, NOT with KILL) from system monitor.
After that if I run
kstart5 plasmashell
it hangs again.
Comment 7 denixx baykin 2018-04-26 10:15:36 UTC
$ uname -a
Linux denixxwork 4.16.3-1-ARCH #1 SMP PREEMPT Thu Apr 19 09:17:56 UTC 2018 x86_64 GNU/Linux

KDE Plasma: 5.12.4
KDE Framework version: 5.45.0
Qt: 5.10.1
Comment 8 denixx baykin 2018-04-27 10:11:24 UTC
Also, I can try to repeat work I've done with LibreOffice in attempt to triage content which breaks klipper.
Please, inform me, if it's needed to be done.
Comment 9 Christoph Roick 2018-04-29 11:39:33 UTC
This is probably related to [1]. Wiping the ~/.local/share/klipper folder resolves this for me as well. For me the plasmashell freezes when using Mathematica which creates large chunks (>10MB) of clipboard content.

[1] https://askubuntu.com/q/1024071
Comment 10 Nate Graham 2021-03-10 03:23:31 UTC
If this is still reproducible for you, can you tell me if you have a huge amount of stuff in the clipboard?
Comment 11 denixx baykin 2021-03-10 08:09:03 UTC
Hi, Nate.
Haven't seen this issue for too long, so it might be resolved already.
Comment 12 denixx baykin 2021-03-10 08:30:19 UTC
To be honest I use a customized config of Klipper.
Usually, I disable its eagerness. I disable some things like grab mouse selections and maybe some other stuff to make Klipper more lightweight and react only on my direct actions to copy-paste something.
Comment 13 Nate Graham 2021-03-10 14:31:56 UTC
Let's call it fixed. :)
Comment 14 Gregor Mi 2021-03-10 18:05:04 UTC
I encountered no problems with klipper for a long time. So for me it is fixed.

Don't no how klipper handles large chunks of clipboard data nowadays (see https://bugs.kde.org/show_bug.cgi?id=392825#c9)