Created attachment 118937 [details] Exception stacktrace Open a report that uses a query that itself contains a parameter. The parameter input dialog pops up Cancel this dialog (for example, if one clicked the wrong report) A huge dialog pops up showing a huge stacktrace of an exception
I would suggest some small dialog saying "User operation aborted" or something,
Created attachment 118939 [details] Test database with report Open the attached database Open the report Query_Table Click on Cancel in the parameter input dialog
On pc Debian x86-64 with master sources updated today, I could reproduce this. I also noticed this on console: warn:legacy.osl:28607:1:xmloff/source/style/xmlimppr.cxx:678: Exception caught; style may not be imported correctly. warn:legacy.osl:28607:1:xmloff/source/core/xmlerror.cxx:181: An error or a warning has occurred during XML import/export! Error-Id: 0x20040001 Flags: 2 ERROR Class: 4 API Number: 1 Parameters: 0: FooterBackGraphicURL Exception-Message: The given value cannot be converted to the required property type. (property name "FooterBackGraphicURL", found value type "void", required property type "string") Position: Public Identifier: System Identifier: Row, Column: 2,2346 warn:legacy.osl:28607:1:dbaccess/source/ui/uno/dbinteraction.cxx:66: BasicInteractionHandler::BasicInteractionHandler: enabling legacy behavior, there should be no clients of this anymore!
** 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.1.6 or 5.2.3 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-20161108
Still happens with 5.3.0.0.alpha0+. It is hard to test with 3.3, since it does not work with Java versions that are available anywhere, but I assume the problem was there even for 3.3.
** 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 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
Same with 5.4.2.2.
It is the same with this 6.0 as well: Version: 6.0.0.0.alpha1 Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: de-AT (de_AT); Calc: CL
The same with 6.1.3.
Created attachment 146990 [details] bt with debug symbols On pc Debian x86-64 with master sources updated yesterday, I could still reproduce this.
Created attachment 146991 [details] bt from "enabling legacy behavior, there should be no clients of this anymore"
Caolán: it seems weld allowed to pinpoint the root cause of this bugtracker. Any thoughts how to fix this? Is the second bt the cause of the problem?
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/e61dec64f86413f3c7d1d32e1675287eb3550f1f%5E%21 Related: tdf#94446 don't assert on unsetting focus handlers It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/92c34111dd8095b97a3761ab10c3ac4a3c191310%5E%21 Related: tdf#94446 set parent for dialog It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/6e8605ee6de4ead23925476f0e945b51dea26be0%5E%21 Related: tdf#94446 don't assert on unsetting focus handlers It will be available in 6.2.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/57bfb56972dc101200466054f0f9446301c214cb%5E%21 Resolves: tdf#94446 if this is a SQLException in disguise, throw that instead It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
We have support for just ignoring the "input param cancelled" exception, but in the reportbuilder it gets wrapped a few levels inside other exceptions to get the exception past the various exception specifications (AFAICS), if I unwrap it on leaving the reportbuilder code then things seem to work just right out of the box