Bug 150026

Summary: 64-bit ChromeOS Cannot Start LibreOffice 7.3.4 or Versions Thereafter
Product: LibreOffice Reporter: Rob Elsman <robelsman0453>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: normal    
Priority: medium    
Version: 7.3.5.2 release   
Hardware: x86-64 (AMD64)   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description Rob Elsman 2022-07-17 18:09:05 UTC 
Description:
While the LibreOffice 7.3.3.2 64-bit Debian version works fine on my Chromebook, beginning with 7.3.4 and continuing with 7.4.0.1 BETA,the program shuts down immediately after the splash screen is very briefly displayed.  No error message is displayed.  The installation process works fine, and icons are created in the Linux Apps folder, just I would expect.

I tried to install and start the program in a completely new and clean Linux container.  The installation was normal, but the problem persisted, so it seems clear that I do not have a corrupted user profile.

Steps to Reproduce:
1.Install
2.Click on any LibreOffice icon on the Chromebook launcher.
3.

Actual Results:
Splash screen very briefly appears, but program immediately crashes.

Expected Results:
Depending on what component icon is selected, I would have expected the component to open with its first screen.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
ChromeOS 103.0.5060.114
Chrome Linux x86-64, version 5.10.114-16024
Comment 1 Rob Elsman 2022-07-23 18:41:25 UTC 
The same error occurs with version 7.3.5.2.
Comment 2 Rob Elsman 2022-08-19 15:06:49 UTC 
19 August 2022
The same crash persists in version 7.4.0.3.
Comment 3 bernard.roux@gmail.com 2022-08-25 07:08:56 UTC 
 Hello,
Same Problem on my Chromebook (Version 104.0.5112.105 (Build officiel) (64 bits)). I Tried also with 7.4.0
Only 7.2.7.2 works
Regards
Comment 4 Rob Elsman 2022-11-07 17:42:08 UTC 
This bug persists in version 7.4.2.3-3.
Comment 5 Rob Elsman 2023-01-18 15:21:20 UTC 
This bug persists in version 7.4.4.2.
Comment 6 Rob Elsman 2023-02-07 18:02:03 UTC 
This bug persists in version 7.5.0.3.