=== Logan__ is now known as Logan_ === G4MBY is now known as PaulW2U === yofel_ is now known as yofel [12:39] mitya57: thank you for reviewing merge 154767 [12:39] i forwarded the fix to debian + upstream [12:40] but can you please coach me on how to fix the distribution in debian/changelog? [12:42] nottheoilrig: just edit it with an editor [12:42] replace unstable with raring [12:42] jtaylor said that :) [12:42] also the version number is wrong for ubuntu [12:45] nottheoilrig: which number does the debian bug have? [12:46] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368297 [12:47] Debian bug 368297 in libldap-2.4-2 "sudo-ldap failes when you change uri to ldaps" [Serious,Open] [12:47] * mitya57 thought that libldap-2.4-2 != python-gnutls [12:49] and the bug linked to your branch is against libgcrypt11 [12:50] what is the correct way to reassign bug #1013798 to python-gnutls? [12:50] Launchpad bug 1013798 in libgcrypt11 (Ubuntu Raring) "Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1" [Critical,In progress] https://launchpad.net/bugs/1013798 [12:51] we would need this patch to be forwarded to debian pygnutls too [12:51] and upstream, do you have a link if you already did? [12:54] how do i mark it as forwarded upstream to dan@ag-projects.com? [12:54] add the link in also affects distribution [12:54] or just post the link [12:58] we need an answer from upstream on this [12:58] who knows maybe gcry_check_version is actually an alias for disable_all_crypto [12:58] which wouldn't surprise me with the crapy crypto apis we have ._. [12:59] the "merge into" is quantal, should i change the distribution to quantal? [12:59] no, but you can change "merge into" to raring [13:00] nottheoilrig: if you get a review on the patch I'm sure adam stokes will take care of the details [13:02] okay thanks [13:06] looking at the debian bug it may be to simple [13:06] gcrypt seems to be impossible to initialize properly when following the docs [13:08] jtaylor: ? [13:08] gcrypt is used implicitly by gnutls [13:09] but the applications need to initialize it [13:09] but they don't even know they are using gcrypt [13:10] it would probably best to revert the fix and use the patch debian used, and then get rid of gcrypt in raring+ as fast as possible :/ [13:10] but I'll leave that to the security team [13:11] i think that's a separate issue [13:12] python-gnutls already attempts to initialize gcrypt [13:13] (it invokes GCRYCTL_INITIALIZATION_FINISHED) [13:13] it just doesn't do it properly [13:14] if it didn't initialize gcrypt at all, gnutls_global_init would and the segfault would be resolved [13:16] if it initialized it according to the gcrypt manual, the segfault would be resolved [13:16] I see [13:16] i think the bug is that python-gnutls does some initialization [13:17] (which stops gnutls_global_init from invoking gcry_check_version) [13:18] but it doesn't initialize it properly === Ursinhal is now known as Ursinha [18:45] hi ,the sound on my system is incresaing and decresing on its own and i am having trouble typing due to this . Can you please tell me how to stop this. I tried disabling the pulseaudio service but that didnt help. I am having a HP CQ 45 207 TU notebook. Is it a bug in ubuntu ?