Hello.
I can confirm this calf GUI crash with the latest Debian
buster/testing packages (ardour 5.10.0~dfsg-1 and latest calf-plugins
and calf-ladspa). The same symptoms appeared as mentioned previously
where the calf plugin can be added to my Ardour session (ie. Calf
Equalizer 30 Band (LV2))
Hello.
Since upstream renamed all the include paths from 'tsk3' to 'tsk since
v4.1.0, would it work to rename libtsk-dev to libtsk3-3-dev so that it
remains with the other libtsk3-3 libraries, and libtsk-dev becomes the
new standard following the v4.x upstream? libtsk3-3-dev can continue
to
For those of you experiencing this bug I've run into a similar
situation with udev + lvm + cryptsetup/LUKS in that any of my newly
generated initramfs images fail to boot my system as they just spin
after entering either a valid or invalid cryptsetup passphrase. A
blank passphrase returns to the
On Fri, Oct 31, 2008 at 4:35 AM, Loïc Minier [EMAIL PROTECTED] wrote:
On Fri, Oct 31, 2008, Loïc Minier wrote:
Actually I dropped that part when rewriting the init script; any idea
what could set MODPROBE_OPTIONS for you?
Could you either try the attached module-init-tools patch, or
On Thu, Oct 30, 2008 at 3:29 AM, Loïc Minier [EMAIL PROTECTED] wrote:
Hi Derrick,
Could you please edit /etc/init.d/acpid as root, and change the
set -e into:
set -e
set -x
initlogfile=$(mktemp -t acpid.init.)
exec 2$initlogfile
This will record the execution of
On Fri, Oct 24, 2008 at 2:57 AM, Michael Meskes [EMAIL PROTECTED] wrote:
On Fri, Oct 24, 2008 at 10:19:55AM +0200, Loïc Minier wrote:
On Fri, Oct 24, 2008, Michael Meskes wrote:
if [ $MODULES ]; then
modprobe --all --use-blacklist $MODULES 2/dev/null
fi
Err you probably lack a -n
On Thu, Oct 23, 2008 at 2:10 AM, Michael Meskes [EMAIL PROTECTED] wrote:
On Wed, Oct 22, 2008 at 04:11:48PM -0600, Derrick Karpo wrote:
Along with the 'set -x' I also added logging statements before and
after the modprobe in /etc/init.d/acpid. modprobe is called correctly
and $MODULES
On Tue, Oct 21, 2008 at 3:51 AM, Loïc Minier [EMAIL PROTECTED] wrote:
On Mon, Oct 20, 2008, Derrick Karpo wrote:
I can confirm this same behaviour under 2.6.17.1 (amd64). With ACPI
compiled into the kernel acpid fails to start on boot however when
ACPI is compiled in as modules then acpid
Hello.
I can confirm this same behaviour under 2.6.17.1 (amd64). With ACPI
compiled into the kernel acpid fails to start on boot however when
ACPI is compiled in as modules then acpid starts correctly. In my
case, ACPI also started correctly with the stock Debian
linux-image-2.6.26-1-amd64
Hi Rene.
On Wed, Apr 9, 2008 at 12:40 AM, Rene Engelhard [EMAIL PROTECTED] wrote:
Hi,
Derrick Karpo wrote:
Frank, can you please confirm that you have 'openoffice.org'
installed? I was able to reproduce this bug on sid and the problem
occurred when 'openoffice.org
Hello.
Frank, can you please confirm that you have 'openoffice.org'
installed? I was able to reproduce this bug on sid and the problem
occurred when 'openoffice.org' was not installed. Without this
package, openoffice would fail with a javaldx: Could not find a Java
Runtime Environment! message
Package: freeradius
Version: 1.0.2-4
When /etc/init.d/freeradius is called without any arguments it errors
with /etc/init.d/freeradius: line 42: $1: unbound variable. This is
due to the 'set -u' in the script.
Attached is a patch which replaces 'set -u' with 'set -e' and also
does some minor
12 matches
Mail list logo
