Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Package: ncmpcpp Version: 0.7.4-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, ncmpcpp is not able to start at all. any attempt to start results into this: bash$ ncmpcpp ncmpcpp: symbol lookup error: ncmpcpp: undefined symbol: _ZN6TagLib6String14WCharByteOrderE I tried to check what is missing: bash$ echo _ZN6TagLib6String14WCharByteOrderE|c++filt TagLib::String::WCharByteOrder though it looks like taglib is available in my system: bash$ dpkg -l | grep libtag ii libtag-extras1 1.0.1-3+b1 amd64TagLib extras library - support for more file formats ii libtag1v5:amd641.11+dfsg.1-0.1amd64audio meta-data library ii libtag1v5-vanilla:amd641.11+dfsg.1-0.1amd64audio meta-data library - vanilla flavour ii libtaglib-ocaml0.3.1-1+b3 amd64OCaml bindings for the TagLib Audio Meta-Data Library ldd also shows, that all dependencies are in place: bash$ ldd /usr/bin/ncmpcpp linux-vdso.so.1 (0x7ffdcdfc5000) libboost_filesystem.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.61.0 (0x7f44a026) libboost_system.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.61.0 (0x7f44a005c000) libboost_locale.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_locale.so.1.61.0 (0x7f449fd71000) libboost_program_options.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.61.0 (0x7f449faf2000) libboost_regex.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.61.0 (0x7f449f7da000) libicuuc.so.57 => /usr/lib/x86_64-linux-gnu/libicuuc.so.57 (0x7f449f43) libicudata.so.57 => /usr/lib/x86_64-linux-gnu/libicudata.so.57 (0x7f449d9b3000) libboost_thread.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.61.0 (0x7f449d78b000) libmpdclient.so.2 => /usr/lib/libmpdclient.so.2 (0x7f449d574000) libreadline.so.6 => /lib/x86_64-linux-gnu/libreadline.so.6 (0x7f449d32a000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f449d10d000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f449cedb000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f449ccb1000) libfftw3.so.3 => /usr/lib/x86_64-linux-gnu/libfftw3.so.3 (0x7f449c8b4000) libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x7f449c63a000) libtag.so.1 => /usr/lib/x86_64-linux-gnu/libtag.so.1 (0x7f449c357000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f449bfd6000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f449bcd) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f449bab9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f449b71b000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f449b513000) libboost_chrono.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.61.0 (0x7f449b30c000) libicui18n.so.57 => /usr/lib/x86_64-linux-gnu/libicui18n.so.57 (0x7f449ae92000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f449ac8c000) /lib64/ld-linux-x86-64.so.2 (0x55964ec77000) libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 (0x7f449aa66000) libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x7f449a832000) librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 (0x7f449a615000) libssh2.so.1 => /usr/lib/x86_64-linux-gnu/libssh2.so.1 (0x7f449a3e9000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7f449a1b) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7f4499e4e000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7f4499c03000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7f449992b000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7f44996fb000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7f44994f7000) liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x7f44992e6000) libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x7f4499095000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4498e7a000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7f4498c45000) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f44989c2000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f44986b1000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7f449844c000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7f4498239000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7f449802d000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7f4497e29000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f4497c12000) libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x7f4
Bug#648319:
Hey, guys, just adding symlink doesn't resolve the issue.
You can find string
: ${BASH_COMPLETION_COMPAT_DIR:=/etc/bash_completion.d}
in /usr/share/bash-completion/bash_completion file.
Therefore most of completions do not working.
Just changing it to /usr/share/bash-completion/completions also break
completions, that left in /etc/bash_completion.d. But most of them
already are in new place.
So we are should wait, while all developers will move it from old
destination to new.
But it would be better to change string with COMPAT_DIR variable. Here is patch:
--- /usr/share/bash-completion/bash_completion_broken 2012-01-11
11:34:13.534680333 +0400
+++ /usr/share/bash-completion/bash_completion 2012-01-11
11:34:04.618636189 +0400
@@ -40,7 +40,7 @@
# Set the following to the location of the backwards compat completion dir.
#
-: ${BASH_COMPLETION_COMPAT_DIR:=/etc/bash_completion.d}
+: ${BASH_COMPLETION_COMPAT_DIR:=/usr/share/bash-completion/completions}
readonly BASH_COMPLETION_COMPAT_DIR
# Blacklisted completions, causing problems with our code.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648319: bash-completion: /etc/bash_completion script doesn't do the job
Sorry again, just missed all others in CC. 2012/1/11, Jonathan Nieder : > > Please use a subject line. Often, preserving the subject > line of the message you are replying to is enough. > Oh, I'm sorry. > I don't follow. Isn't COMPAT_DIR _supposed_ to point to > /etc/bash_completion.d? Which completion is not working? If I specify /etc/bash_completion.d in this variable noone from /usr/share/bash-completion/completions/ will work. I tested on ssh, ip, apt-get, aptitude and others (nothing happens on TAB [[only dirs suggested for completion]]). After changing it to /usr/share/bash-completion/completions/ it works well. But there are some comletions left in old dir. They do not work in this case. $ ls /etc/bash_completion.d/ apache2.2-common desktop-file-validate dpatch_edit_patch git initramfs-tools m-a openvpn rinse apt-file devscripts.chdist dput grub insserv mpc pon vim-addon-manager debconf devscripts.pkgnamesduploadhelpers libreoffice.sh ncmpcpp quilt PS. And yes, I've restarted shell every time after I changed /usr/share/bash-completion/bash_completion . Best regards, Rush. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#1054744:
Hacked
