If the user is elevated the two quit / close functions should behave the same.
Description
Description
Revisions and Commits
Revisions and Commits
rKLEOPATRA Kleopatra | |||
rKLEOPATRAca31d694351a Accept close event of main window if Kleo is run with elevated permissions | |||
rKLEOPATRAd812c442424e Do not quit Kleopatra when user chooses to just close the main window | |||
rKLEOPATRAb2c858895a47 Quit Kleopatra when last windows is closed for elevated users on Windows | |||
rKLEOPATRA1c4bf2f41a54 Do not block application shutdown with a QEventLoopLocker | |||
rKLEOPATRA57359f6296ec Do not quit Kleopatra when user chooses to just close the main window | |||
rKLEOPATRAbff1b01a2e45 Accept close event of main window if Kleo is run with elevated permissions | |||
rKLEOPATRAbfed041ea1b1 Do not block application shutdown with a QEventLoopLocker | |||
rKLEOPATRA662bdc315e7a Quit Kleopatra when last windows is closed for elevated users on Windows | |||
rKLEOPATRA51d9756abe0a Always quit on Quit for users with elevated permissions on Windows | |||
rKLEOPATRAf7efd7d6e6b5 Always quit on Quit for users with elevated permissions on Windows |
Related Objects
Related Objects
Event Timeline
Comment Actions
Yes, the kleopatra.exe process ist shut down for me with that version, too.
But I wonder if the remaining gpg-agent and scdaemon processes which remain may cause issues later on. The are still running with elevated rights according to the process explorer after restarting as normal user. It does not cause any immediately obvious issues, though.
Comment Actions
I don't see a problem here. Of course Kleopatra could run a gpgconf -K all when it really exits but I doubt that we need to do that in this special elevated case