User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 Build Identifier: LibreOffice 5.2.0.4 I tried this with the LO applications that I use the most, being: LO Writer LO Impress LO Calc And I can confirm that, after performing an update today (August 10), when clicking on the button described as 'Styles and Formatting', this triggers a bug that closes all applications and force-kicks the user out of their session. Also it's worth pointing out this bug did not happen prior to updating today. Reproducible: Always Steps to Reproduce: 1.Open any application from LO Suite (Writer, Impress or Calc); 2.Click on the button to the right described as 'Styles and Formatting'; 3.The latest update released on August 10 triggers a bug that closes all applications and force-kicks the user out of their session. Actual Results: After the bug takes place, the system (Linux Mint 17.3 32-bit) shows the login screen, asking for a user and password.as if I had logged out of my session. Expected Results: Before performing the update released today (August 10), clicking on the 'Styles and Formatting' button actually displayed Formatting options. [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux Mint 17.3 32-bit. OS is 64bit: no Reset User Profile?No
Hello RoD_BT, *, I cannot confirm your bug with OS: Debian Testing AMd64 LO: Version: 5.2.0.4 Build ID: 066b007f5ebcc236395c7d282ba488bca6720265 CPU Threads: 4; OS Version: Linux 4.5; UI Render: default; Locale: de-DE (de_DE.UTF-8) nor LO: Version: 5.2.1.1 Build ID: 2d75cf29e6d05e44c404f0547047f1da6563d380 CPU Threads: 4; OS Version: Linux 4.5; UI Render: default; Locale: de-DE (de_DE.UTF-8); Calc: group Could it be that LO triggered some hardware defect (flaky RAM, or something else?)? HTH Thomas.
Hello there, Thomas, and thank you for investigating the issue. Could you please let me know how I can provide some extra info to detect the cause/trigger of the bug described before? I tried to reproduce the same error on other computers (laptops) and failed to do so. My problem is, as you may have noticed, that this turned out to be an isolated case.
You can go through this checklist: https://wiki.documentfoundation.org/QA/FirstSteps
Hello RoD_BT, *, (In reply to RoD_BT from comment #2) > Hello there, Thomas, and thank you for investigating the issue. > > Could you please let me know how I can provide some extra info to detect the > cause/trigger of the bug described before? I tried to reproduce the same > error on other computers (laptops) and failed to do so. My problem is, as > you may have noticed, that this turned out to be an isolated case. are there any differences between the system where you reproduced this bug and your mentioned other computers (different distro / version / architecture, using the distro's version of LO, different WM/DE in use, etc.)? If you can only reproduce it on this particular system, it would be difficult for us to try to reproduce it ... :( You could try to get a backtrace or a strace log by starting LO from commandline as described on https://wiki.documentfoundation.org/QA/BugReport/Debug_Information and / or trying one of our versions, if you could only reproduce it with Mint's LO version (but then you should close this bug and search it on https://bugs.launchpad.net/linuxmint to see, if it is already reported there). To find out, if it is a problem with the hardware of your system, this would be more difficult to answer (and would go beyond the scope of our bugtracker), but maybe an internet search for "Linux Mint automatic logout hardware problem" could be helpful ... ;) HTH Thomas.
Please, could you answer question in comment #4. Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
Dear Bug Submitter, 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-20180404
Dear Bug Submitter, 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-20180502