soundconverter crashed with SIGSEGV in PyThreadState_New()

[Nawaf Alsallami]

Binary package hint: soundconverter

i was converting .rm sound file then quited when error message showed up
thank you for your help

ProblemType: Crash
Architecture: i386
Date: Fri Mar 28 01:56:26 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/soundconverter
InterpreterPath: /usr/bin/python2.5
Package: soundconverter 0.9.8-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/soundconverter file:///home/User Name/Downloads/mawlay.rm
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ar_EG.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: soundconverter
StacktraceTop:
 PyThreadState_New ()
 PyGILState_Ensure ()
 ?? ()
 ?? ()
 ?? ()
Title: soundconverter crashed with SIGSEGV in PyThreadState_New()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:PyGILState_Ensure () at ../Python/pystate.c:567
?? () from /usr/lib/python2.5/site-packages/gst-0.10/gst/_gst.so
?? ()
?? ()
?? ()

[Kjell Braden (afflux)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 123870, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Kjell Braden (afflux)]

Stop, it's maybe not. Can you try to provide a full backtrace following the instructions at [WWW] http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report? This will greatly help us in tracking down your problem.

Thanks a lot!

[Kjell Braden (afflux)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!