Bug#658896: Please apply patch no_global_init_during_thread_callbacks.diff
ametzler at downhill.at.eu.org
Wed Jan 23 18:48:52 UTC 2013
On 2013-01-23 Carlos Alberto Lopez Perez <clopez at igalia.com> wrote:
> On 23/01/13 19:04, Andreas Metzler wrote:
> > On 2013-01-23 Carlos Alberto Lopez Perez <clopez at igalia.com> wrote:
> >> I'm attaching the debdiff. I rebuilt libgcrypt11 with the attached debdiff.
> >> After installing it, sudo works as expected.
>> According to the experiences in Ubuntu it breaks other stuff:
>> (+ 2 merged bugreports)
> If you download the last Ubuntu dsc for libgcrypt11
> $ dget -u http://archive.ubuntu.com/ubuntu/pool/main/libg/libgcrypt11/libgcrypt11_1.5.0-3ubuntu2.1.dsc
> You will see that the patch they are carrying is the one that
> I put on the debdiff (no-global-init-thread-callbacks.diff)
> The previous patch (enable-global-init-secure-memory.patch)
> applied on libgcrypt11/1.5.0-3ubuntu1 was the one that caused
> the regression and was the patch reverted (.
I am pretty sure you are mistaken.
Doublechecking LP #1013798 we find this:
| I just found the apparent root cause for the libgcrypt11 crash:
| Ubuntu includes a patch called
| This bug was fixed in the package libgcrypt11 - 1.5.0-3ubuntu2
| * debian/patches/enable-global-init-secure-memory.patch:
| Fix regression during disable/suspend of secure memory
| Afaict this bug should not be marked as "fixed released" anymore because
| 1.5.0-3ubuntu2.1 reverted 1.5.0-3ubuntu2.
enable-global-init-secure-memory.patch would have fixed LP #1013798
but was reverted back to no-global-init-thread-callbacks.diff (which
fixes the sudo/LDAP issue) because the regression
from no-global-init-thread-callbacks.diff to
was too severe.
LP #1013798 is still open and unfixed.
More information about the Pkg-gnutls-maint