banshee.exe crashed with SIGSEGV in g_hash_table_lookup()

[LCID Fire]

Binary package hint: banshee

Crashed when quitting

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Feb 19 20:30:03 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/banshee/banshee.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: banshee 0.13.2+dfsg-2
PackageArchitecture: i386
ProcCmdline: banshee /usr/lib/banshee/banshee.exe --play-enqueued --enqueue
ProcCwd: /home/andreas
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=C
Signal: 11
SourcePackage: banshee
StacktraceTop:
 g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: banshee.exe crashed with SIGSEGV in g_hash_table_lookup()
Uname: Linux moonlight 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
?? ()
?? ()
?? ()
?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Andrew Conkling (andrewski)]

Pedro, is it that the stacktrace is missing debug symbols? Or that we need a gdb-based backtrace in this case?

[Pedro Villavicencio (pedro)]

yes the stacktrace is missing a lot of symbols look at the "??", that should be a function name, a full stacktrace shouldn't contains that, Please try to get a report with apport to see if it can be automated retrace or get one with gdb, thanks!.

[Pedro Villavicencio (pedro)]

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!.

[maku520 (maku520)]

hi, sorry i haven't really elaborated on the problem... it started happening after i got a bluetooth headset with A2DP and used banshee to play music through them. hope that helps.

also, i tried to obtain a backtrace but the repositories kept wanting GPG keys and i didn't see any on that page. what should i do in that regard?

again, sorry for not providing more info sooner. i hadn't read the comments, i just submitted the bug report through Apport. thanks!

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

maku520, just try again to obtain a backtrace following https://wiki.ubuntu.com/DebuggingProgramCrash. This will greatly help us.

If you follow the instruction step by step, there should be no problem with the GPG keys. Thanks in advance.

[maku520 (maku520)]

martin-
i don't have this problem anymore. i upgraded to ubuntu intrepid and now use pulseaudio for my bluetooth headphones. i do not get this specific problem with intrepid. however, i do get a new problem and i can't seem to get apport to report it. when i'm playing music through my bluetooth headphones (from any source) and then unplug my power adapter, gnome-power-settings and banshee crash and i have to manually kill them. apport doesn't automatically open when this happens. what should i do to file a bug report?
thanks,
maku

[maku520 (maku520)]

er, sorry... "gnome-power-settings" should be "gnome-power-manager"

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thanky you for your quick reply, maku520. You don't have to use apport to report a new bug; you can just do it via https://bugs.launchpad.net/ubuntu/+source/banshee/+filebug and then attach a backtrace of the crash (see https://wiki.ubuntu.com/DebuggingProgramCrash). Thanks.

[Andrew Conkling (andrewski)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.