Re: [LAU] qtractor crashes (was: the defacto host for lv2)

One possibility is that totally independent of Qtractor, an installed faulty ladspa calf plugin is messing things up... I've removed the offending "ladspa-calf-plugins.x86_64 0.0.18.5-3.fc12." (Perhaps this is ultimately the plugin that was causing the other errors I was seeing when browsing different plugin dirs in qtractor, earlier?) Is there any way of isolating a plugin host from faulty plugins like this? Especially when they're just there and not even being used. I will see (and follow up on) whether qtractor ends up working more stably without the bad plugin. Removing the plugin stops rosegarden from crashing, for example: https://bugzilla.redhat.com/show_bug.cgi?id=600713#c4 (thanks to Orcan Ogetbil for the suggestion https://bugzilla.redhat.com/show_bug.cgi?id=600713#c3 ): ....................... Indeed, after removing ladspa-calf-plugins, it [rosegarden] now quits with a warning, but doesn't coredump. I will await update of this package. Thanks for letting me know of this interaction, especially on a plugin I'm not using but is just "sitting" in the directory. That level of sensitivity to faulty plugins is therefore the bug for this particular crash. It'll be interesting if that also clears up the qtractor issues also pointing towards memory corruption, which happen infrequently. gnulem-125-~/Documents> sudo yum remove ladspa-calf-plugins.x86_64 [...] Removed: ladspa-calf-plugins.x86_64 0:0.0.18.5-3.fc12 Dependency Removed: lmms.x86_64 0:0.4.6-2.fc12 Complete! gnulem-126-~/Documents> rosegarden [...] QMainWindow::saveState(): 'objectName' not set for QDockWidget 0x32efa30 'Special Parameters; RosegardenSequencer::quit() Warning: Composition::~Composition() with 3 observers still extant Observers are: 0x33b97c0 [N10Rosegarden19SegmentParameterBoxE] 0x340eec0 [N10Rosegarden17TrackParameterBoxE] 0x38aef30 [N10Rosegarden20CompositionModelImplE] ................. Niels http://nielsmayer.com