show stack trace in verbose mode (closes #2480) - #2481

/cc @matthid

Oh I was too slow: #2480 (comment)
Please only handle the one particular instance of the error.

The reasoning is that I want to move away from all the general "with e ->" clauses thoughout the code base. but that is a painful process (so I kind of provoke people to open issues by printing stacktraces on errors, this was imho better than if I forgot something and introduced breaking changes)

I'll understand.
Updated it and limiting to IOException. Unfortunately a bunch of inherited classes are also now catched the same way (PathTooLong, etc.). Is this okay?

@Stift in a perfect world i'd like to only catch the access denied error, but I can see the difficulties here. So I'm fine with it. Maybe we can add a code comment to clarify why it was added (to make it easier for future contributors to handle the sub-types differently). A link to your issue is probably just fine.

I know, that perfect world I also dream of. I just wanted to prevent filtering on message strings and the exception does not give more details.

Yes I agree, filtering of the string is error prone. Thanks for looking into this.

thanks!