Just realized my report was a bit unclear. Upstream does not have this bug.
It's the debian packaging that creates it, by moving libalsapid.so away from
/usr/lib.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.de
Package: ladish
Version: 0.3-9ubuntu0danmppa2~lucid1
Severity: important
Tags: patch
ladish from Sid installs libalsapid.so into /usr/lib/ladish, away from
/usr/lib where ladish assumes it to be. As a result ladish cannot preload
this library when executing apps, and some ALSA MIDI ports do not
Package: ladish
Version: 0.3-4ubuntu0danmppa1
Severity: normal
Tags: patch
ladish defaults to using xterm as a a terminal emulator (which may not even
be installed). In Debian, it's best to use x-terminal-emulator, which
reflects the user's choice.
-- System Information:
Debian Release: squeez
Package: ladish
Version: 0.3-4
Severity: normal
Tags: patch
Ladish tries to start terminal-bound commands as -e 'command
args'. In general, "x-terminal-emulator -e" expects an executable +
arguments, NOT a command string, as daemon/loader.c provides. The attached
(if trivial) patch fixes that
Package: jack-keyboard
Version: 2.5-2
Severity: normal
Tags: patch
Per the manual page, jack-keyboard should pass through incoming MIDI
messages but replace the channel number with its own. It only recognizes
incoming messages sent on MIDI channel 0 however, and does not rewrite
the channel at al
Package: lv2core
Version: 4.0-5
Severity: normal
Tags: patch
This is a bug against the SOURCE package from Debian Sid so my distribution
is irrelevant.
When building lv2core-4.0-5 from sid, I noticed a warning about snprintf
being guaranteed to overflow in write_text. The problem seems to be t
