| Summary: | Crash when moving a window | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Peter Toye <lo> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INSUFFICIENTDATA | ||
| Severity: | normal | CC: | xiscofauli |
| Priority: | medium | ||
| Version: | 6.0.2.1 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | ["basctl::Layout::ArrangeWindows()"] | Regression By: | |
|
Description
Peter Toye
2018-03-20 13:01:21 UTC
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided I wish I could reproduce it quickly. Unfortunately, when a program crashes it's not always possible to remember the exact steps that made it crash. Also, it seems that the crash has lost not only all my edits (about an hours work) but also the entire dialog, so reproducing the problem will not be a trivial task, if indeed it is possible. I would suggsst that in a future release of LibO the text of the crash report window be changed to say that it is only worth while reporting the bug if it can be reproduced. Unfortunately, by that time, the window with the crash report location in it will have disappeared..... Some thought on workflow is needed here if crashes are to be meaningfully reported and not just time-wasters, both for the reporter and for yourselves. Maybe put the text of the window into a text processor (e.g. Notepad on Windows) so that it can be quickly saved. Looking at http://crashreport.libreoffice.org/stats/signature/basctl::Layout::ArrangeWindows(), it seems this crash is really weird to reproduce. Closing as RESOLVED INSUFFICIENTDATA for the time being. Put it back to UNCONFIRMED if you manage to reproduce it again... |