Hi I've ran into an issue while updating the port of LibreOffice to 4.2.6.3 on OpenBSD and I can't really find the source of the issue. Basically any element of the LO installation results in the following exception: $ soffice --help terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException' I've traced and checked everything I could and all dynamic libraries are being loaded properly. Can someone give me a hint please? Thanks
In general, I'd suggest that you take developer questions to the Dev list: https://wiki.documentfoundation.org/Development/Mailing_List That's probably the quickest way to get a response. Given that 4.3.x is running on OpenBSD now, I'm going to guess that this bug is fixed, but I'll toss it into NEEDINFO rather than just resolve it. Status -> NEEDINFO
Created attachment 111711 [details] loffice --help --backtrace
I can confirm it, though on an unusual OS [1]. Version 4.3.3: # loffice --help terminate called after throwing an instance of 'com::sun::star::container::NoSuchElementException' terminate called recursively Attaching backtrace. [1] http://osdyson.org/
Created attachment 111727 [details] lowriter --help --backtrace Note the hieroglyphs.
well, it is not hieroglyphs :-) >>> print "\045\120\122\117\104\125\103\124\116\101\115\105\040\045\120\122\117\104\125\103\124\126\105\122\123\111\117\116\045\120\122\117\104\125\103\124\105\130\124\105\116\123\111\117\116" %PRODUCTNAME %PRODUCTVERSION%PRODUCTEXTENSION >>>
I know what's wrong (in my case) :-) soffice.bin get _Unwind* symbols from libc, but should get is from libgcc_s
(In reply to Igor Pashev from comment #3) > I can confirm it, though on an unusual OS [1]. > > Version 4.3.3: > > # loffice --help > terminate called after throwing an instance of > 'com::sun::star::container::NoSuchElementException' > terminate called recursively Interesting, interesting. I can't confirm on Ubuntu 14.04 with 4.3.2.2 or 4.4.0.1, but it sounds like there's enough here to change Status -> NEW > Attaching backtrace. > Great, thanks!
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear Robert Nagy, 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
No more verification since 2015. I close this bug report as INSUFFICIENTDATA. If this is wrong, please reopen as NEW with your LibreOffice build info.