SIGABRT fatal error with mono applications

[Benjamin Humphrey]

Binary package hint: banshee

NOTE: This is a mono bug, rather than a problem with banshee itself, as the same thing happens in Gnome-Do. It could be due to one of the recent updates as this just happened today. I have reinstalled all the relevant packages, banshee, all mono packages and gnome-do as well but it still throws the error message below:

---------------------------------------

benjamin@benjamin-laptop:~$ banshee

** (/usr/lib/banshee-1/Banshee.exe:4794): CRITICAL **: _wapi_shm_file_open: shared file [/home/benjamin/.wapi/shared_data-benjamin-laptop-Linux-x86_64-328-12-0] open error: Input/output error

** (/usr/lib/banshee-1/Banshee.exe:4794): CRITICAL **: _wapi_shm_attach: shared file [/home/benjamin/.wapi/shared_data-benjamin-laptop-Linux-x86_64-328-12-0] open error
**
ERROR:shared.c:349:shm_semaphores_init: assertion failed: (tmp_shared != NULL)

** (/usr/lib/banshee-1/Banshee.exe:4794): WARNING **: Thread (nil) may have been prematurely finalized
Stacktrace:

** (/usr/lib/banshee-1/Banshee.exe:4794): WARNING **: Thread (nil) may have been prematurely finalized

Native stacktrace:

 banshee-1 [0x47a5ef]
 /lib/libpthread.so.0 [0x7efff4ebc190]
 /lib/libc.so.6(gsignal+0x35) [0x7efff48ed4b5]
 /lib/libc.so.6(abort+0x180) [0x7efff48f0f50]
 /lib/libglib-2.0.so.0(g_assertion_message+0x120) [0x7efff5536540]
 /lib/libglib-2.0.so.0 [0x7efff5536ab0]
 banshee-1 [0x56a310]
 banshee-1 [0x557be6]
 banshee-1(mono_once+0x64) [0x5653e4]
 banshee-1 [0x557b53]
 banshee-1 [0x5692c5]
 banshee-1 [0x506dfe]
 banshee-1(mono_runtime_init+0x25) [0x50e9b5]
 banshee-1 [0x419133]
 banshee-1(mono_main+0x417) [0x461f97]
 /lib/libc.so.6(__libc_start_main+0xfd) [0x7efff48d8abd]
 banshee-1 [0x416e19]

Debug info from gdb:

[Thread debugging using libthread_db enabled]
0x00007efff4ebb090 in __read_nocancel () from /lib/libpthread.so.0
* 1 Thread 0x7efff5b9b730 (LWP 4794) 0x00007efff4ebb090 in __read_nocancel ()
   from /lib/libpthread.so.0

Thread 1 (Thread 0x7efff5b9b730 (LWP 4794)):
#0 0x00007efff4ebb090 in __read_nocancel () from /lib/libpthread.so.0
#1 0x000000000047a764 in ?? ()
#2 <signal handler called>
#3 0x00007efff48ed4b5 in raise () from /lib/libc.so.6
#4 0x00007efff48f0f50 in abort () from /lib/libc.so.6
#5 0x00007efff5536540 in g_assertion_message () from /lib/libglib-2.0.so.0
#6 0x00007efff5536ab0 in g_assertion_message_expr ()
   from /lib/libglib-2.0.so.0
#7 0x000000000056a310 in ?? ()
#8 0x0000000000557be6 in ?? ()
#9 0x00000000005653e4 in mono_once ()
#10 0x0000000000557b53 in ?? ()
#11 0x00000000005692c5 in ?? ()
#12 0x0000000000506dfe in ?? ()
#13 0x000000000050e9b5 in mono_runtime_init ()
#14 0x0000000000419133 in ?? ()
#15 0x0000000000461f97 in mono_main ()
#16 0x00007efff48d8abd in __libc_start_main () from /lib/libc.so.6
#17 0x0000000000416e19 in ?? ()
#18 0x00007fffe76f4ee8 in ?? ()
#19 0x000000000000001c in ?? ()
#20 0x0000000000000002 in ?? ()
#21 0x00007fffe76f6603 in ?? ()
#22 0x00007fffe76f660d in ?? ()
#23 0x0000000000000000 in ?? ()

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted

-----------------------------------------

ProblemType: Bug
Architecture: amd64
Date: Sat Nov 7 23:09:58 2009
DistroRelease: Ubuntu 9.10
Package: banshee 1.5.1-1
ProcEnviron:
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
Uname: Linux 2.6.32-020632rc5-generic x86_64

[Benjamin Humphrey (humphreybc)]

Reason I marked it as a banshee bug rather than a mono bug is that there are dozens of mono related packages, and I wasn't sure which one is actually causing the problem. Sorry for any inconvenience.

[Chow Loong Jin (hyperair)]

On Saturday 07,November,2009 06:15 PM, Benjamin Humphrey wrote:
> Reason I marked it as a banshee bug rather than a mono bug is that there
> are dozens of mono related packages, and I wasn't sure which one is
> actually causing the problem. Sorry for any inconvenience.
>
Input/Output error indicates a hard disk issue. `rm -rf ~/.wapi` should do the
trick. Marking invalid.

   affects ubuntu/banshee
   status invalid

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Contributing Developer

[Benjamin Humphrey (humphreybc)]

So it did, thankyou! One more problem that I now know how to fix. Cheers!