GNOME Bugzilla – Bug 573767
gnome-keyring-daemon crashed with SIGSEGV
Last modified: 2009-03-30 23:34:46 UTC
This bug has been opened on http://bugs.launchpad.net/bugs/332342 "The trigger appears to have been an ordinary ssh connection; I have ssh connection multiplexing enabled by default in .ssh/config, which explains the verbose output, but this output is normal for this particular host and is not normally a problem. $ ssh -C cocoplum.canonical.comControl socket connect(/home/vorlon/.ssh/master-vorlon@cocoplum.canonical.com:22): Connection refused Control socket connect(/home/vorlon/.ssh/master-vorlon@chinstrap.ubuntu.com:22): Connection refused ControlSocket /home/vorlon/.ssh/master-vorlon@chinstrap.ubuntu.com:22 already exists, disabling multiplexing Error reading response length from authentication socket. Permission denied (publickey). the apport-retrace command appears to be broken in jaunty, but here's a backtrace from manually unpacking the apport report and running gdb with the dbgsym packages installed. (gdb) thread apply all bt full
+ Trace 213064
Thread 1 (process 7742)
(gdb)"
I ran into this problem too and I believe I fixed it in HEAD (and the soon to be released 2.25.92). When you get a chance could you verify that this is the case?
the ubuntu submitter didn't get the bug again let's close it for now