Bug 165978 - MacOS: unresponsiveness behavior when cmd+q is pressed
Summary: MacOS: unresponsiveness behavior when cmd+q is pressed
Status: RESOLVED DUPLICATE of bug 165277
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.1.2 release
Hardware: ARM macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-31 03:39 UTC by Jim Zhou
Modified: 2025-04-01 02:44 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Zhou 2025-03-31 03:39:35 UTC
Description:
When pressing cmd+q with unsaved changes, LibreOffice will pop up a dialogue to ask you whether save the document or not. 

This popup window seems to be unresponsive, nothing happens fter I click the `don't save` `cancel` and `save` button. Also the red close button on the top left corner does not close the popup window.

Also it is notable that the CPU utilization of LibreOffice is abnormally high when this behavior happens, with significant energy usage.

This behavior happens on me every time I press cmd+q, and sometimes the popup window is just blank. When this happens, what I can only do is to force quit LibreOffice and recover my Document later, which may be unsafe.

This behavior also happens in safe mode.

My LibreOffice version is 25.2.1.2
My MacOS version is 15.3-beta and my machine is 13-inch MacBook Air with M3 chip.


Steps to Reproduce:
1. start LibreOffice with a document or anything you can save.
2. modifie the document, but don't save it 
3. press cmd+q

Actual Results:
A popup window appears and asked me whether to save the document or not. It is draggable, but it is unresponsive, unclickable and unclosable.

Expected Results:
A popup window appears and asked me whether to save the document or not. And it functions normally and closes normally.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
LibreOffice version information:
Version: 25.2.1.2 (AARCH64) / LibreOffice Community
Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49
CPU threads: 8; OS: macOS 15.3; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Patrick (volunteer) 2025-03-31 12:59:26 UTC
This sounds very similar to tdf#165277 which was fixed in LibreOffice 25.2.2. Do you still see this bug after upgrading to 25.2.2?
Comment 2 Jim Zhou 2025-04-01 02:44:59 UTC
(In reply to Patrick (volunteer) from comment #1)
> This sounds very similar to tdf#165277 which was fixed in LibreOffice
> 25.2.2. Do you still see this bug after upgrading to 25.2.2?

Thanks for replying. The problem is fixed after updating the newer version!

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