#109 Seg Fault on openSuse 11.2

v0.5
open
None
6
2009-12-17
2009-12-16
No

OpenSuse 11.2, installed 0.5.0 from the repositories, also installing bsl.
System Architecture: AM2+ 64-bit
Segfault when trying to enter dtmfsrc or memoryaudiosrc or sfsrc pattern editor (It only shows the digits from 0000-000F where usually the "ticks" column should be, but without a title.)

Couple of errors with fluidsynth:
fluidsynth: error: Unable to open file "/usr/share/doc/libfluidsynth-dev/examples/example.sf2"
fluidsynth: error: Couldn't load soundfont file
fluidsynth: error: Failed to load SoundFont "/usr/share/doc/libfluidsynth-dev/examples/example.sf2"
fluidsynth: error: Unable to open file "/usr/share/sounds/sf2/Vintage_Dreams_Waves_v2.sf2"
fluidsynth: error: Couldn't load soundfont file
fluidsynth: error: Failed to load SoundFont "/usr/share/sounds/sf2/Vintage_Dreams_Waves_v2.sf2"
fluidsynth: error: Unable to open file "/home/jonas/sbks/synth/FlangerSaw.SF2"
fluidsynth: error: Couldn't load soundfont file
fluidsynth: error: Failed to load SoundFont "/home/jonas/sbks/synth/FlangerSaw.SF2"

hopin you can fix it, Davey
PS: If you need any more debug info/me testing out something, send me a mail at Davey.Jones@gmx.de. Best wishes, Davey

Discussion

  • Jonas Oberhauser

    • milestone: --> v0.5
    • priority: 5 --> 6
     
  • Stefan Sauer

    Stefan Sauer - 2009-12-17
    • assigned_to: nobody --> ensonic
     
  • Stefan Sauer

    Stefan Sauer - 2009-12-17

    Thanks for the report. Some of the shown plugins are not useful to be used as a source. I will think of a way to blacklist some (e.g. memoryaudiosrc). I don't get any crashes with the latest svn. It would be great if you could try running your installed version as below and attach the output here:

    > gdb buzztard-edit
    run
    ...
    (make it crash :) )
    bt
    0 ...
    1 ...
    (send me that backtrace)

    if you have further questions, we could also use IRC (#buzztard or irc.freenode.net) if that suits you.

     
  • Jonas Oberhauser

    here is the backtrace:

    #0 0x000000000044f4f6 in bt_pattern_editor_refresh_cursor ()
    #1 0x000000000044fb38 in bt_pattern_editor_button_press ()
    #2 0x00007ffff74cf7c8 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0
    #3 0x00007ffff34c168e in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0
    #4 0x00007ffff34d667d in ?? () from /usr/lib64/libgobject-2.0.so.0
    #5 0x00007ffff34d7bfc in g_signal_emit_valist () from /usr/lib64/libgobject-2.0.so.0
    #6 0x00007ffff34d82b3 in g_signal_emit () from /usr/lib64/libgobject-2.0.so.0
    #7 0x00007ffff75d66cf in ?? () from /usr/lib64/libgtk-x11-2.0.so.0
    #8 0x00007ffff74c7d73 in gtk_propagate_event () from /usr/lib64/libgtk-x11-2.0.so.0
    #9 0x00007ffff74c8d43 in gtk_main_do_event () from /usr/lib64/libgtk-x11-2.0.so.0
    #10 0x00007ffff713dccc in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
    #11 0x00007ffff286ddde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
    #12 0x00007ffff28717a8 in ?? () from /usr/lib64/libglib-2.0.so.0
    #13 0x00007ffff2871c05 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
    #14 0x00007ffff74c9217 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0
    #15 0x000000000041bfee in bt_main_window_run ()
    #16 0x000000000041913d in bt_edit_application_run_ui ()
    #17 0x0000000000419f08 in bt_edit_application_run ()
    #18 0x0000000000418408 in main ()

    hth, Davey

    PS:
    >I will think of a way to blacklist some (e.g. memoryaudiosrc).
    I wouldn't do that. I would rather add useful descriptions and color the names (background?) red if they are "bad" machines...
    These descriptions could show up like tooltips. Shouldn't be too long then, though.

    best wishes, Davey

     
  • Stefan Sauer

    Stefan Sauer - 2010-01-15

    Please note that they aren'T per se 'bad machines', they are just not useful for making music. buzztard support all gstreamer plugins, some of them as slightly mis-classified. I can't just hide all sources with no params as that would also hide e.g. live input.sources.

    Is that backtrace from the svn version?

     
  • Jonas Oberhauser

    >Is that backtrace from the svn version?
    No, from the one I have installed. (">try running your installed version as below and attach the output here:")

    >I can't just hide all sources with no params as that would also hide e.g. live input.sources.
    quoting myself: "I wouldn't do that. I would rather add useful descriptions and color the
    names (background?) red if they are "bad" machines...
    These descriptions could show up like tooltips. Shouldn't be too long
    then, though." (">I will think of a way to blacklist some (e.g. memoryaudiosrc).")

    > 'bad machines',
    quoting myself: '"bad" machines'
    The double quotes enclosing 'bad' would normally identify the word "bad" as 'metaphorically', or 'not literally'. What I meant was that these are not really "bad", just not useful for making music.

    In hopes such misunderstandings can be avoided next time, Davey

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks