Description: After a sudden reset while saving a doc in libreoffice writer, libreoffice does not starts any more, hugs on open screen (either libreoffice or librewriter) Try to fix proble with soffice.com -env:UserInstallation=file:///c:/my-test-profile but failed reporting: vkEnumeratePhysicalDevices failed: -3 Steps to Reproduce: 1. Reset while saving a doc 2. 3. Actual Results: OfficeLibre doew not start, it hungs on start screen Expected Results: Open then LibreOffice Reproducible: Always User Profile Reset: Yes Additional Info: For Windows: soffice.com -env:UserInstallation=file:///c:/my-test-profile
The message is about Vulkan. I see you are launching it with a fresh profile. I wonder, if you had disabled Vulkan earlier and the fresh profile is making it enabled again? Does the same happen, if you launch in Safe Mode from the Windows start menu entry?
That's it!!! Tnks Buovjaga I started LibreOfficein SafeMode, I disabled the Vulcan and evething is fine now.
Great! It might be interesting, if you attached to this report the file C:\Users\User\AppData\Roaming\LibreOffice\4\cache\skia.log (where User is your user name). You might also experiment with a newer LibreOffice version to see, if Vulkan behaves better. An easy way is to download Win-x86_64@tb77-TDF unstable build from https://dev-builds.libreoffice.org/daily/master/current.html because it installs separately and will not mess with your stable profile.
Created attachment 179003 [details] C:\Users\User\AppData\Roaming\LibreOffice\4\cache\skia.log
(In reply to Simos Dalkiriadis from comment #4) > Created attachment 179003 [details] > C:\Users\User\AppData\Roaming\LibreOffice\4\cache\skia.log Ok, I guess the log was overwritten - it shows render method as raster instead of Vulkan.
This may help too: https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29 (first thing is to check if you got last driver version).
Dear Simos Dalkiriadis, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Simos Dalkiriadis, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp