The problem is that glib is failing to start a thread with the scheduling priority of the parent thread. In particular, eglibc is reporting that the requested priority is out of range. So something somewhere is deciding that I am not allowed to set the real-time priority of a thread, which is obviously wrong since I was allowed to launch the process with a modified priority in the first place.
I've tried qt applications (hydrogen and kdenlive, both likely to be multithreaded) and there is no problem with them. So although I may as well be blaming the messenger, there is a good chance that it's GNOME's libraries that are at fault here. -- glib2.0 crashes when applications are started 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
