Banshee.exe crashed with SIGABRT in raise()

Bug #750608 reported by Maciej Piotrowski
126
This bug affects 16 people
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: banshee

Don't know what happened. Just linstening to the music.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: banshee 1.9.6-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Apr 4 20:41:10 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
Signal: 6
SourcePackage: banshee
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: Banshee.exe crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Maciej Piotrowski (maccieju) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=0x5e0be0 "mono_convert_imt_slot_to_vtable_slot", message=0x7f17d41a86cd "code should not be reached") at /build/buildd/glib2.0-2.28.5/./glib/gtestutils.c:1358
 mono_convert_imt_slot_to_vtable_slot (slot=<value optimized out>, regs=<value optimized out>, code=<value optimized out>, method=<value optimized out>, impl_method=0x7f179f7dd260, need_rgctx_tramp=0x7f179f7dd26c) at mini-trampolines.c:183
 mono_magic_trampoline (regs=0x7f179f7dd488, code=0x4046b65a "H\213\375H\201\307\360\376\377\377A\272\340\026'\002\220\350\200w-\001\205\300u\304H\203\354\b\350\t", arg=0xffffffffffffffff, tramp=<value optimized out>) at mini-trampolines.c:366

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in banshee (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
Kieran Hogg (xerosis) wrote :

Just saw this same bug too.

Changed in banshee (Ubuntu):
status: New → Confirmed
Revision history for this message
Alex Murray (alexmurray) wrote :

Just got hit by this (or at least what looks like this). Am attaching the output from ~/.config/banshee-1/log which contains the crash info I think.

Revision history for this message
Andres G. Aragoneses (knocte) wrote :

That looks like a Mono bug, what version of Mono are you running? If you're running any version lower than 2.10.x it would be nice to check if the bug is gone when you upgrade to 2.10.x.

Changed in banshee (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Kieran Hogg (xerosis) wrote :

I'm on 2.10.4

Changed in banshee (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in banshee (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.