I think I found out how to work around this issue. Since an empty test account didn't show the behaviour, I decided moving my dirs and files out of ~ until I got f-spot to work. After a while of some trial and error, I nailed it down to ~/.gnupg.
After that, I kept trying until I pinpointed the problem (at least for me) to gpg.conf. Since it was a nearly empty file (only three options, including default key and keyserver), I finally got to the offending option: use-agent Commenting this option was sufficient to make F-Spot close as expected. Could others affected see if this helps you as well? -- F-Spot refused to close, force quit used https://bugs.launchpad.net/bugs/211692 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
