Bug 166174 - LibreOffice 25.2.2.2 doesn't start
Summary: LibreOffice 25.2.2.2 doesn't start
Status: RESOLVED DUPLICATE of bug 164788
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.2.2.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-14 07:40 UTC by duffy55
Modified: 2025-04-19 00:19 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 duffy55 2025-04-14 07:40:49 UTC
Description:
I executed the update to the version in summary, the program doesn't start, I removed the program and installed the version 24.8.6.2 that is working.
I am using Windows 10 19045.5337

Actual Results:
Now is working with LibreOffice 24.8.6.2

Expected Results:
/*


Reproducible: Always


User Profile Reset: No

Additional Info:
*/
Comment 1 Mike Kaganski 2025-04-14 08:12:36 UTC
(In reply to duffy55 from comment #0)
> I executed the update to the version in summary

Please don't try to skip info by referring to another place ("in summary" instead of "25.2.2.2") - it doesn't even save bytes or keystrokes, and avoids ambiguity (the summary / metadata may be changed eventually, to better reflect the issue - and what then?).
Comment 2 V Stuart Foote 2025-04-17 18:53:00 UTC
Please identify your GPU and drivers on your Windows 10 system, steps listed in see also bug166122 (against Win11 systems having similar issues with the 25.2 release builds).

https://bugs.documentfoundation.org/show_bug.cgi?id=166122#c22
Comment 3 duffy55 2025-04-18 16:23:39 UTC
GPU NVidia GeoForce 610M, actual driver 388.57
Comment 4 V Stuart Foote 2025-04-18 17:32:39 UTC
Win10 with old nVidia GeForce GT 610M, non-Vulkan capable. So skia path issues.

*** This bug has been marked as a duplicate of bug 166235 ***
Comment 5 V Stuart Foote 2025-04-19 00:18:33 UTC

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