slgui output with jack running, but no engine running yet: [EMAIL PROTECTED]:~$ slgui slgui: our URL is osc.udp://cheese:10400/ execing: 'sooperlooper -q -U osc.udp://cheese:10400/ -p 9951 -l 1 -c 2 -t 40 -m "/home/roger/.sooperlooper/default_midi.slb"'
slgui: spawned new engine slgui: gave up on spawned engine Only part of GUI is rendered at the "spawned new engine" point and after a short delay, the "gave up" line appears with a GUI message box: "No response from sooperlooper engine process. Please make sure the JACK server is running. Also check that the system's hostname resolves correctly" The slgui output is the same with a sooperlooper engine running already, but I think this is because slgui crashes the existing one before trying to start a new one and crashing that one too. Output of gdb slgui has one extra line of interest; (gdb) run Starting program: /usr/bin/slgui (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1220606256 (LWP 17898)] (no debugging symbols found) (no debugging symbols found) ---snip--- (no debugging symbols found) (no debugging symbols found) slgui: our URL is osc.udp://cheese:10785/ [New Thread -1222669424 (LWP 17907)] execing: 'sooperlooper -q -U osc.udp://cheese:10785/ -p 9951 -l 1 -c 2 -t 40 -m "/home/roger/.sooperlooper/default_midi.slb"' slgui: spawned new engine OSC thread poll failed: Interrupted system call slgui: gave up on spawned engine I couldn't turn up any clues about that extra line, it seems to be an effect of the engine segfault rather than a cause. -- Sooperlooper segfaults when launched from slgui https://bugs.launchpad.net/bugs/115152 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
