Bug 140181

Summary: Open File Dialog does not appear
Product: LibreOffice Reporter: Jens <frodo.hobbit>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: evgenijaf82
Priority: medium    
Version: 7.1.0.3 release   
Hardware: x86 (IA32)   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Jens 2021-02-05 10:03:50 UTC 
LibreOffice is installed out of the box for the first time on an iMac Pro - power should be sufficient. Start LibreOffice. A GUI appears. Press Open File.
Expectation: A Open File Dialog should appear.
What actually happens: A colorful ball comes up, spins for some time and disappears. Nothing else happens. 
Press Open File again - same behaviour.
Comment 1 Evgenija Chumachenko 2021-07-29 11:48:44 UTC 
no repro in
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 67f2a99229101757af4f40118f4d3c83ba38648b
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: en-US (ru_RU); UI: en-US
Calc: threaded
Comment 2 Anton F 2021-07-29 15:48:49 UTC 
Not reproduced.

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: cd2b5168e8ef1cb6e721bc5220421464ed723096
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: ru-RU (ru_RU.UTF-8); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-07-21_14:56:23
Calc: threaded
Comment 3 Denys Prokhorov 2021-08-03 15:25:00 UTC 
no repro

Additional Info:
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 246f24ebc8227345f13784d9e2f055d813f3d24f
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: ru-RU (ru_UA.UTF-8); UI: en-US
Calc: threaded

Version: 7.1.5.2 / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: ru-RU (ru_UA.UTF-8); UI: en-US
Calc: threaded
Comment 4 eisa01 2022-02-05 14:45:56 UTC 
This sounds like a duplicate of bug 128233

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