#202 Core dump on Ubuntu Quantal 64 bit

v2.2
open
nobody
None
3
2014-12-11
2014-02-08
No

I installed the latest sonic package (deb package) on my Ubuntu 12.10 machine (Quantal) and found that is crashes immediately when you try to open a file. Just clicking File - Open generates a core dump.

Debian package installed:

markus@markus-ThinkPad-W530:~/Downloads$ dpkg -l "sonic*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                  Version                 Architecture            Description
+++-=====================================-=======================-=======================-================================================================================
ii  sonic-visualiser                      2.3cc-1                 amd64                   View and analyse the contents of music audio files

Starting sonic-visualizer and clicking on 'File' - 'Open'

markus@markus-ThinkPad-W530:~/Downloads$ sonic-visualiser 
`menu_proxy_module_load': sonic-visualiser: undefined symbol: menu_proxy_module_load

(sonic-visualiser:9127): Gtk-WARNING **: Failed to load type module: (null)

`menu_proxy_module_load': sonic-visualiser: undefined symbol: menu_proxy_module_load

(sonic-visualiser:9127): Gtk-WARNING **: Failed to load type module: (null)

`menu_proxy_module_load': sonic-visualiser: undefined symbol: menu_proxy_module_load

(sonic-visualiser:9127): Gtk-WARNING **: Failed to load type module: (null)

`menu_proxy_module_load': sonic-visualiser: undefined symbol: menu_proxy_module_load

(sonic-visualiser:9127): Gtk-WARNING **: Failed to load type module: (null)

PaneStack::showOrHidePaneAccessories: count == 1
Segmentation fault (core dumped)

Discussion

  • Chris Cannam

    Chris Cannam - 2014-02-13

    I couldn't reproduce this on Xubuntu 12.10. Can you get any sort of stack trace? i.e. run

    $ gdb ./sonic-visualiser
    (gdb) run
    (gdb) thread apply all backtrace
    $

    I don't think a trace will have much detail in it (the build won't have debug symbols) but it might give some hint.

     
  • Markus Baertschi

    Post awaiting moderation.

Log in to post a comment.

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

Sign up for the SourceForge newsletter:





No, thanks