Your message dated Fri, 21 Aug 2020 22:15:53 -0400
with message-id <20200822021553.d7k2pqzahdep3k6n@localhost>
and subject line Re: Bug#968747: vim-gtk3: vim (when linked to vim-gtk3 or
vim-nox) fails to start due to undefined symbol
has caused the Debian Bug report #968747,
regarding vim-gtk3: vim (when linked to vim-gtk3 or vim-nox) fails to start due
to undefined symbol
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 ow...@bugs.debian.org
immediately.)
--
968747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vim-gtk3
Version: 2:8.2.0716-3
Severity: grave
Justification: renders package unusable
After dist-upgrading Debian testing to bullseye/sid, vim/ex/gvim/etc. no longer
started:
vim: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0:
undefined symbol: XML_SetHashSalt
A check shows that this only affects vim.gtk3 and vim.nox; vim.basic works
fine.
-- Package-specific info:
--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk3
/usr/bin/vim is /usr/bin/vim.gtk3
/usr/bin/gvim is /usr/bin/vim.gtk3
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vim-gtk3 depends on:
ii libacl1 2.2.53-8
ii libc6 2.31-3
ii libcairo2 1.16.0-4
ii libcanberra0 0.30-7
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii libglib2.0-0 2.64.4-1
ii libgpm2 1.20.7-6
ii libgtk-3-0 3.24.22-1
ii libice6 2:1.0.9-2
ii liblua5.2-0 5.2.4-1.1+b3
ii libpango-1.0-0 1.46.0-2
ii libpangocairo-1.0-0 1.46.0-2
ii libperl5.30 5.30.3-4
ii libpython3.8 3.8.5-2
ii libruby2.7 2.7.1-3
ii libselinux1 3.1-2
ii libsm6 2:1.2.3-1
ii libtcl8.6 8.6.10+dfsg-1
ii libtinfo6 6.2-1
ii libx11-6 2:1.6.10-3
ii libxt6 1:1.1.5-1+b3
ii vim-common 2:8.2.0716-3
ii vim-gui-common 2:8.2.0716-3
ii vim-runtime 2:8.2.0716-3
vim-gtk3 recommends no packages.
Versions of packages vim-gtk3 suggests:
ii cscope 15.9-1
ii fonts-dejavu 2.37-2
ii gnome-icon-theme 3.12.0-3
ii vim-doc 2:8.2.0716-3
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Aug 20, 2020 at 09:24:01PM +0200, Tim Van Holder wrote:
> After dist-upgrading Debian testing to bullseye/sid, vim/ex/gvim/etc. no
> longer
> started:
>
> vim: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0:
> undefined symbol: XML_SetHashSalt
While trying to load libpython3.8.so.1.0, which requires libexpat.so.1,
it couldn't resolve expat's XML_SetHashSalt symbol. This suggests you
either have a broken libexpat1 package installed or a version of it
that's not built by Debian.
"ldd /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0 | grep expat" should
show which libexpat is being loaded. It should also be in
/usr/lib/x86_64-linux-gnu.
> A check shows that this only affects vim.gtk3 and vim.nox; vim.basic works
> fine.
That's because vim.basic doesn't include the language interpreters.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
