Description: LO 7.0.4 cannot be terminated on win2012 in terminal server mode sometimes. A document can be closed. Ctrl+Q or click on croos doesn't work. The task manager must be used to exit. Steps to Reproduce: 1. cannot be reproduced (???) 2. 3. Actual Results: LO can't be terminated Expected Results: standard termination Reproducible: Sometimes User Profile Reset: No OpenGL enabled: Yes Additional Info:
Hi kabilo, How are you opening LO? 1- Are you opening LO through it's normal Writer shortcut? 2- Are you opening LO by double clicking a document? 3- Are you opening LO using it's API or through a third party program or IDE? 4- Are you opening LO using DCOM and it's API or through a third party program or IDE? Another questions: 1- Have you monitored soffice.bin using procdump (on CMD use procdump -e -t soffice.bin) or winDBG? 2- Have you tried to reset your LO profile? See https://wiki.documentfoundation.org/QA/FirstSteps just to exclude corruption LO profile and skia parts. Please get back to us with these informations and analysis suggested above. Please read the following link as well: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace Best Regards.
Hi Makrea, I think this problem was after exporting data to LO from 3rd party applications. I can't verify this, version 6.4 has been returned to the production environment. Regards
(In reply to kabilo from comment #2) > Hi Makrea, > I think this problem was after exporting data to LO from 3rd party > applications. > I can't verify this, version 6.4 has been returned to the production > environment. > Regards Hi kabilo, Since you are "exporting data to LO from 3rd party applications", those applications must be using LO by means of its API. I did a code comparison of both versions of LO, the one that is working, and the one that is broken and I found some code that for me is the cause of the problem. The new code creates a "block" (they name it veto) on the close operation if LO is opened by its API. When in this state LO can only be closed by a OLE Object demanding the LO to close by its API. A completely biased usage of LO in my opinion when users interact with LO after exporting data to the document. See this https://bugs.documentfoundation.org/show_bug.cgi?id=141097#c13 for more information. We also went back to a previous version (6.3.5.2) of LO in production environment. Please can you tell the complete build number of your 6.4 version? Is it 6.4.7.2? Best regards
Hi Makrea, yes, we use 6.4.7.2. This version works correctly. Regards
*** This bug has been marked as a duplicate of bug 141097 ***