[ubuntu-mono] [Bug 191414] Re: mono applications don't start anymore

flickerfly josiah.ritchie at gmail.com
Wed Feb 13 16:46:36 GMT 2008


I'm having a similar problem, but I am getting errors. I've tried
reinstalling everything having to do with Mono. I think this might be a
MONO_PATH issue. Here's the information output when running the various
programs.

~$ tomboy
Corlib not in sync with this runtime: expected corlib version 60, found 56.
Loaded from: /usr/lib/mono/2.0/mscorlib.dll
Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.

~$ banshee
Corlib not in sync with this runtime: expected corlib version 60, found 56.
Loaded from: /usr/lib/mono/2.0/mscorlib.dll
Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.

~$ f-spot

** (/usr/lib/f-spot/f-spot.exe:30548): WARNING **: The following assembly referenced from /usr/lib/f-spot/f-spot.exe could not be loaded:
     Assembly:   NDesk.DBus    (assemblyref_index=8)
     Version:    1.0.0.0
     Public Key: f6716e4f9b2ed099
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/f-spot).


** (/usr/lib/f-spot/f-spot.exe:30548): WARNING **: Could not load file or assembly 'NDesk.DBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6716e4f9b2ed099' or one of its dependencies.
Stacktrace:


Native stacktrace:

        f-spot [0x8194ca6]
        f-spot [0x81770ed]
        [0xffffe440]
        f-spot(mono_object_new+0x18) [0x80b596a]
        f-spot(mono_exception_from_name_two_strings+0x44) [0x80f0a45]
        f-spot(mono_get_exception_file_not_found2+0x4f) [0x80f0b9c]
        f-spot [0x810f9a7]
        f-spot [0x811a390]
        f-spot(mono_class_vtable+0x181) [0x80b29b3]
        f-spot(mono_object_new+0x18) [0x80b596a]
        f-spot(mono_exception_from_name_two_strings+0x44) [0x80f0a45]
        f-spot(mono_get_exception_file_not_found2+0x4f) [0x80f0b9c]
        f-spot [0x810f9a7]
        f-spot [0x8176370]
        f-spot [0x817699e]
        f-spot [0x8176a98]
        f-spot [0x8176f2d]
        f-spot(mono_runtime_invoke+0x27) [0x80b0b2f]
        f-spot(mono_runtime_exec_main+0x142) [0x80b5383]
        f-spot(mono_runtime_run_main+0x27e) [0x80b5631]
        f-spot(mono_jit_exec+0xbd) [0x805a4cb]
        f-spot [0x805a5a8]
        f-spot(mono_main+0x1683) [0x805bdc9]
        f-spot [0x8059636]
        /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7cad050]
        f-spot [0x80595b1]

Debug info from gdb:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211541808 (LWP 30548)]
[New Thread -1222968432 (LWP 30550)]
[New Thread -1217188976 (LWP 30549)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
  3 Thread -1217188976 (LWP 30549)  0xffffe410 in __kernel_vsyscall ()
  2 Thread -1222968432 (LWP 30550)  0xffffe410 in __kernel_vsyscall ()
  1 Thread -1211541808 (LWP 30548)  0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread -1217188976 (LWP 30549)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e129f6 in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x0811bc9f in ?? ()
#3  0xb77323ac in ?? ()
#4  0x00000000 in ?? ()

Thread 2 (Thread -1222968432 (LWP 30550)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e0f676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0x08120dde in ?? ()
#3  0xb76991dc in ?? ()
#4  0xb76991c4 in ?? ()
#5  0xb7e0d541 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#6  0x081210eb in ?? ()
#7  0xb76991dc in ?? ()
#8  0xb76991c4 in ?? ()
#9  0x00000000 in ?? ()

Thread 1 (Thread -1211541808 (LWP 30548)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7d632a1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7e82780 in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#3  0xb7e82b4c in g_spawn_command_line_sync () from /usr/lib/libglib-2.0.so.0
#4  0x08194d84 in ?? ()
#5  0xb7b55844 in ?? ()
#6  0xb7b5582c in ?? ()
#7  0xb7b55828 in ?? ()
#8  0xb7b55824 in ?? ()
#9  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()


=================================================================
Got a SIGSEGV 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 (core dumped)

-- 
mono applications don't start anymore
https://bugs.launchpad.net/bugs/191414
You received this bug notification because you are a member of MOTU Mono
Team, which is a bug contact for mono in ubuntu.



More information about the Ubuntu-mono mailing list