https://bugs.kde.org/show_bug.cgi?id=405020
Dan Jensen <ad...@leinir.dk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ad...@leinir.dk
--- Comment #1 from Dan Jensen <ad...@leinir.dk> ---
As much as i like the idea of the application getting out of the way, i'm not
sure i see a way of doing this that doesn't involve storing the password in
memory for a while, which... seems like a concept with which our more security
conscious people would be terribly displeased. Perhaps a different approach
might be to solve the core issue, which is that Discover checks for updates
(and blocks your other operations) on startup, regardless of how that launch
occurred. If that update check did not occur when you launch Discover with some
parameter to show a specific application (either from a .deb, .rpm, an
appstream link or anything else like that), then you would not suddenly have to
wait for a potentially long running update check.
--
You are receiving this mail because:
You are watching all bug changes.
