https://bugs.documentfoundation.org/show_bug.cgi?id=170906

            Bug ID: 170906
           Summary: LibreOffice Writer Appears to Freeze Uing File > Save
                    as
           Product: LibreOffice
           Version: 26.2.0.3 release
          Hardware: x86 (IA32)
                OS: macOS (All)
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
After upgrading from LibreOffice 25.x to 26.2.0.3, Writer's File > Save as
option makes Writer appear to freeze.  This made it seem that Writer's File >
Save as option wouldn't work.

Steps to Reproduce:
1. Upgrade from LibreOffice 25.x to 26.2.0.3.
2. Open LibreOffice and Create a new Writer Document.
3. Select File > Save as


Actual Results:
Writer froze with a beach ball and I had to use command+tab to move away from
Writer, as it wouldn't respond at all.  Given that it froze, I force quit
Writer.  After doing so I realized there was a prompt about whether I should
allow Writer access to Microsoft OneDrive hidden behind the frozen window. 
After responding to that, I created a new Writer document, and File > Save as
then worked properly.  

I ran this test because someone else reported in a Mac users group that the
File > Save as option didn't work in LibreOffice Writer.  So I'm not the only
person who encountered this and it's being spread.  I did report the solution
in that Mac Users group and that i would report it.

Expected Results:
I don't know if it's possible, but that Microsoft OneDrive prompt should appear
in front of of the Writer window, not behind it.  


Reproducible: Didn't try


User Profile Reset: No

Additional Info:
Version: 26.2.0.3 (X86_64)
Build ID: afbbd0df0edb6d40b450b0337ac646b0913a760c
CPU threads: 16; OS: macOS 26.3; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to