Description: Running "soffice.exe .uno:Open" causes a crash. The next time I opened LibreOffice it generated this crash report. http://crashreport.libreoffice.org/stats/crash_details/578d8f25-2f4f-4d93-b18d-da153a5a8e09 I'm running LibreOffice 6.1.1.2 64-bit on Windows 7 64-bit. Steps to Reproduce: 1. Open cmd.exe 2. enter cd "c:\Program Files\LibreOffice\program" 3. enter soffice.exe .uno:Open Actual Results: Microsoft Windows displays a window that says "LibreOffice has stopped working" and closes the program. Expected Results: No crash. Maybe show an error message if LibreOffice doesn't like the command line options. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 6.1.1.2 (x64) Build ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group threaded
I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: aaa3c31ba79b1b3d335dcf55d72837a13411b45e CPU threads: 16; OS: Windows 6.3; UI render: default; Locale: en-GB (en_GB); Calc: threaded
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
Created attachment 145205 [details] Minimal testcase file that causes the crash Resetting the profile did fix the issue. I was able to track the problem to the CollectUsageInformation property in registrymodifications.xcu. I've attached a minimal testcase registrymodifications.xcu file that can be used to reproduce the crash.
Ok, I can repro. Let's set to NEW and see what happens. The property can be enabled from the tools - options - libreoffice - advanced - expert configuration. Then it appears in registrymodifications.xcu as <item oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="CollectUsageInformation" oor:op="fuse"><value>true</value></prop></item> Command line output: UNO exception during client open: Given module is not a frame nor a window, controller or model. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 9a373521d7a328197a4bf9abeb0a981b7acba896 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on 19 October 2018
Dear Matt Perry, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present. Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US
Created attachment 164071 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this.
Dear Matt Perry, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
since: commit 2c0b84dc65739bfc47dca684e819717eb9cce387 Date: Mon Jul 19 17:00:17 2021 +0800 tdf#140107 Remove all collect usage data code. Remove all collect usage data code because we don't really use them. Change-Id: I8d83d57220bed8f8c15bd012584943cd0913500d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/119166 The support for CollectUsageInformation was removed so this case presumably doesn't arise anymore. I certainly can't reproduce it.