FS#3641 - Mono apps seem to be experiencing problems

Attached to Project: Arch Linux
Opened by Chris Kaminski (Skankinsasquatch) - Tuesday, 20 December 2005, 04:54 GMT
Last edited by arjan timmerman (blaasvis) - Tuesday, 20 December 2005, 07:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Monodevelop errors with the following:

[shaft@leetbox ~]$ monodevelop

** (./MonoDevelop.exe:23898): WARNING **: The following assembly referenced from /opt/gnome/lib/monodevelop/bin/MonoDevelop.exe could not be loaded:
Assembly: gnome-sharp (assemblyref_index=4)
Version: 2.6.0.0
Public Key: 35e10195dab3c99f
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 (/opt/gnome/lib/monodevelop/bin/).


** (./MonoDevelop.exe:23898): WARNING **: Missing method get_UI in assembly /opt/gnome/lib/monodevelop/bin/MonoDevelop.exe, type Gnome.Modules

** ERROR **: file mini.c: line 9639 (mono_jit_compile_method_inner): should not be reached
aborting...
Aborted

Monodoc with the following:
[shaft@leetbox ~]$ monodoc
Bookmark Manager init

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

Stacktrace:

in <0x4> (wrapper managed-to-native) Gtk.Notebook:gtk_notebook_set_current_page (intptr,int)
in <0xffffffe2> (wrapper managed-to-native) Gtk.Notebook:gtk_notebook_set_current_page (intptr,int)
in <0x1a> Gtk.Notebook:set_CurrentPage (int)
in <0xa1> Monodoc.Browser:AddTab ()
in <0x84f> Monodoc.Browser:.ctor (bool)
in <0x2cd> Monodoc.Driver:Main (string[])
in <0x50653b6b> (wrapper runtime-invoke) System.Object:runtime_invoke_int_string[] (object,intptr,intptr,intptr)

Native stacktrace:

/usr/bin/mono(mono_handle_native_sigsegv+0xc0) [0x8149e10]
/usr/bin/mono [0x8119970]
[0xffffe440]
/opt/mozilla/lib/firefox/libgtkembedmoz.so [0xb67ad5c0]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b) [0xb6c0e4bb]
/usr/lib/libgobject-2.0.so.0 [0xb6c01829]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x139) [0xb6c01ee9]
/usr/lib/libgobject-2.0.so.0 [0xb6c114b2]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6c0) [0xb6c12e90]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6c131f9]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0xb4) [0xb70022a4]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0xd8) [0xb7002478]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6e7b345]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6e39baf]
/usr/lib/libgtk-x11-2.0.so.0(gtk_container_forall+0x6c) [0xb6e7988c]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6e7b399]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b) [0xb6c0e4bb]
/usr/lib/libgobject-2.0.so.0 [0xb6c01829]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x139) [0xb6c01ee9]
/usr/lib/libgobject-2.0.so.0 [0xb6c114b2]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6c0) [0xb6c12e90]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6c131f9]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x6f) [0xb700240f]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6e7b345]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6e39baf]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6f4d87c]
/usr/lib/libgtk-x11-2.0.so.0(gtk_container_forall+0x6c) [0xb6e7988c]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6e7b399]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b) [0xb6c0e4bb]
/usr/lib/libgobject-2.0.so.0 [0xb6c01829]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x139) [0xb6c01ee9]
/usr/lib/libgobject-2.0.so.0 [0xb6c114b2]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6c0) [0xb6c12e90]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6c131f9]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x6f) [0xb700240f]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6f25081]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b) [0xb6c0e4bb]
/usr/lib/libgobject-2.0.so.0 [0xb6c01829]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x139) [0xb6c01ee9]
/usr/lib/libgobject-2.0.so.0 [0xb6c114b2]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6c0) [0xb6c12e90]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6c131f9]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0x6f) [0xb700240f]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_set_child_visible+0xfc) [0xb700258c]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6f25642]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6f0e06f]
/usr/lib/libgobject-2.0.so.0 [0xb6c01829]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x139) [0xb6c01ee9]
/usr/lib/libgobject-2.0.so.0 [0xb6c118e2]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6c0) [0xb6c12e90]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6c131f9]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6f2598c]
[0xb67f0845]
[0xb67f07fb]
[0xb67ebb9a]
[0xb70e92b8]
[0xb7a3f066]
[0xb7a3e86c]
/usr/bin/mono(mono_runtime_exec_main+0x9c) [0x80923ac]
/usr/bin/mono(mono_runtime_run_main+0x16d) [0x80951ad]
/usr/bin/mono(mono_main+0x1011) [0x805d7c1]
/lib/tls/libc.so.6(__libc_start_main+0xdb) [0xb7d0ed6b]
/usr/bin/mono [0x805c251]
Aborted


However this does not pertain to all mono applications; for instance f-spot seems to load just fine. This is further documented in this thread: http://bbs.archlinux.org/viewtopic.php?t=17173&highlight=banshee.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Saturday, 04 February 2006, 14:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  seems it starts fine over here, closing
Comment by Tobias Kieslich (tobias) - Tuesday, 20 December 2005, 08:43 GMT
I see your trouble and I'm sorry for this. The point is that mono is breaking it's dependencies faster than you can rcompile the whole thing, which is a 100MB upload everytime for all the apps. But this time even a recompile of the whole suite didn't help. We even moved mono to /usr to get rid of all the pathes trouble. Considering, that they release software that doesn't compile at all or only ever now and then (mono-debugger for the past 3 releases of mono) or has tp be patched (monodevelop's --disable-boo switch doesn't help and even the patch provided on monodevelop's ML doesn't help anylonger, as of mono-1.1.11 for boo support) I seriously consider to pull back a couple of mono apps from the repos, since this is all definately beta/unstable quality software. Sorry for saying that.
Comment by Mark Rosenstand (bitbull) - Tuesday, 20 December 2005, 14:59 GMT
I agree with #1. Mono isn't very stable yet, and that causes a lot of trouble.

As I see it we have three options:
1. Completely get rid of all mono applications and libraries from the official repositories.
2. Move it all to unstable.
3. Learn to live with occasinal breakage till mono becomes more stable (should that ever happen) and *don't* count on it for anything production critical.

Personally I prefer 3, as I don't see any advantages in 1 and 2 other than maybe saving a kB in the repo database for extra. But I can follow tobias if he votes for 1, as he's the one with the "heavy" tasks whereas my mono packages usually only needs a recompile and sometimes a small patch.
Comment by Alexander Hunziker (alexthelion) - Thursday, 22 December 2005, 17:15 GMT
the config system of beagle-0.1.4 doesn't work either. beagle-settings as well as beagled throw exceptions upon reading the contents of ~/.beagle/config/indexing.xml. Somebody in #dashboard on GimpNet suggested this may be an incompatibility with Mono > 1.1.10.

Should I file a separate bug for this even if it is probably not distrospecific?
Comment by Janusz Kwiatkowski (janex) - Saturday, 14 January 2006, 13:11 GMT
This is a libgtkembedmoz.so from firefox problem. Try to export MOZILLA_FIVE_HOME=/opt/mozilla/lib/mozilla. This solve a monodoc problem, but monodevelop still try to use library from firefox. It is necessary to recompile monodevelop (or gecko-sharp-2) against library from mozilla.

Sorry for my poor english....
Comment by Tobias Kieslich (tobias) - Wednesday, 25 January 2006, 05:10 GMT
I followed the suggestion and monodevelop-0.9 is available from testing. PLease check and report if it works for you?

Loading...