From: Shelagh M. <on...@tp...> - 2006-02-26 02:51:26
|
On Fri, 24 Feb 2006 10:56:20 -0500, D. Michael 'Silvan' McIntyre wrote: > On Friday 24 February 2006 10:27 am, Hector Centeno-Garcia wrote: >> Sorry. Here it is: >> >> (gdb) bt >> #0 0xb5a197d2 in ?? () >> #1 0xb7e11218 in __nptl_deallocate_tsd () >> from /lib/tls/i686/cmov/libpthread.so.0 >> #2 0xb7e1136f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 >> #3 0xb6a59bde in clone () from /lib/tls/i686/cmov/libc.so.6 > > Urk. > > I wonder what would happen if you tried --nofork, which I think stops it from > threading. > > That's just wild speculation. We clearly have a problem I couldn't begin to > imagine how to fix. > > Chris? Guillaume? This is what he's getting when running "rosegarden" > normally. GUI dies, leaving the sequencer up. GUI runs fine if started with > no sequencer and --nosequencer option. He can't seem to get them both > working at the same time. > > Punt. Sorry to but into this thread, but I also have been having the same difficulties with rosegarden4-1.2.3. on Ubuntu Breezy. Compiles like a dream, crashes every time I try to open it. Tried compiling with debug=full and so on, but have no confidence that I have not done something utterly stupid elsewhere on my system that could be interfering. Just thought I'd tell you that getting rid of whysynth, as you suggested, seems to do the trick. One or two odd things to note, In settings -> configure rosegarden -> sequencer It says I have no driver. I assume that means something is odd with the alsa driver? Please let me know if you want more details. Shelagh |