Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as Won't Fix.
** Changed in: sooperlooper (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unable to reproduce on Lucid.
** Changed in: sooperlooper (Ubuntu)
Status: Confirmed = Fix Released
** Also affects: sooperlooper (Ubuntu Karmic)
Importance: Undecided
Status: New
--
Sooperlooper segfaults when launched from slgui
https://bugs.launchpad.net/bugs/115152
You
Hi again,
Sorry but I forgot to mention that the segfault I've experienced in
v1.6.3 was due to missing libalsa during compile time, causing a missing
- and unchecked - MIDI handle to segfault. Now I'm pretty sure that my
problem wasn't related to Rog's segfault.
@Rog (initial reporter?)
I've
I've no idea about this, but I'm not sure what other information would
be useful to address it. I still can't replicate it.
** Changed in: sooperlooper (Ubuntu)
Assignee: Emmet Hikory (persia) = (unassigned)
Status: Incomplete = Confirmed
--
Sooperlooper segfaults when launched
I'm facing a similar problem with self-compiled sooperlooper v1.6.2 - it really
seems that the engine is segfaulting.
Has anyone found any solution to this, yet?
--
Sooperlooper segfaults when launched from slgui
https://bugs.launchpad.net/bugs/115152
You received this bug notification because
I've recompiled sooperlooper v1.6.3 with debugging symbols and it seems that
mine is segfaulting in SooperLooper::MidiBridge.
Here's gdb's output:
0x08081c54 in SooperLooper::MidiBridge::get_current_host_time (this=0x0) at
midi_bridge.cpp:909
909 if (_port) {
Walking up the stack
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
Thanks for the additional information. I do wish I could replicate it
locally. Could you please post the output of running slgui from the
command line to show the crash? I'm curious at which point it crashes.
** Changed in: sooperlooper (Ubuntu)
Importance: Undecided = Low
Assignee:
I had another go at using sooperlooper today, and it turns out that my
workaround just delays the problem. Starting up sooperlooper from the
command line with no arguments works fine, but as soon as I start slgui
on a separate command line, the engine segfaults and slgui tries to
spawn its own
Addressing your comments in reverse order: the -U option is used to
connect the sooperlooper engine to an extant slgui session for OSC
control. I'm not sure why it's undocumented, and it probably shouldn't
segfault when it fails, but that's somewhat expected behaviour (although
still a bug).
As
10 matches
Mail list logo
