After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573767 - gnome-keyring-daemon crashed with SIGSEGV
gnome-keyring-daemon crashed with SIGSEGV
Status: RESOLVED FIXED
Product: gnome-keyring
Classification: Core
Component: general
2.25.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-03-02 15:09 UTC by Sebastien Bacher
Modified: 2009-03-30 23:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Sebastien Bacher 2009-03-02 15:09:30 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

Thread 1 (process 7742)

  • #0 egg_secure_realloc_full
    at egg-secure-memory.c line 277
  • #1 egg_buffer_reserve
    at egg-buffer.c line 175
  • #2 egg_buffer_resize
    at egg-buffer.c line 190
  • #3 run_client_thread
    at gck-ssh-agent.c line 118
  • #4 g_thread_create_proxy
    at /build/buildd/glib2.0-2.19.8/glib/gthread.c line 635
  • #5 start_thread
    from /lib/libpthread.so.0
  • #6 clone
    from /lib/libc.so.6
  • #7 ??
(gdb)"
Comment 1 Stef Walter 2009-03-02 15:16:31 UTC
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?
Comment 2 Sebastien Bacher 2009-03-30 23:34:46 UTC
the ubuntu submitter didn't get the bug again let's close it for now