seahorse segfault when adding remote server ssh key

Bug #308985 reported by Fernando Miguel
28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seahorse (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: seahorse

I was trying to add a remote server ssh key, but i just got a popup with

<big><b>Couldn't configure Secure Shell keys on remote computer.</b></big>

(seahorse-ssh-askpass:19577): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse-ssh-askpass:19577): atk-bridge-WARNING **: IOR not set.

(seahorse-ssh-askpass:19577): atk-bridge-WARNING **: Could not locate registry

(seahorse-ssh-askpass:19648): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse-ssh-askpass:19648): atk-bridge-WARNING **: IOR not set.

(seahorse-ssh-askpass:19648): atk-bridge-WARNING **: Could not locate registry
Host key verification failed.

Afterwards i noticed that there was another popup under it, asking for yes/no and another for password.
to enter both, i had to keep clicking on them with mouse.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: seahorse 2.24.1-0ubuntu1
ProcEnviron:
 SHELL=/bin/bash
 PATH: custom, no user
 LANG=en_US.UTF-8
SourcePackage: seahorse
Uname: Linux 2.6.28-2-generic x86_64

Tags: apport-bug
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

from gdb:

$ gdb --args seahorse
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /usr/bin/seahorse
[Thread debugging using libthread_db enabled]
[New Thread 0x7f2c33951780 (LWP 19494)]

(seahorse:19494): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse:19494): atk-bridge-WARNING **: IOR not set.

(seahorse:19494): atk-bridge-WARNING **: Could not locate registry
** Message: init gpgme version 1.1.6
[New Thread 0x7f2c23f8f950 (LWP 19563)]
** Message: could not grab keyboard
** Message: could not grab keyboard

** (seahorse:19494): WARNING **: SSH command failed: (255)

** (seahorse:19494): WARNING **: SSH error output:
(seahorse-ssh-askpass:19577): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse-ssh-askpass:19577): atk-bridge-WARNING **: IOR not set.

(seahorse-ssh-askpass:19577): atk-bridge-WARNING **: Could not locate registry

(seahorse-ssh-askpass:19648): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse-ssh-askpass:19648): atk-bridge-WARNING **: IOR not set.

(seahorse-ssh-askpass:19648): atk-bridge-WARNING **: Could not locate registry
Host key verification failed.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f2c33951780 (LWP 19494)]
0x00007f2c30e83cec in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
(gdb) quit
The program is running. Exit anyway? (y or n) y

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

strace

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

$ strace -f -o seahorse.strace.log seahorse

(seahorse:23810): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse:23810): atk-bridge-WARNING **: IOR not set.

(seahorse:23810): atk-bridge-WARNING **: Could not locate registry
** Message: init gpgme version 1.1.6
** Message: could not grab keyboard

** (seahorse:23810): WARNING **: SSH command failed: (255)

** (seahorse:23810): WARNING **: SSH error output:
(seahorse-ssh-askpass:24210): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse-ssh-askpass:24210): atk-bridge-WARNING **: IOR not set.

(seahorse-ssh-askpass:24210): atk-bridge-WARNING **: Could not locate registry

(seahorse-ssh-askpass:24347): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(seahorse-ssh-askpass:24347): atk-bridge-WARNING **: IOR not set.

(seahorse-ssh-askpass:24347): atk-bridge-WARNING **: Could not locate registry
Host key verification failed.

** Message: could not grab keyboard

** (seahorse:23810): CRITICAL **: couldn't read from seahorse-ssh-askpass: Broken pipe
upeek: ptrace(PTRACE_PEEKUSER,24207,120,0): No such process
bugabundo@blubug:~$ gedit seahorse.strace.log

(gedit:25166): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gedit:25166): atk-bridge-WARNING **: IOR not set.

(gedit:25166): atk-bridge-WARNING **: Could not locate registry
Traceback (most recent call last):
  File "/usr/lib/gedit-2/plugins/bracketcompletion.py", line 243, in deactivate
    window.disconnect(handler)
NameError: global name 'handler' is not defined

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in seahorse:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

Hi Sebastien
Thanks for looking into this.

Currently i cant see it crashing, and the key seems to be set on the server, but sshing to it wont use the key for login. but thats another prob.
From what i can see, the original bug/crash is fix.

Any tips on current prob?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.