mono applications don't start anymore

Bug #191414 reported by Manuel Schmid
4
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: mono

Since approximately 10 days, all mono-application (tested with Tomboy, F-Spot and Desktop Drapes) don't start any more. When I try starting them from the console, no error message is displayed and the hard drive makes a strange clicking noise.
The problem occurs on a Sony Vaio laptop running Ubuntu 7.10 with the latest updates installed. The laptop is not my own, but If more info about the hardware or package versions are needed, I can provide them.

Revision history for this message
flickerfly (josiah-ritchie) wrote :
Download full text (4.7 KiB)

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

Read more...

Revision history for this message
flickerfly (josiah-ritchie) wrote :

gtkpod is complaining also. I didn't realize it had mono depends...

~$ gtkpod
gtkpod: /opt/mono-1.2.6/lib/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
gtkpod: symbol lookup error: /usr/lib/libxml2.so.2: undefined symbol: gzopen64

Revision history for this message
flickerfly (josiah-ritchie) wrote :

...

~$ vim
vim: /opt/mono-1.2.6/lib/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
vim: Symbol `ospeed' has different size in shared object, consider re-linking

Revision history for this message
John Dong (jdong) wrote :

/opt/mono-1.2.6? Where did you install Mono from?

It seems like your Mono distribution installed a bunch of .so's that are not compatible with your Ubuntu install.

Revision history for this message
flickerfly (josiah-ritchie) wrote :

I found out my problem. It had nothing to do with a bug. Sorry for the noise. Manuel, I had to remove my /opt/mono-1.2.6 directory and reinstall mono from rubenv's repositories to get the latest mono from his stuff. The problem turned out to be a 2 competing installations of libraries. The Cairo guys got me straightened out. I did have to also re-install a couple mono packages to get everything back in its proper place and to let everyone know where they were.

I'm going to mark it as invalid because because I expect Manuel's problem to be similar and my problem clearly wasn't a bug in mono or ubuntu, but with me. Manuel, correct the status if I'm wrong.

Changed in mono:
status: New → 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.