Hi, Yesterday I followed up on a Debian bug against KeePassX that I think affects Tails as well. Now I'm a bit lost in the technical details behind this. If someone else could have a look and answer for me, it might prevent me from saying silly things :)
https://bugs.debian.org/658312 Felix Geyer: > On 11.08.2015 22:38, sajolida wrote: >> Hi, I can confirm that this bug also happens in Tails >> (https://tails.boum.org/) on both our stable version (based on Wheezy) >> and our development version (based on Jessie). >> >> The consequences here are similar: if Tails is shut down while KeePassX >> is still open, then on the next reboot, KeePassX opens with a warning >> about "The database you are trying to open is locked". >> >> This behavior can be triggered by sending the SIGINT signal to KeePassX >> (for example using `kill -s INT`). >> >> KeePassX should instead close the database gracefully and release any >> lock when received SIGINT. > > What kind of desktop session is Tails running? > > KeePassX doesn't setup any signal handlers so sending SIGINT or SIGTERM > will just kill it. > However it does react to requests from the X session manager. > It ask whether to save changes, remove the lock file etc. > Tested on KDE and Gnome 3. _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
