Public bug reported:
Binary package hint: ardour
I'm running the latest karmic as of this writing (17-Oct-2009), and I'm
using the 2.6.31-9-rt kernel.
I launch ardour using the command "chrt 69 ardour2" to ensure it gets
enough attention from the system. This worked flawlessly in Jaunty (with
a custom-compiled kernel, though), but in Karmic I get:
---
$ chrt 69 ardour2
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs
out of memory. You can view the memory limit with 'ulimit -l', and it
is normally controlled by /etc/security/limits.conf
Ardour/GTK 2.8.2
(built using 5396 and GCC version 4.4.1)
Copyright (C) 1999-2008 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker
Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/pablo/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/pablo/.ardour2/ardour.rc
ardour: [INFO]: No H/W specific optimizations in use
GThread-ERROR **: file /build/buildd/glib2.0-2.22.2/gthread/gthread-posix.c:
line 348 (g_thread_create_posix_impl): error 'Invalid argument' during
'pthread_attr_setschedparam (&attr, &sched)'
aborting...
Aborted (core dumped)
---
This doesn't happen if I execute "ardour2" and then "chrt -p 69 $(pidof
ardour-2.8.2)", so I guess that it is only at startup that Ardour's
scheduling policy/priority is checked by glib.
I guess the problem is really in glib, so I'll add it to the package
list. I will recheck with the non-rt kernel to see what happens there.
For the record, I'm also running jackd at a priority of 75, hydrogen
(compiled from svn) at a priority of 69, and have increased the priority
of the soundcard and rtc0 interrupts to 85 and 98, respectively [all of
these with policy SCHED_RR].
ProblemType: Bug
Architecture: amd64
Date: Sat Oct 17 13:07:06 2009
DistroRelease: Ubuntu 9.10
Package: ardour 1:2.8.2-0ubuntu1
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SourcePackage: ardour
Uname: Linux 2.6.31-9-rt x86_64
XsessionErrors:
(gnome-settings-daemon:2810): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(gnome-settings-daemon:2810): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(polkit-gnome-authentication-agent-1:2928): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:2916): Eel-CRITICAL **: eel_preferences_get_boolean: assertion
`preferences_is_initialized ()' failed
(gnome-panel:2913): Gdk-WARNING **:
/build/buildd/gtk+2.0-2.18.2/gdk/x11/gdkdrawable-x11.c:952 drawable is not a
pixmap or window
** Affects: ardour (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug
--
ardour crashes if launched with chrt
https://bugs.launchpad.net/bugs/453898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
