@Ovation1357 - I think you are correct that the USB/flash drive is a correlation, however I don't think it is an absolute dependence, because I was using a fresh Ubuntu install on a totally normal HP desktop machine hard disk with no USB/flash in sight. The only factor I can think of is perhaps the hardware RAID controller.
In terms of backtraces etc, I had a similar problem in that I had no obvious way to run it through any of the usual tools, because it is automatically started by the X session management code (without checking if a suitable instance is already running). You can start an instance yourself and then restart gdm (etc) but a new keyring instance is automatically started (and crashes) and the one you started is completely ignored and doesn't crash. I guess apport is one option. The other options would be to hack and recompile the x-session-manager (or whatever is executing keyring) or else to figure out a functional wrapper script or alias of some kind. Thanks all for the workarounds, they are certainly easier than recompiling from SVN ;) -- gnome-keyring-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/218434 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
