[Bug 1013798] Re: Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1

[gdi2k]

I got a helpful response from Saúl Ibarra Corretgé at AG Projects, the
makers of Blink. I will paste it below:

We do have plans to repackage Blink for Precise, it will happen after
the next python-sipsimple release, but we have no ETA for that yet.

As for the crash, it happens somewhere in libcrypto, which is wrapped by
python-gnutls, so there is nothing to fix in Blink. However, we are also
the authors of python-gnutls, so if it's a problem in that library we
will fix it. Unfortunately, the problem seems to be in libcrypto, not in
python-gnutls, so there is not much we can do.

Nevertheless I'll have a look at this and see if there is anything to be
fixed in python-gnutls.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libgcrypt11 in Ubuntu.
https://bugs.launchpad.net/bugs/1013798

Title:
  Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1

Status in “libgcrypt11” package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure to which package I should report this, but I use the
  Blink SIP client (http://icanblink.com/) and noticed that it segfaults
  at startup if I have libgcrypt11 1.5.0-3ubuntu0.1 installed, but if I
  force the older version 1.5.0-3 Blink works ok.

  Blink is a Python app and I think I managed to find the line of Python
  code that causes the segfault. The line is 'from gnutls.crypto import
  X509Certificate, X509PrivateKey'. Here is what happens when I run it
  in the Python console:

  Python 2.7.3 (default, Apr 20 2012, 22:44:07) 
  [GCC 4.6.3] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> from gnutls.crypto import X509Certificate, X509PrivateKey
  Segmentation fault (core dumped)

  I'm using 12.04, but I originally noticed the issue when I had 11.10
  and the proposed updates enabled. One day there were some updates that
  broke Blink and going through the updates I discovered that reverting
  libgcrypt fixed it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1013798/+subscriptions