Bug 166235 - LibreOffice_25.2.2_Win_x86-64 don't work after installation
Summary: LibreOffice_25.2.2_Win_x86-64 don't work after installation
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: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-17 19:52 UTC by Valentin Filchev
Modified: 2025-04-19 00:20 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
This is folder insaid in %appdata% >Roaming >LibreOffice (787.92 KB, application/vnd.rar)
2025-04-17 20:28 UTC, Valentin Filchev
Details
CPUZ, GPUZ, System Information first page (in Bulgarian) (61.08 KB, application/x-zip-compressed)
2025-04-17 22:41 UTC, Valentin Filchev
Details
System Drivers (8.57 KB, application/x-zip-compressed)
2025-04-17 22:53 UTC, Valentin Filchev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Filchev 2025-04-17 19:52:59 UTC
Description:
LibreOffice_25.2.2_Win_x86-64 don't work after installation
When I try to repair installator crash 
When I uninstall and install again was warning about DeepL - translator which I use and again don't work=

Steps to Reproduce:
1.Instal DeepL 
2.Install  LibreOffice_25.2.2_Win_x86-64 
3.Try to use application 
4.Try to repair application

Actual Results:
I back to LibreOffice_24.8.6_Win_x86-64

Expected Results:
New version work at all


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: bg
Module: StartModule
[Information guessed from browser]
OS: Windows (Home)
OS is 64bit: yes

Version: 24.8.6.2 (X86_64) / LibreOffice Community
Build ID: 6d98ba145e9a8a39fc57bcc76981d1fb1316c60c
CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win
Locale: bg-BG (bg_BG); UI: bg-BG
Calc: CL threaded

But this is Information for older working version=
Comment 1 Valentin Filchev 2025-04-17 20:28:21 UTC
Created attachment 200378 [details]
This is folder insaid in %appdata% >Roaming >LibreOffice
Comment 2 V Stuart Foote 2025-04-17 21:27:38 UTC
You might try translate.google.com, it looks to support bg-BG Bulgarian without needing the DeepL

Otherwise, issue seems like it could be a dupe of bug 166122 and issues with the build system update from skia m116 to skia m130 

Could you please post details about your system's CPU, GPU and the graphics drivers.  See how to find the details https://bugs.documentfoundation.org/show_bug.cgi?id=166122#c22

Also, if the issue is the same LibreOffice startup testing of Vulkan rendering using skia calls--you can bypass that rendering testing and get a working install of 25.2.2

From the Safe mode start panel as in attachment.

But if you are unable to get into the GUI to get to SafeMode you can --simply add/adjust renderings stanzas directly in per user Profile registrymodifications.xcu:

<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="ForceSkiaRaster" oor:op="fuse"><value>true</value></prop></item>
<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseSkia" oor:op="fuse"><value>true</value></prop></item>

They won't be there with a new default profile (and Skia Vulkan enabled by default), but you can add them both. And the ForceSkiaRaster will toggle between Skia Vulkan and Skia software based raster framing with edits outside of LibreOffice.

If you set them both to 'False', skia rendering libs will not be used and system will instead use fallback GDI+ rendering that your graphics processor or the CPU can support.

On major version upgrades, e.g. 24.8 to 25.2, the profile will be replaced. So you may need to make a copy of the old profile .xcu modified with the two stanzas--ForceSkiaRaster and UseSkia.

Then after install of 25.2.2 replace the default registrymodifications.xcu with the copy from 24.8

Again, the main NEEDINFO is for you to post the details about your graphics processor (discrete card or one integrated with the CPU) and what driver is used.

=-Google translate gloss-=

Може да опиташ translate.google.com, изглежда поддържа bg-BG български, без да има нужда от DeepL

В противен случай изглежда, че проблемът може да е дублиране на грешка 166122 и проблеми с актуализацията на системата за компилация от skia m116 до skia m130

Бихте ли могли да публикувате подробности за процесора, графичния процесор и графичните драйвери на вашата система. Вижте как да намерите подробностите https://bugs.documentfoundation.org/show_bug.cgi?id=166122#c22

Освен това, ако проблемът е същото стартиращо тестване на LibreOffice на рендиране на Vulkan с помощта на skia повиквания – можете да заобиколите това тестване на рендиране и да получите работеща инсталация на 25.2.2

От панела за стартиране на безопасен режим, както в прикачения файл.

Но ако не можете да влезете в графичния потребителски интерфейс, за да стигнете до SafeMode, можете просто да добавите/настроите строфи за изобразяване директно в потребителски профил registrymodifications.xcu:

<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="ForceSkiaRaster" oor:op="fuse"><value>true</value></prop></item>
<item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseSkia" oor:op="fuse"><value>true</value></prop></item>

Те няма да бъдат там с нов профил по подразбиране (и Skia Vulkan активиран по подразбиране), но можете да ги добавите и двамата. И ForceSkiaRaster ще превключва между Skia Vulkan и Skia софтуерно базирано растерно рамкиране с редакции извън LibreOffice.

Ако зададете и двете на „False“, библиотеките за рендиране на skia няма да се използват и вместо това системата ще използва резервно GDI+ рендиране, което вашият графичен процесор или CPU може да поддържа.

При надстройки на големи версии, напр. 24.8 до 25.2 профилът ще бъде сменен. Така че може да се наложи да направите копие на стария профил .xcu, модифициран с двете строфи - ForceSkiaRaster и UseSkia.

След това след инсталиране на 25.2.2 заменете по подразбиране registrymodifications.xcu с копието от 24.8

Отново основната NEEDINFO е да публикувате подробности за вашия графичен процесор (дискретна карта или интегрирана с процесора) и какъв драйвер се използва.
Comment 3 Valentin Filchev 2025-04-17 22:41:46 UTC
Created attachment 200379 [details]
CPUZ, GPUZ, System Information first page (in Bulgarian)
Comment 4 Valentin Filchev 2025-04-17 22:53:59 UTC
Created attachment 200380 [details]
System Drivers
Comment 5 Valentin Filchev 2025-04-17 23:02:28 UTC
I am just simple user and I prefer to stay in one old version because i don't understand all most noting from your explanation.
Comment 6 V Stuart Foote 2025-04-18 14:05:18 UTC
So looking at the attached reports: for a GeForce GT 610 in use, the listed nVidia 388.13 GeForce driver was released in 2017. The last driver update for the Geforce GT 610 was 391.35 build from March 2018, 7 years old.

Also, from the GeForce 600 series, the GeForce GT 610 did not support Vulkan. Nor does the GT 620, nor the GT 625 while other GeForce 600 series cards support only at the Vulkan 1.2 SC release API.

A driver update to the 391.35 release is unlikely to improve things.

Believe the nVidia GeForce GT 610 GPU device (0x0915) should be denylisted by LO. 

Although if the denylist is being parsed correctly against the nVidia drivers < 457.36.0 for the 388.13 driver should already be deny listed against the and *force skia lib raster framing* with no further testing. Other 600 series devices--630, 635, 640 are Vulkan capable and run Vulkan driver > 472.12.0 or 473.47.0 through the 1.2.175 release Vulkan API.

Suspect the skia testing methods LO has used for vendor, device and driver values may have been changed by skia between the m116 and m130 skia release builds--skia libs as used in LO 24.8 and 25.2 respective.

LO is somehow now choking on the skia/Vulkan test rather than honoring the denylist as it had done for this system through the 24.8 builds.

=-From OPs attachments-=

Display adapter 0 (primary)	
	ID			0x1060419
	Name			NVIDIA GeForce GT 610
	Board Manufacturer	NVIDIA Corporation
	Revision		A1
	Codename		GF119
	Core family		0xD9 (GF119)
	Cores			48
	ROP Units		4
	Technology		40 nm
	Memory type		DDR3
	Memory vendor		Hynix
	Memory size		1024 MB
	Memory bus width	64 bits
	Current Link Width	x8
	Current Link Speed	2.5 GT/s
	PCI device		bus 2 (0x2), device 0 (0x0), function 0 (0x0)
		Vendor ID	0x10DE (0x10DE)
		Model ID	0x104A (0x0915)
		Revision ID	0xA1
	Root device		bus 0 (0x0), device 3 (0x3), function 1 (0x1)
	Performance Level	Current
		Core clock	270.0 MHz
		Shader clock	540.0 MHz
		Memory clock	405.0 MHz
	Driver version		23.21.13.8813
	WDDM Model		2.3

Win32_VideoController		AdapterRAM = 0x40000000 (1073741824)
Win32_VideoController		DriverVersion = 23.21.13.8813
Win32_VideoController		DriverDate = 10/27/2017
Comment 7 V Stuart Foote 2025-04-18 17:32:39 UTC
*** Bug 166174 has been marked as a duplicate of this bug. ***
Comment 8 V Stuart Foote 2025-04-19 00:18:07 UTC

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