Thanks for the report.

Can you run gdb on plasmashell when it is taking over your cpu?

Copy-paste this to terminal

gdb --pid=`pidof plasmashell`

if you see something like "ptrace: Operation not permitted", rerun the same with sudo.

When it is done loading, type "thread apply all bt" and then get the full backtrace and post here.

Thanks :)

(In reply to Martin Klapetek from comment #1)
> Thanks for the report.
> 
> Can you run gdb on plasmashell when it is taking over your cpu?
> 
> Copy-paste this to terminal
> 
> gdb --pid=`pidof plasmashell`
> 
> if you see something like "ptrace: Operation not permitted", rerun the same
> with sudo.
> 
> When it is done loading, type "thread apply all bt" and then get the full
> backtrace and post here.
> 
> Thanks :)

http://pastebin.com/RUaKnhkE


But i think it isn't useful (Is it ok if after the first command the output was like:
 "Reading symbols from /usr/lib/qt/plugins/plasma/dataengine/plasma_engine_clipboard.so...(no debugging symbols found)...done." ?)

I am experiencing a similar occurrence using plasma-workspace-5.1.2-2 under Manjaro Linux (arch derivative). I will try to follow with more info a la gdb when this next happens.

Best regards.

No updates for over a year, assuming fixed.

If you can still reproduce with Plasma 5.5.3, please follow
steps from comment #1, make sure you have debug symbols
installed and please attach or paste the backtrace here
directly.

Thanks

This no longer occurs for me with latest versions.

Best regards.