Description: When I finish my work on a Writer document and I saved it, I normally want to close the Writer window. But since version 7.0.4.1 this does not work properly anymore. I am not able to close the complete window. I only can close the document itself. The LibreOffice-Suit-Window is father opened and can not be closed (neither by clicking on the X nor via Shortcut CTRL+Q or by mouse over the menue). After waiting a few minuts I can close the LibreOffice-Suit-Window without any problems. Steps to Reproduce: I am not sure if others have the same problem: 1. Open a ODT-document in writer and edit it 2. Save the document 3. Try to close the complete Writer window 4. Only close the ODT-documtent itself 5. Try to close the LibreOffice-Suit-window 6. Wait a few minuts 7. Try to close the LibreOffice-Suit-window again Actual Results: I can not close the main program window. Expected Results: The program windows should close. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.3 (x64) / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL
Thank you for reporting the bug. I can not reproduce the bug in Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nb-NO (en_US); UI: en-US Calc: CL Version: 7.2.0.0.alpha0+ (x64) Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Hello, I cannot reproduce this bug in Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL and Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 005adbefc746f9024adcf572c287dc061acbcf00 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Hello Knecker, Thank you for reporting the bug. But I cannot reproduce this bug. Version: LibreOffice_7.0.4_Linux_x86-64_rpm Time: Mon Mar 29 19:01:12 IST 2021
Hi Knecker, 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? Another questions: 1- Have you monitored soffice.bin using procdump 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.
Hello Knecker, Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
(In reply to Xisco Faulí from comment #5) > Hello Knecker, > Thank you for reporting the bug. To be certain the reported issue is not > related to corruption in the user profile, could you please reset your > Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and > re-test? > > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the issue is still present I purpose closing this bug. Zero feedback has been given to any of the comments. What you asked for, I asked more than a month ago. I welcome you to visit the bug: https://bugs.documentfoundation.org/show_bug.cgi?id=141097 This knecker bug (unconfirmed but I suspect), my bug, kabilo bug, and a duplicate of my bug all seems to be the same issue regarding opening LO through API enforcing a vetoexception on close. I will be more than happy to provide any info you need on 141097 bug thread. Best regards.
Dear Knecker, 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
Dear Knecker, 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