https://bugs.documentfoundation.org/show_bug.cgi?id=168158
--- Comment #1 from Noel Grandin <[email protected]> --- I would suggest setting breakpoint where the exception is thrown, and examing the call stack at that point in time. When you know what the "good" call stack looks like, you can find the code that displays a message (i.e. handles the exception nicely). Work your way back up the "bad" call stack and examine the code as you go, try and find a similar spot to add code to handle the exception, like the "good" call stack did. -- You are receiving this mail because: You are the assignee for the bug.
