Description: I was working on an important document and thought about installing the Roboto font. SO I went to google fonts and downloaded the Roboto font from https://fonts.google.com/specimen/Roboto. Version: 6.1.0.1 (x64) Build ID: 378e26bd4f22a135cef5fa17afd5d4171d8da21a CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-IN (en_IN); Calc: CL Multiple styles or form of the font was installed like Robot italic, roboto bold, roboto regular, etc. I installed all the font simultaneously. When I opened LibreOffice writer, it started turning white and then froze and this process occurred many times. I then closed the application and opened it again. I was able to recover the file but some data was lost. I had not saved the file. Steps to Reproduce: 1.Download a font from google fonts like https://fonts.google.com/download?family=Roboto 2.Open Libreoffice writer. keep it open 3.Install all teh variants of font simentaneously 4. You might or might not experince this proeblem like I did , but it should be there Actual Results: Libre OFfice writer crashed and did not respond Expected Results: --------------------------- Reproducible: Didn't try User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no Version: 6.1.0.1 (x64) Build ID: 378e26bd4f22a135cef5fa17afd5d4171d8da21a CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-IN (en_IN); Calc: CL
If it's an important file, backups are useful. Also, working on a not stable version (6.1 branch is still in RC) may be risky and should be used for tests only. Any link to a crashreport?
(In reply to Julien Nabet from comment #1) > If it's an important file, backups are useful. > Also, working on a not stable version (6.1 branch is still in RC) may be > risky and should be used for tests only. > > Any link to a crashreport? tell me how to generate one, I will try to do it.(In reply to Julien Nabet from comment #1) > If it's an important file, backups are useful. > Also, working on a not stable version (6.1 branch is still in RC) may be > risky and should be used for tests only. > > Any link to a crashreport?
(In reply to Julien Nabet from comment #1) > If it's an important file, backups are useful. > Also, working on a not stable version (6.1 branch is still in RC) may be > risky and should be used for tests only. > > Any link to a crashreport? I got a report, from windows.Take a look Source LibreOffice Summary Stopped responding and was closed Date 21-07-2018 05:29 PM Status Report sent Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\LibreOffice\program\soffice.bin Problem signature Problem Event Name: AppHangB1 Application Name: soffice.bin Application Version: 6.1.0.1 Application Timestamp: 5b3d74ce Hang Signature: 7a0a Hang Type: 134217728 OS Version: 10.0.17134.2.0.0.768.101 Locale ID: 16393 Additional Hang Signature 1: 7a0a0ae5ce5530d0e2e1be4f53ccfec4 Additional Hang Signature 2: 53ca Additional Hang Signature 3: 53cad8b437339d77f771fb4993726ecd Additional Hang Signature 4: 7a0a Additional Hang Signature 5: 7a0a0ae5ce5530d0e2e1be4f53ccfec4 Additional Hang Signature 6: 53ca Additional Hang Signature 7: 53cad8b437339d77f771fb4993726ecd Extra information about the problem Bucket ID: 0649c315ff757f67113dd77e33e6d10c (1242386009260740876) Source LibreOffice Summary Stopped responding and was closed Date 21-07-2018 05:29 PM Status Report sent Description A problem caused this program to stop interacting with Windows. Faulting Application Path: C:\Program Files\LibreOffice\program\soffice.bin Problem signature Problem Event Name: AppHangB1 Application Name: soffice.bin Application Version: 6.1.0.1 Application Timestamp: 5b3d74ce Hang Signature: 7a0a Hang Type: 134217728 OS Version: 10.0.17134.2.0.0.768.101 Locale ID: 16393 Additional Hang Signature 1: 7a0a0ae5ce5530d0e2e1be4f53ccfec4 Additional Hang Signature 2: 53ca Additional Hang Signature 3: 53cad8b437339d77f771fb4993726ecd Additional Hang Signature 4: 7a0a Additional Hang Signature 5: 7a0a0ae5ce5530d0e2e1be4f53ccfec4 Additional Hang Signature 6: 53ca Additional Hang Signature 7: 53cad8b437339d77f771fb4993726ecd Extra information about the problem Bucket ID: 0649c315ff757f67113dd77e33e6d10c (1242386009260740876)
Here a link which explains how to retrieve a backtrace on Windows: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace
(In reply to Julien Nabet from comment #4) > Here a link which explains how to retrieve a backtrace on Windows: > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows: > _How_to_get_a_backtrace Hello evsamtp@hotmail.com, Could you please try to follow the link shared by Julien to retrieve a backtrace ?
This was tested on 6.1.0.1; should try again on 6.1.0.3. It sounds like LO was not responding and you closed it. Is that correct? That is different than a complete crash. I have been testing many font families on LibreOffice lately. And I have been installing the font files for each family all at once by selecting all the font files, right-clicking, and selecting install. This causes LO to be "Not Responding" for quite awhile. While it is not responding the screen "goes white" and then it comes back, you think it is back, you click anywhere and it again goes to white and not responding. It cycles through this quite a few times before I actually have back control and a cursor. I just tested installing the 18 font files from Helvetica Neue Condensed and timed it. It took a little over 3 minutes to regain control. I installed all the Roboto font files yesterday with a similar time lag. So I am wondering if you could wait longer and regain control. Because it sounds like you manually closed the non-responding LO. There was another user with a different issue with LO on Windows 10, and their LO took 7 minutes to come back. I am on Windows 7 x64 using LO 6.1.0.3 x64. Been testing a lot of font families. and have been doing other things when waiting for LO to come back after installing font families. I assume LO is rebuilding its font cache and that is a substantial part of the lag. Once it is done I do have immediate access to the new fonts in the fonts list and go back to work creating the samples for all the fonts in that family. So I would recommend: - testing with LO 6.1.0.3 - waiting longer, it may come back .
(In reply to LibreTraining from comment #6) > So I would recommend: > - testing with LO 6.1.0.3 > - waiting longer, it may come back Latest in 6.1.x line is now 6.1.1. You might also try with a master build: https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/ Master and the upcoming 6.1.2 include some tweaks in Win font handling (maybe unrelated, but you never know). Set to NEEDINFO. Change back to UNCONFIRMED after you have provided further testing information.
Dear Bug Submitter, 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-20190321
Dear revsamtp, 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