Description: We have 3 Windows 11 systems with Version 7.5.3.2. At the first start after starting the system the small LibreOffice start window stops when the progress bar reaches about 30 %. After closing the program in the task manager, LibreOffice starts normally at the second try. I have reset my user settings and disabled hardware acceleration without success. The program also crashes much more often in normal use than in previous versions. Steps to Reproduce: 1.Start LibreOffice 2.Start window hangs 3. Actual Results: No response of the program Expected Results: Normal start Reproducible: Always User Profile Reset: Yes Additional Info: Normal start
Any better with LO 7.5.4 ?
Response sent in private: "no, unfortunately not." (Please next time respond on the bugtracker by using this link https://bugs.documentfoundation.org/show_bug.cgi?id=156085# so the information is shared.) Thank you for the feedback, I don't have more questions here.
Do you see a crash reporter dialog when restarting LO? If so, please share the crash report link. Please also share the detailed version info copied from Help > About LibreOffice. If you don't get a crash report, it would be helpful to get a backtrace for that crash. If you have the time, please follow these steps: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
Created attachment 188170 [details] WinDbg backtrace and version info Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded
[Automated Action] NeedInfo-To-Unconfirmed
The windbg trace shows nothing. Once you did "g" to indicate "go", you must try to reproduce a crash. Once it crashes, you must type !analyze -v to retrieve an useful stacktrace.
Created attachment 188205 [details] WinDbg backtrace
Argh, the stack only contains this: 00000000`00000000 00000000`00000000 soffice.bin!unknown_function+0x0 which can't help I suppose. I must recognize I'm stuck here.
Please also provide the Skia log: https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_(_Skia_) And test if the issue is Skia-related by using "Force Skia software rendering" in Tools ▸ Options ▸ LibreOffice ▸ View Thank you!
Created attachment 188206 [details] skia.log skia.log inncludes only 2 lines disabling/enabling of "Force Skia software rendering" does not solve the problem.
Right, thank you. Moving on to other ideas: - please check that all updates for drivers and OS are installed - try completely uninstalling LO, including removing the user profile, and reinstalling Still no luck? Are the three devices exactly the same hardware?
Resetting profile and reinstallation we have tried without success. We have 3 different computers, two of them Win 11, one Win 10.
jan, what hardware do you use? CPU and GPU? Could you try to start LibreOffice in Safe mode using main menu item for it?
My colleagues and I have been using LibreOffice for many years. Unfortunately, we have been bothered by a bug for several years now, which occurs every time we start LibreOffice. With each new version that comes out, we hope that the issue will be resolved, but so far, that hasn't happened. Regarding the bug: When starting LibreOffice, the loading progress bar runs normally until it reaches about 1/3 of the total progress, and then the program freezes. Nothing further happens. If you click or wait in this situation, LibreOffice displays the message "LibreOffice is not responding." If you start a new instance after ending the frozen task, everything works normally. The frustration has now reached a point where I decided to investigate the cause. I downloaded Microsoft's Process Monitor (Procmon.exe) and examined what happens at the moment of startup. Since many things are happening, I gradually disabled processes in the Task Manager. Suddenly, LibreOffice could be started without any issues, without freezing. The cause of this problem is our email program "The Bat!". When I don't have The Bat! running, LibreOffice also works flawlessly. Now, I can even set LibreOffice to start in the Autostart before the email client, and everything functions perfectly. I'm afraid I can't provide more specific details about the root cause. To do that, you would probably need to contact the developers of "The Bat!!". When I look at the log files of Process Monitor with my limited knowledge, it's noticeable that in the case of the error, the last accesses of "soffice.bin" occur in C:\Users\Name\AppData\Roaming\LibreOffice\4\user... while in the case where it works, fonts like C:\Windows\Fonts\DejaVuSans.ttf and various INI files (e.g., C:\Program Files (x86)\LibreOffice\program\soffice.ini) are being loaded, and the program seemingly starts and loads resources. It's possible that also this problem might be related to another process, or it could be that The Bat! as an email client is causing the issue. In that case, my description might be a potential solution.
Dear jan, 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
Even though it's somewhat an old version, the issue smells like as this one: https://bugs.documentfoundation.org/show_bug.cgi?id=157135#
Dear jan, 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