Hallo, (I'm the original reporter of this bug, and I didn't get many emails from this report because I wasn't put in CC).
This bug has now been fixed in version 2.2.2-1. The application now starts in the foreground as normal, not hidden in the background. One point for the upstream developer that might be helpful: I could argue that the feature to close the application window and run the application hidden in the background as a service is not really needed and is a technical burden. A sensitive application like Ausweisapp should always run in the foreground and let the user know that the application is running, and once the window is closed the application will quit, not hide in the background while still running. There is no need for the application to continue running hidden in the background. If the user wants to use the Ausweisapp desktop application to communicate with the browser, then the user must make the decision to keep the application running in the foreground until the process is complete and then close it. A use case I was faced with to support this argument: I started the process of proving my personal identity on a government website. I had no idea that the browser was communicating with the Ausweisapp desktop application while the application was hiding in the background. The process was waiting for me to interact with the desktop application, but I had no idea what to do because the application was hiding in the background. A sensitive process like this should always be in the foreground. In short, remove the ability to close the application window and leave it running in the background - it's not needed. And consequently, remove the tray icon - it will be useless by then. Best, Amr
