Your message dated Fri, 11 Nov 2022 10:12:21 +0100
with message-id <[email protected]>
and subject line Re: ardour: Ardour won't start
has caused the Debian Bug report #1023839,
regarding ardour: Ardour won't start
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.)
--
1023839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023839
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ardour
Version: 1:7.0.0+ds0-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: [email protected]
Ardour doesn't start
/usr/lib/ardour7/ardour-7.0.0~ds0: symbol lookup error:
/usr/lib/ardour7/libardour.so.3: undefined symbol:
_ZNK10RubberBand19RubberBandStretcher20getPreferredStartPadEv
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-2-rt-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ardour depends on:
ii ardour-data 1:7.0.0+ds0-3
ii ardour-lv2-plugins 1:7.0.0+ds0-3
ii libarchive13 3.6.0-1
ii libasound2 1.2.7.2-1
ii libatkmm-1.6-1v5 2.28.3-1
ii libaubio5 0.4.9-4.2+b1
ii libc6 2.36-4
ii libcairo2 1.16.0-6
ii libcairomm-1.0-1v5 1.14.4-1
ii libcurl3-gnutls 7.86.0-1
ii libcwiid1 0.6.91-4
ii libdbus-1-3 1.14.4-1
ii libfftw3-single3 3.3.8-2
ii libfluidsynth3 2.3.0-1+b1
ii libfontconfig1 2.13.1-4.5
ii libgcc-s1 12.2.0-9
ii libgdk-pixbuf-2.0-0 2.42.9+dfsg-1
ii libglib2.0-0 2.74.1-1
ii libglibmm-2.4-1v5 2.66.5-1
ii libgtk2.0-0 2.24.33-2
ii libgtkmm-2.4-1v5 1:2.24.5-4+b1
ii liblilv-0-0 0.24.14-1
ii liblo7 0.31-1
ii liblrdf0 0.6.1-3
ii libltc11 1.3.2-1
ii libpango-1.0-0 1.50.10+ds-1
ii libpangocairo-1.0-0 1.50.10+ds-1
ii libpangoft2-1.0-0 1.50.10+ds-1
ii libpangomm-1.4-1v5 2.46.3-1
ii libpulse0 16.1+dfsg1-2+b1
ii libqm-dsp0 1.7.1-5
ii libreadline8 8.2-1.1
ii librubberband2 1:2.0.2-dmo1
ii libsamplerate0 0.2.2-2
ii libsigc++-2.0-0v5 2.10.8-1
ii libsndfile1 1.1.0-3+b1
ii libstdc++6 12.2.0-9
ii libsuil-0-0 1:0.10.10-dmo1
ii libtag1v5 1.13-1
ii libusb-1.0-0 2:1.0.26-1
ii libvamp-hostsdk3v5 1:2.10.0-dmo1
ii libvamp-sdk2v5 1:2.10.0-dmo1
ii libwebsockets17 4.1.6-3
ii libx11-6 2:1.8.1-2
ii libxml2 2.9.14+dfsg-1+b1
Versions of packages ardour recommends:
ii ardour-video-timeline 1:7.0.0+ds0-3
ardour suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
hi.
thanks for your bug-report.
On Fri, 11 Nov 2022 08:31:39 +0100 raffaele morelli
<[email protected]> wrote:
Package: ardour
Version: 1:7.0.0+ds0-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: [email protected]
Ardour doesn't start
[...]
Versions of packages ardour depends on:
ii librubberband2 1:2.0.2-dmo1
it seems you have enabled the deb-multimedia package repository, which
is explicitely unsupported by Debian (see [1] for the reason why it
breaks in your case).
once you have removed all deb-multimedia packages and migrated to the
package versions provided by Debian, things will start to work again.
gdsamr
IOhannes
[1] https://wiki.debian.org/DebianMultimedia/FAQ#versioning
--- End Message ---
