Your message dated Mon, 27 Mar 2017 08:40:26 -0400
with message-id
<canyoob3wser8sydrbjk64-j3zwsz0abrscvdyiwrgbtvfmh...@mail.gmail.com>
and subject line Re: Bug#858030: Acknowledgement (mutt: relocation error in
libgpgme.so.11)
has caused the Debian Bug report #858030,
regarding mutt: relocation error in libgpgme.so.11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
858030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858030
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.8.0-1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Maintainer,
When I try to start mutt, I get the following error:
$ mutt
mutt: relocation error: mutt: symbol gpgme_get_ctx_flag, version
GPGME_1.1 not defined in file libgpgme.so.11 with link time reference
- -- Package-specific info:
- -- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mutt depends on:
ii libassuan0 2.4.3-2
ii libc6 2.24-9
ii libcomerr2 1.43.4-2
ii libgnutls30 3.5.8-5
ii libgpg-error0 1.26-2
ii libgpgme11 1.8.0-3+b2
ii libgssapi-krb5-2 1.15-1
ii libidn11 1.33-1
ii libk5crypto3 1.15-1
ii libkrb5-3 1.15-1
ii libncursesw5 6.0+20161126-1
ii libnotmuch4 0.23.7-1
ii libsasl2-2 2.1.27~101-g0780600+dfsg-2
ii libtinfo5 6.0+20161126-1
ii libtokyocabinet9 1.4.48-11+b1
Versions of packages mutt recommends:
ii libsasl2-modules 2.1.27~101-g0780600+dfsg-2
ii locales 2.24-9
ii mime-support 3.60
Versions of packages mutt suggests:
ii aspell 0.60.7~20110707-3+b2
ii ca-certificates 20161130
ii exim4-daemon-heavy [mail-transport-agent] 4.89-1
ii gnupg 2.1.18-6
ii ispell 3.4.00-5
ii mixmaster 3.0.0-8.1
ii openssl 1.1.0e-1
ii urlview 0.9-20+b1
Versions of packages mutt is related to:
ii mutt 1.8.0-1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEAREIAB0WIQT5xLt2Dng/DewQpoprjrOgZc+6qQUCWMvy8wAKCRBrjrOgZc+6
qZnTAQCAVZtcB19iyilQarFOJKxXl2DZVxG9z0j884X0UuRAUAD7BcjzV4N0FJKp
F1yJDuruOQRle4tPqzEbQXNVTHi/CoCIdQQBFggAHRYhBO7QFYAT3C5tbgAepDe5
UHrP8gFuBQJYy/LzAAoJEDe5UHrP8gFupWsA/1p8BjP4eOa2NprpZs6bblqsw0xE
YtYxfMCC5Bk43vh3AP9Xu5zn+99opWA+qKU3pa33ZgaoO27mHkylwOTox3boBw==
=RZI0
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I realized I had an extra libgpgme.so.11 sitting around in
/usr/local/lib. Once I removed it, mutt worked fine. This bug report
may be closed.
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQTu0BWAE9wubW4AHqQ3uVB6z/IBbgUCWNkIFgAKCRA3uVB6z/IB
bpXOAP9TSOF6k0QZ7NYEBavzA3JvjG2/AwzoLHY7O7wiYqroPwEAxMVZU9L1kT6a
1Fr+Aup2ZfZhytegW3XzZINKhdPCMA+IdQQBEQgAHRYhBPnEu3YOeD8N7BCmimuO
s6Blz7qpBQJY2QgyAAoJEGuOs6Blz7qpLu8A/jz8g4XoIcMA1rGLdMBGsM5+dM9Y
oOgyASaJb/jy/aqAAP0bkqPz0B3RcqscF2moVxDhamO9lwA31wJ1qvmtW1p5MA==
=tfxg
-----END PGP SIGNATURE-----
--- End Message ---
