New Suggested Fix (taking into account C de-Avillez's input above): 1) inform the operator that the ~/.gnupg/ directory and all the files in it are owned by root and therefore cannot be used to generate a key.
2) either (my strong preference) 2.1.1) give operator option to change the ownership of the directory and files to be controlled by their userid. 2.1.2) authenticate their sudo password, make the ownership changes. 2.1.3) ask if they wish to try creating the keys again (ie. without having to re-enter the configuration info). or (minimally -- I don't prefer this and think its inadequate) 2.2.0 provide a short explanation that they will need to do the steps above manually. >From a user experience view point I think the 2.1.1-3 branch is quite a bit better. The user is well-informed as to what the problem is and has an immediate action they can take to fix the brokeness and to continue on with the creation of their keys. Otherwise they may be stuck in a situation they don't have the knowledge to fix and essentially Seahorse will stop working for them -- again note that in this root ownership condition 'Syncing and Publishing' is broken as well, so applying this fix would solve that problem as well. Also this set of actions could be added to the 'Syncing and Publishing' function as well (if there is not already a bug report written for that bug there probably should be). -- Seahorse won't generate a key when .gnupg directory owned by root, only gives unhelpful "General error" https://bugs.launchpad.net/bugs/321287 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
