Bug 159951 - Crashes immediately at startup of every component on a brand new Win11 notebook
Summary: Crashes immediately at startup of every component on a brand new Win11 notebook
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.6.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-29 00:10 UTC by Matthias Rauch
Modified: 2024-03-06 03:14 UTC (History)
1 user (show)

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 Matthias Rauch 2024-02-29 00:10:49 UTC
Description:
After a first fresh of version 7.6.5 install on a new Asus Zenbook with Win11 Home on startup the Libre Office Banner shortly shows up than disappears. 

Deinstalling, removing the user context and installing the older version 7.4.6.2, which runs fine on all other of my computers (Win10 Pro, Win 7 Pro) behaves the same way. The event log for this attempt is

Name der fehlerhaften Anwendung: soffice.bin, Version: 7.4.6.2, Zeitstempel: 0x6402696f
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.22621.2506, Zeitstempel: 0x097c794c
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000007f61e
ID des fehlerhaften Prozesses: 0x0x2988
Startzeit der fehlerhaften Anwendung: 0x0x1DA6A86355BB293
Pfad der fehlerhaften Anwendung: C:\Program Files\LibreOffice\program\soffice.bin
Pfad des fehlerhaften Moduls: C:\Windows\System32\ucrtbase.dll
Berichtskennung: af391707-31ca-4f7c-8f5c-eb654b3839bd
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

The portable version 7.5.7 (MultilingualStandard) seems not to be affected.

I wonder why a 64bit version checks fpr dlls in System32 anyway.

Steps to Reproduce:
1. Just start soffice.exe or scalc.exe or whatever component
2.
3.

Actual Results:
Splash screen shows up shortly then disappears 

Expected Results:
Porgram starts up and is useable


Reproducible: Always


User Profile Reset: Yes

Additional Info:
I understand that the module reported to be in error, ucrtbase.dll, is not provided by Libreoffice. There are some, even rather old, reports regarding Libreoffice problems in connection with  this dll, but the version 10.0.22621.2506 seems to be almost the newest available, and there seems to be no indocation of a corrupted file. 

Anyway, if a dll is vital for the overall functionality of Libreoffice, the sotware package should provide its own version.
Comment 1 Stéphane Guillou (stragu) 2024-02-29 05:02:44 UTC
Thank you for the report.

I don't see that with:

Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

- Which locale do you use?
- Does it also happen with LO 24.2?
- If it does, could you please see if the issue is still reproducible with a daily build from https://dev-builds.libreoffice.org/daily/master/current.html ?
Comment 2 Matthias Rauch 2024-03-01 15:34:16 UTC
Hi,

you wrote:

> I don't see that with: ...

no surprise to me, on all the other machines there is no problem with whatever version

> - Which locale do you use?

de_DE

> - Does it also happen with LO 24.2?

yes, see here:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> 
  <EventID>1000</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2024-03-01T13:48:27.9780902Z" /> 
  <EventRecordID>1294</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="7740" ThreadID="8100" /> 
  <Channel>Application</Channel> 
  <Computer>Zenbook</Computer> 
  <Security UserID="S-1-5-21-2448148023-4083034520-2558083710-1001" /> 
  </System>
- <EventData>
  <Data Name="AppName">soffice.bin</Data> 
  <Data Name="AppVersion">24.2.1.2</Data> 
  <Data Name="AppTimeStamp">65dba9ce</Data> 
  <Data Name="ModuleName">ucrtbase.dll</Data> 
  <Data Name="ModuleVersion">10.0.22621.2506</Data> 
  <Data Name="ModuleTimeStamp">097c794c</Data> 
  <Data Name="ExceptionCode">c0000409</Data> 
  <Data Name="FaultingOffset">000000000007f61e</Data> 
  <Data Name="ProcessId">0x4ce0</Data> 
  <Data Name="ProcessCreationTime">0x1da6bdf20245ab2</Data> 
  <Data Name="AppPath">C:\Program Files\LibreOffice\program\soffice.bin</Data> 
  <Data Name="ModulePath">C:\Windows\System32\ucrtbase.dll</Data> 
  <Data Name="IntegratorReportId">1b47643e-d368-47f3-8be5-521f8f7681ab</Data> 
  <Data Name="PackageFullName" /> 
  <Data Name="PackageRelativeAppId" /> 
  </EventData>
  </Event>

> - If it does, could you please see if the issue is still reproducible
> with a daily build from ...

I don't think this would make a difference, and as I said, the portable version works fine on that machine (an Asus Zenbook btw). Either this .dll is damaged or too new for Libreoffice. 

In both cases I would have expected, if an OS provided file is as vital for the functionality of Libreoffice as this .dll seems to be, that the installation process checks for compatibility in advance.
Comment 3 QA Administrators 2024-03-02 03:15:58 UTC Comment hidden (obsolete)
Comment 4 Stéphane Guillou (stragu) 2024-03-04 11:32:31 UTC
My version of ucrtbase.dll is also 10.0.22621.2506

If you are able to, please collect and share a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Comment 5 Matthias Rauch 2024-03-05 20:30:57 UTC
Sorry, the laptop is currently travelling, will be back in about 2 weeks, I will then try to collect that backtrace.
Comment 6 QA Administrators 2024-03-06 03:14:35 UTC Comment hidden (obsolete)