Feature request:

1. Allow the user to enable verbose debug logging in the main build (ie shouldn't require recompiling the app; it should just be a toggle button or change to about:config at runtime)
2. Update this project's documentation describing how the user can enable and view the extension's debug log messages

Problem

Problem: There is currently no way (at least that's easy to find) to enable verbose debug logging so that a user can figure out what failed when this extension doesn't work as expected.

I needed to sign a document today (PIN2) on an Estonian government website, but it failed. I got a very unhelpful error message displayed in the browser:

Signing failed. Please make sure the ID-card software is installed and updated and web browsers are configured correctly. Further guidance

I'm 100% sure that the ID software is installed and my smartcard is recognized by my browser (and this extension) because I used it to sign-into the portal (PIN1). I tried it again in another tab and confirmed that, yes, it's still connected and working (again PIN1).

I tried to sign the document again (PIN2), and got the same unhelpful message in the browser.

I checked the browser's debugging console, but nothing was there. I checked the network tab, and all requests were 200.

I tried downloading the document and opening it for signing locally in qdigidoc4, and when I tried to sign the doc, I got a dreaded Segmentation Fault

Is this extension failing for the same reason? Is it also caused by a segfault? Or is it some backend API failing because of the segfault? I have no idea because I cannot view any log messages to see what is going on under the hood.

Solution

This tool needs a way for the user to be able to enable and view very, very detailed debug log messages so that they can pinpoint issues and submit bug reports or pull requests.