Bug 510560

Summary: Clipboard, copy-paste in Libreoffice calc as image, not actual cell-content
Product: [Plasma] plasmashell Reporter: kde.org <kde.org>
Component: Clipboard widget & pop-upAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, qydwhotmail
Priority: NOR    
Version First Reported In: 6.4.5   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screencast showing problem

Description kde.org@human.li 2025-10-13 11:12:50 UTC
Created attachment 185733 [details]
screencast showing problem

copy-pasting of a cell in Libreoffice does paste an image instead of the actual content of the cell

SUMMARY

First, I looked at Libreoffice: They have a bug-report about this: https://ask.libreoffice.org/t/calc-keeps-copying-and-pasting-cells-as-images/119164

However, it is attributed to a faulty-clipboard-manager. 

So I tried disabling it in KDE: Right-Click on Tray > configure system tray > Entries > Clipboard, set to "disabled"

Now copy-paste works as expected in Libreoffice

STEPS TO REPRODUCE
See Libreoffice bug report above
1. copy a single cell (ctrl-c)
2. paste it over several cells (ctrl-v)

OBSERVED RESULT
often, not always an image is pasted instead of the content of the cell. The content of the clipboard is indeed considered an image, as I can paste it into gimp and see an empty cell. 

EXPECTED RESULT
cell content in LO calc should be pasted. No image should be in the clipboard. 

SOFTWARE/OS VERSIONS
Operating System: KDE neon User Edition
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-33-generic (64-bit)
Graphics Platform: Wayland
Processors: 14 × Intel® Core™ Ultra 7 155U
Memory: 34 GB of RAM (33.1 GB usable)
Graphics Processor 1: Intel® Graphics
Graphics Processor 2: llvmpipe

Using wayland


ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-10-13 19:20:08 UTC
They're right! It'll be fixed in Plasma 6.4.6

*** This bug has been marked as a duplicate of bug 505209 ***