http://bugzilla.opensuse.org/show_bug.cgi?id=981020 Sebastian Wagner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebix+novell.com@sebix.at Assignee|bnc-team-screening@forge.pr |premysl.janouch@suse.com |ovo.novell.com | Summary|gnupg segmentation fault |Base:System/gpg2: Bug |"mpi-bit.c: No such file or |segmentation fault |directory." |"mpi-bit.c: No such file or | |directory." QA Contact|qa-bugs@suse.de |opensuse-communityscreening | |@forge.provo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=981020 http://bugzilla.opensuse.org/show_bug.cgi?id=981020#c2 --- Comment #2 from Sebastian Wagner --- I did the following changes and it works now again :) 2016-05-23 15:11:25|install|libpth20|2.0.7-142.80|x86_64||repo-oss|e742063b7e90c4dd38c3716d9d5cef0dab164b3b| 2016-05-23 15:11:25|install|libusb-0_1-4|0.1.13-36.3|x86_64||repo-oss|1eefb99284d32ed046f2f7bb7f75cde7dea358f1| 2016-05-23 15:11:25|install|dirmngr|1.1.1-5.2|x86_64||http-download.opensuse.org-5b2b9b6a|896cbc22e6eae2073318cf1ca48bdebd92de25c7| 2016-05-23 15:11:25|install|dirmngr-lang|1.1.1-5.2|noarch||http-download.opensuse.org-5b2b9b6a|8a061c9dbf9e2c1fd32bdab2c724380b4202c333| 2016-05-23 15:11:26|install|gpg2|2.0.24-5.1|x86_64|root@linux-gx1b|http-download.opensuse.org-6a00c28e|a2650fc5f627337f7c2eb21e088ddc047225d81a4917d91a69a3ece61a608e5d| 2016-05-23 15:11:26|install|gpg2-lang|2.0.24-5.1|noarch||http-download.opensuse.org-6a00c28e|1265d0a5edccc71bb01b51c641b0e7607cba7e09c2fa70744246d3ac2053b63a| I installed them all from Leap 42.1's Update repository. All except gpg2 have been installed as dependencies of leap's gpg2 package. Probably related to bug 979261? Downgrading libksba8 to leap's version 1.3.0-4.1 (from 1.3.4-1.1) did not help though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=981020 http://bugzilla.opensuse.org/show_bug.cgi?id=981020#c5 --- Comment #5 from Rainer Sabelka --- I can also reproduce the crash with gpg2-2.1.12-1.1 and libgcrypt20-1.6.5-2.1 (see bt in the attachment). I also ran valgrind. There is an "Invalid read" shortly before the crash: ~> valgrind gpg -k ==10542== Memcheck, a memory error detector ==10542== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==10542== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==10542== Command: gpg -k ==10542== gpg: enabled debug flags: memstat gpg: verwende Vertrauensmodell pgp gpg: "Trust-DB" wird überprüft gpg: removing stale lockfile (created by 10456) gpg: buffer shorter than subpacket gpg: buffer shorter than subpacket gpg: signature packet without keyid gpg: buffer shorter than subpacket gpg: buffer shorter than subpacket gpg: buffer shorter than subpacket gpg: signature packet without keyid gpg: buffer shorter than subpacket ==10542== Invalid read of size 4 ==10542== at 0x56016B0: _gcry_mpi_normalize.part.0 (mpi-bit.c:61) ==10542== by 0x560173F: _gcry_mpi_normalize (mpi-bit.c:75) ==10542== by 0x560173F: _gcry_mpi_get_nbits (mpi-bit.c:79) ==10542== by 0x429D5D: encode_md_value (seskey.c:350) ==10542== by 0x43F4AD: check_signature_end_simple (sig-check.c:461) ==10542== by 0x44000E: check_signature_over_key_or_uid (sig-check.c:892) ==10542== by 0x4406EF: check_key_signature2 (sig-check.c:1075) ==10542== by 0x440784: check_key_signature (sig-check.c:686) ==10542== by 0x429601: keyring_rebuild_cache (keyring.c:1554) ==10542== by 0x426293: keydb_rebuild_caches (keydb.c:1775) ==10542== by 0x46FD8E: validate_keys (trustdb.c:1904) ==10542== by 0x444BB7: public_key_list (keylist.c:133) ==10542== by 0x40B661: main (gpg.c:4100) ==10542== Address 0x4 is not stack'd, malloc'd or (recently) free'd ==10542== gpg: signal Segmentation fault caught ... exiting ==10542== ==10542== Process terminating with default action of signal 11 (SIGSEGV) ==10542== at 0x5EEA908: raise (in /lib64/libc-2.23.so) ==10542== by 0x5EEA98F: ??? (in /lib64/libc-2.23.so) ==10542== by 0x56016AF: ??? (in /usr/lib64/libgcrypt.so.20.0.5) ==10542== by 0x560173F: _gcry_mpi_normalize (mpi-bit.c:75) ==10542== by 0x560173F: _gcry_mpi_get_nbits (mpi-bit.c:79) ==10542== by 0x429D5D: encode_md_value (seskey.c:350) ==10542== by 0x43F4AD: check_signature_end_simple (sig-check.c:461) ==10542== by 0x44000E: check_signature_over_key_or_uid (sig-check.c:892) ==10542== by 0x4406EF: check_key_signature2 (sig-check.c:1075) ==10542== by 0x440784: check_key_signature (sig-check.c:686) ==10542== by 0x429601: keyring_rebuild_cache (keyring.c:1554) ==10542== by 0x426293: keydb_rebuild_caches (keydb.c:1775) ==10542== by 0x46FD8E: validate_keys (trustdb.c:1904) ==10542== ==10542== HEAP SUMMARY: ==10542== in use at exit: 3,965,558 bytes in 57,887 blocks ==10542== total heap usage: 140,986 allocs, 83,099 frees, 32,966,576 bytes allocated ==10542== ==10542== LEAK SUMMARY: ==10542== definitely lost: 42 bytes in 2 blocks ==10542== indirectly lost: 0 bytes in 0 blocks ==10542== possibly lost: 0 bytes in 0 blocks ==10542== still reachable: 3,965,516 bytes in 57,885 blocks ==10542== suppressed: 0 bytes in 0 blocks ==10542== Rerun with --leak-check=full to see details of leaked memory ==10542== ==10542== For counts of detected and suppressed errors, rerun with: -v ==10542== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Speicherzugriffsfehler (Speicherabzug geschrieben) Note, that the crash doesn't occur if I delete .gnupg/trustdb.gpg but as soon as I modify the trust level of any key gpg crashes again. -- You are receiving this mail because: You are on the CC list for the bug.