Bug 168048 - Copy cells from Calc and paste into external application
Summary: Copy cells from Calc and paste into external application
Status: RESOLVED DUPLICATE of bug 167075
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.8.0.4 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-21 19:25 UTC by Eliane Domingos de Sousa
Modified: 2025-08-21 20:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Gimp application screen after pasting the cell copied from Calc (25.06 KB, image/png)
2025-08-21 19:29 UTC, Eliane Domingos de Sousa 		Details
Simulation of the problem (3.60 MB, video/mp4)
2025-08-21 19:45 UTC, Eliane Domingos de Sousa 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eliane Domingos de Sousa 2025-08-21 19:25:34 UTC 
Description:
When pasting the cell copied from Calc into the Gimp or Whatsapp application, a blank screen appears.
Until release 25.2, this step was done normally and pasted the copied information into the desktop area of these applications, exactly as it was copied.

Steps to Reproduce:
1.copy cells from a spreadsheet
2.open an application such as Gimp
3.and paste what you copied

Actual Results:
white screen with dotted border

Expected Results:
the content that was copied


Reproducible: Always


User Profile Reset: No

Additional Info:
No more information
Comment 1 Eliane Domingos de Sousa 2025-08-21 19:29:05 UTC 
Created attachment 202441 [details]
Gimp application screen after pasting the cell copied from Calc
Comment 2 Eliane Domingos de Sousa 2025-08-21 19:45:59 UTC 
Created attachment 202442 [details]
Simulation of the problem
Comment 3 Xisco Faulí 2025-08-21 20:01:44 UTC 
Thanks for reporting this issue.
This is a duplicated of bug 167075

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