Comment 33 for bug 1013798

You're welcome!

On Tue, Apr 2, 2013 at 8:31 AM, Adam Stokes <email address hidden>wrote:

> Thank you Michael I really appreciate the testing. I'll get this
> packaged up this week and have an SRU sent out for the releases.
>
> Thanks
> Adam
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1013798
>
> Title:
> Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1
>
> Status in “libgcrypt11” package in Ubuntu:
> In Progress
> Status in “libgcrypt11” source package in Lucid:
> In Progress
> Status in “libgcrypt11” source package in Oneiric:
> In Progress
> Status in “libgcrypt11” source package in Precise:
> In Progress
> Status in “libgcrypt11” source package in Quantal:
> In Progress
> Status in “libgcrypt11” source package in Raring:
> In Progress
>
> Bug description:
> [Impact]
> This regression was introduced from bug 423252
>
> [Test Case]
> 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)
>
> [Regression Potentional]
> All known test cases pass so unless there is another corner case the
> regression potentional should be minimal.
>
> 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:
>
> 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
>