Description: Working on a complex Draw file. Had created a new Layer as default Layer8, then renamed it and immmediately opened the dialogue box to check its visibility and lock status while its displayed name was black (expected) non-italic (expected) and Bold (what's that?') The crash dialogue invited me to reload, which I did from the icon. I can't remember any more details - I was expecting to see a recovery dialogue box but I possibly saw and complied with the crash reporting box on the way in. When LibreOffice tried to reload the splash screen cycled indefinitely. I tried to use TaskMaster to intervene but it said there were no applications running. I recorded a video in case it helps (16Mb) and have quarantined whatever happens to be left of the file I was working on. I will report back after I have reopened it with version details etc. Ask if you want the video. I couldn't see anything worth 16Mb of storage on it. Meanwhile. AFAIK this is trhe only bug report on this module from Draw. I will also file another report on clicking the position and size information with no object selected. Actual Results: The program reported it had crashed. The crash report was successfully uploaded. You can soon find the report at: crashreport.libreoffice.org/stats/crash_details/a8a4a07f-f496-47ec-90b5-38afbf9ded1c Please check the report, and if no bug report is connected to the crash report yet, open a new bug report at bugs.documentfoundation.org. Expected Results: I expected the Visible-Printable-Locked dialogue to appear. Reproducible: Didn't try User Profile Reset: No Additional Info: 7.0.3.1 (X64) crashreport.libreoffice.org/stats/crash_details/a8a4a07f-f496-47ec-90b5-38afbf9ded1c gerrit.libreoffice.org / core / d7547858d014d4cf69878db179d326fc3483e082 It would help if the information could be copied to clipboard!
Created attachment 168198 [details] The file after the crash report said all files have been saved. Prior to the crash, working on Page 2, I had added a frame (Frame 8) after BlueGrid and before RedTroop. I thern renamed the frame BlackGrid (by right clicking, not using the dialogue) then tried to opened the dialogue - it crashed. AFAIR the crash reporter said it had been saved. This is a copy of the saved file. On reloading, using default choices following the crash, the file needed repair. The repaired file does not have the added frame.
Prior to the crash, working on Page 2, I had added a frame (Frame 8) after BlueGrid and before RedTroop. I then renamed the frame BlackGrid (by right clicking, not using the dialogue) then tried to opened the dialogue - it crashed. AFAIR the crash reporter said it had been saved. This is a copy of the saved file. On reloading, using default choices following the crash, the file needed repair. The repaired file does not have the added frame.
The crash cannot be replicated on the recovered file. Prior to the crash I had done a lot of work involving rotating rectangles to find the correct size of grid for the diagram. These were all on the layout frame and subsequently deleted. Without the prior work (I had notes of the calculations I had done) the crash did not repeat.
Hi DrC, Have you reproduced the crash again since you reported this issue ?
No - Draw insisted on repairing it before it would do anything. I was rather hoping a developer might be able to work out what happened from whatever needed fixing otherwise there's nothing to be won from the crash detector saving it. Prrsumably your Draw also repaired it?
I haven't come across it again in further work but that further work is on 'brain rest' at the moment. Meanwhile, life gets even more complicated because Windows10 has been sent a couple of restart updates in the meantime. I suggest this should be left in case or until somethung else rings the same bell.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to DrC from comment #6) > I haven't come across it again in further work but that further work is on > 'brain rest' at the moment. Meanwhile, life gets even more complicated > because Windows10 has been sent a couple of restart updates in the meantime. > > I suggest this should be left in case or until somethung else rings the same > bell. Let's close it as RESOLVED WORKSFORME for the time being. Feel free to reopen it if you experience the issue again