[ubuntu-mono] [Bug 882501] Re: Mono crashes while executing mono + Gtk# applications

Pekka Karjalainen 882501 at bugs.launchpad.net
Wed Nov 2 19:25:49 UTC 2011

Some statements I found in a series of web searches suggest that Oneiric
uses the CLI 4.0 runtime, and thus required using the appropriate
compiler for C# code and appropriate settings in Monodevelop. According
to them, you should use the dmcs compiler instead of gmcs. There is also
a specific setting in Monodevelop to compile for the 4.0 CLI runtime.

I managed to verify that, on Oneiric, a simple hello world window
application using GTK# compiles with dmcs on the command line and run
without the error shown above. If I use gmcs to compile it, it throws
the same exception and crashes the same way as above.

I learned that dmcs is the compiler to use for CLI 4.0 from here:


The 2nd message here recommends setting the "build -> runtime version"
option in Monodevelop to Mono / 4.0. :


I haven't tested the Monodevelop setting yet, because I haven't yet
installed it on my computer. Dmcs is in the mono-dmcs package.

You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to mono in Ubuntu.

  Mono crashes while executing mono + Gtk# applications

Status in “mono” package in Ubuntu:

Bug description:
  Platform: Intel x32 + Ubuntu Oneiric 11.10
  Package version: 2.10.5-1

  This error is still present in Ubuntu Oneiric for mono applications
  created with monodevelop and using Gtk#, but not, for some reason,
  applications bundled with the operating system.

  The same happened to me in Windows, and the problem disappeared
  upgrading to the current version of Mono (2.10.6). I guess this is
  going to be the same thing.

  Unfortunately, recompiling applications is not an option, as
  Monodevelop 2.6 is unable to find the Gtk# in the system (?). Again,
  the same happened to me in Windows, and upgrading to the current
  version of MonodeDevelop (2.8) solved the problem.

  Would it be possible to upgrade these packages to their current versions, so this bugs disappear?
  If not, how can I solve this in my system, so I'm able to use mono again?

To manage notifications about this bug go to:

More information about the Ubuntu-mono mailing list