Created attachment 79935 [details] observed screen with red marks to point out strange areas of the screen Problem description: Maybe once a month ^ while using LibO in average about 3 - 4 times per week, I get the strange screen of which I attached a screen shot; I could not yet find out what causes this behavior of LibO. I say LibO because I never got such a screen in another application. I still can save my file - if I am quick. LibO crashes within maybe 10 - 20sec - guessed value. Today I was fast and closed LibO and restarted it. Although I don't know the route cause yet. I want to report it here to encourage other readers to add information when they observe a similar screen and hope that joining forces will lead to a solution. Operating System: Windows XP Version: 3.6.6.2 release
Created attachment 79936 [details] screen shot with marked unregularly appearing elements
Comment on attachment 79935 [details] observed screen with red marks to point out strange areas of the screen better use the second attachment. I cannot delete the first one.
Strange..never seen that before with Win7 & Ubuntu 12.04 Perhaps XP users can confirm that behavior
I think having seen a fix about this kind of bug. Could you give a try to 4.0.3? FYI, there will be a last 3.6 version (see https://wiki.documentfoundation.org/ReleasePlan#3.6_release) and 4.0.3 is now recommended version (compared to 3.6.6).
@Julien Nabet I will move to 4.0.3 or 4.0.4 soon and will definitely keep an eye on this. Should someone have an idea on what to look for when such a screen appears, please let me know, I will try to verify.
Caolán: for the moment, we'll wait for feedback with newer LO version but you might be interested in this bugtracker since it might be a vcl problem (if it's still reproducible of course!)
Dear Bug Submitter, Please read the entire message before proceeding. 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO
Hi and sorry for my late reply. I reported this bug on v3.6.6.2. In the meantime I migrated to 4.2.4.2 and typically move to the next family at x.y.4 Although I created many doc files, in newer versions, I don't recall having seen this bug. Thus I assume the bug is done. Why? If someone worked on it, thanks a lot to the one(s) who did the effort. If not, who cares as long as it doesn't show up again. If needed I create a new bug report.