--- Please enter the report below this line. ---
I'm on unstable and after upgrading seahorse, the seahorse-agent crashes if a
new ssh connection is made.

<seahorse-agent running>
# ssh <somehost>
blah@hostname's password:
...
Last login: Fri Jun 15 18:01:50 2007

After that bug-buddy comes up and informs that seahorse-agent has crashed.

A more detailed report can be found here:
http://bugzilla.gnome.org/show_bug.cgi?id=447931

Debian Release: lenny/sid
  990 unstable        ftp.debian-unofficial.org
  990 unstable        ftp.at.debian.org
  500 etch            debian.beryl-project.org
    1 experimental    ftp.at.debian.org
--- Package information. ---
Depends                         (Version) | Installed
=========================================-+-===============
libart-2.0-2                  (>= 2.3.18) | 2.3.19-3
libatk1.0-0                   (>= 1.13.2) | 1.18.0-2
libavahi-client3              (>= 0.6.13) | 0.6.19-2
libavahi-common3              (>= 0.6.10) | 0.6.19-2
libavahi-glib1                (>= 0.6.12) | 0.6.19-2
libbonobo2-0                  (>= 2.15.0) | 2.18.0-2
libbonoboui2-0                (>= 2.15.1) | 2.18.0-5
libc6                          (>= 2.5-5) | 2.5-11
libcairo2                      (>= 1.4.0) | 1.4.6-1.1
libdbus-1-3                     (>= 0.94) | 1.1.0-1
libdbus-glib-1-2                (>= 0.73) | 0.73-2
libfontconfig1                 (>= 2.4.0) | 2.4.2-1.2
libgcc1                      (>= 1:4.1.2) | 1:4.2-20070609-1
libgconf2-4                   (>= 2.13.5) | 2.18.0.1-3
libglade2-0                  (>= 1:2.5.1) | 1:2.6.0-4
libglib2.0-0                  (>= 2.12.9) | 2.12.12-1
libgnome-keyring0                (>= 0.8) | 0.8.1-2
libgnome2-0                   (>= 2.17.3) | 2.18.0-4
libgnomecanvas2-0             (>= 2.11.1) | 2.14.0-3
libgnomeprint2.2-0            (>= 2.17.0) | 2.18.0-2
libgnomeprintui2.2-0          (>= 2.17.0) | 2.18.0-2
libgnomeui-0                  (>= 2.17.1) | 2.18.1-2
libgnomevfs2-0             (>= 1:2.17.90) | 1:2.18.1-2
libgnutls13                  (>= 1.5.3-0) | 1.6.3-1
libgpg-error0                    (>= 1.4) | 1.4-2
libgpgme11                     (>= 1.0.1) | 1.1.2-5
libgtk2.0-0                   (>= 2.10.3) | 2.10.13-1
libgtksourceview1.0-0          (>= 1.7.2) | 1.8.5-1
libice6                      (>= 1:1.0.0) | 1:1.0.3-2
libldap2                    (>= 2.1.17-1) | 2.1.30-13.4
libnautilus-extension1       (>= 2.17.90) | 2.18.1-3
libnotify1                     (>= 0.4.4) | 0.4.4-3
libnotify1-gtk2.10                        |
libnspr4-0d                 (>= 1.8.0.10) | 4.6.6-3
liborbit2                   (>= 1:2.14.1) | 1:2.14.7-0.1
libpanel-applet2-0              (>= 2.14) | 2.18.2-1
libpango1.0-0                 (>= 1.16.2) | 1.16.4-1
libpopt0                        (>= 1.10) | 1.10-3
libsm6                                    | 2:1.0.3-1
libsoup2.2-8                  (>= 2.2.98) | 2.2.100-1
libx11-6                                  | 2:1.0.3-7
libxcursor1                    (>> 1.1.2) | 1:1.1.8-2
libxext6                                  | 1:1.0.3-2
libxfixes3                   (>= 1:4.0.1) | 1:4.0.3-2
libxi6                                    | 1:1.0.1-4
libxinerama1                              | 1:1.0.2-1
libxml2                       (>= 2.6.28) | 2.6.29.dfsg-1
libxrandr2                   (>= 2:1.2.0) | 2:1.2.1-1
libxrender1                               | 1:0.9.2-1
libxul0d                                  | 1.8.1.4-2
zlib1g                       (>= 1:1.2.1) | 1:1.2.3-15
gconf2                      (>= 2.10.1-2) | 2.18.0.1-3

Le vendredi 15 juin 2007 à 18:48 +0200, Stefan Schoenleitner a écrit :


Did it happen only right after upgrading, or is it always happening now
since the upgrade?

In the former case, please tell us what version you were upgrading from
(you can see that in /var/log/dpkg.log). In the latter case, please try
to obtain a better backtrace by installing the relevant debugging
libraries (and if possible rebuilding seahorse itself with debugging
symbols as explained in http://wiki.debian.org/HowToGetABacktrace).

Cheers,

severity 429060 important
thanks

Hi,
I'm lowering the severity of this bugreport as no response was given
after some time and I can't reproduce it locally.

Bye

I appear to be seeing this bug reproduced on every login.  During the
login seahorse-agent will generally prompt me for the passphrase for my
SSH key and then segfault with what appears to be a very similar
backtrace.  This behaviour appeared within the past week.

In my opinion this bug should at least be important - no matter how
malformed the data it is dealing with the application should not crash,
especially given that it is a security sensitive application.

Is this still an issue for you? It's been awhile since you reported this
and this appears to be fixed. If not, please drop a statement here. Thanks.

Control: notforwarded -1
Control: tags -1 = moreinfo
...

Does this still happen? The upstream bug was closed as not having enough
information to investigate further.

The backtrace in the upstream bug didn't have debug symbols and involves a
call into libgnomeui, which doesn't exist in Debian any more, so I suspect
the code has changed a lot in the 13 years since the bug was reported and
this crash might well no longer exist.

    smcv