Bug 364180 - Invoking fast qdbus org.kde.klipper /klipper setClipboardContents "$line" leads to Panel freeze
Summary: Invoking fast qdbus org.kde.klipper /klipper setClipboardContents "$line" lea...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard widget & pop-up (show other bugs)
Version: 5.15.3
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: 1.0
Assignee: Martin Flöser
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-10 12:03 UTC by mhruscak
Modified: 2023-08-11 03:20 UTC (History)
2 users (show)

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


Attachments
gdb plasma-shell backtrace (22.15 KB, text/plain)
2016-06-10 13:50 UTC, mhruscak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mhruscak 2016-06-10 12:03:35 UTC
Loading many lines of text using 'qdbus org.kde.klipper /klipper setClipboardContents "$line"' causes freezing of Panel for 10sec-1min
Freezing not occuring if sleep(higher than 0.3) is used between commands.
This behaviour is observable also when klipper is configured to "synchronize contents of the clippboard and selection" and user is selecting different text to fast e.g. 5 fast clicks on some text in Konsole

Reproducible: Always

Steps to Reproduce:
1. run command 
for a in `seq 10`; do qdbus org.kde.klipper /klipper setClipboardContents "$a";done
2. 
3.

Actual Results:  
Panel freezes

Expected Results:  
Panel should not be influenced
Comment 1 Martin Flöser 2016-06-10 12:48:22 UTC
is it freezing or busy looping? In case of freeze, could you gdb into plasmashell and get a backtrace of all threads?
Comment 2 mhruscak 2016-06-10 13:50:17 UTC
Created attachment 99441 [details]
gdb plasma-shell backtrace
Comment 3 mhruscak 2016-06-10 13:58:23 UTC
Maybe it is busy-looping, because longer "list" with 30 lines takes longer time than only 5 lines list.
Comment 4 Martin Flöser 2016-06-13 05:43:10 UTC
> QXcbClipboard::waitForClipboardEvent

that sounds a lot like blocking
Comment 5 Noah Davis 2023-08-11 03:20:56 UTC
This bug is from Plasma 5.6.4, not Plasma 5.15.3. It seems that this problem is fixed because I could not reproduce it using the command the original reporter provided.