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
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
|
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
Saturday, 04 February 2006, 14:22 GMT
Reason for closing: Fixed
Additional comments about closing: seems it starts fine over here, closing
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.
Should I file a separate bug for this even if it is probably not distrospecific?
Sorry for my poor english....