Checked that it happens also with kernel 2.6.31-14-generic.
Also, I've found out that this happens with many other GTK applications, presumably those which are threaded (nautilus, rhythmbox, totem, etc), and non-threaded ones (gcacl-tool, same-gnome, gnome-terminal, etc) are not affected.
So this has nothing to do with ardour at all. I've reassigned the bug to glib2.0. I'll update the description too.
Furthermore, it appears that the issue is with non-zero priorities. SCHED_IDLE|OTHER|BATCH do not accept non-zero priorities, so they work fine:
---
$ chrt -i 0 totem
$ chrt -o 0 totem
$ chrt -b 0 totem
---
however SCHED_FIFO|RR only accept non-zero priorites, and they fail to run:
---
$ chrt -f 50 totem
Checked that it happens also with kernel 2.6.31-14-generic.
Also, I've found out that this happens with many other GTK applications, presumably those which are threaded (nautilus, rhythmbox, totem, etc), and non-threaded ones (gcacl-tool, same-gnome, gnome-terminal, etc) are not affected.
So this has nothing to do with ardour at all. I've reassigned the bug to glib2.0. I'll update the description too.
Furthermore, it appears that the issue is with non-zero priorities. SCHED_IDLE| OTHER|BATCH do not accept non-zero priorities, so they work fine:
---
$ chrt -i 0 totem
$ chrt -o 0 totem
$ chrt -b 0 totem
---
however SCHED_FIFO|RR only accept non-zero priorites, and they fail to run:
---
$ chrt -f 50 totem
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_setschedpa ram (&attr, &sched)'
aborting...
Aborted (core dumped)
$ chrt -r 50 totem
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_setschedpa ram (&attr, &sched)'
aborting...
Aborted (core dumped)
---
Unrelated Launchpad question: how does one add (rather than replace) an affected package in a bug?