Bug 152955 - Pasting into a diagram causes beachball hang on MacBook
Summary: Pasting into a diagram causes beachball hang on MacBook
Status: RESOLVED DUPLICATE of bug 148435
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.3.2 release
Hardware: ARM macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-10 06:41 UTC by Ken Shirriff
Modified: 2023-01-16 18:55 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Crash report after force-quit (2.93 MB, text/plain)
2023-01-10 06:42 UTC, Ken Shirriff
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Shirriff 2023-01-10 06:41:28 UTC
Description:
If I screenshot from a spreadsheet and paste into a drawing, LibreOffice hangs with a beachball until I force-quit.


Steps to Reproduce:
1. Edit a spreadsheet
2. Screenshot part of it with shift-control-command-4 and drag
3. Go to a drawing and paste with command-V.

Actual Results:
Image of the screenshot should be pasted.

Expected Results:
Hang


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
This has happened a dozen times for me. It appears to be resolved if I give LibreOffice access to the full file system.

I.e. workaround:
go to System Settings->Privacy&Security
Click on Full Disk Access
Click on +
In the chooser window, click Applications/LibreOffice.app and Open

Version information:
Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Ken Shirriff 2023-01-10 06:42:15 UTC
Created attachment 184551 [details]
Crash report after force-quit

This is one of the crash reports after I force-quit LibreOffice.
Comment 2 Telesto 2023-01-16 18:55:05 UTC
This should be fixed with LibreOffice 7.4.4 based on the crash reporter information attached

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