>> Perhaps try seahorse as a workaround? A reboot seems to have cured this issue. Hopefully it doesn't crop up again, but if it does I'll try to figure out how to reproduce it.