I figured out the reason that monodevelop failed to start on two of our "trusty" systems.
What I did was to start monodevelop under "strace", trying to figure out what kind of load caused the exeception. Instead I found that monodevelop picked up dlls that I did not know was on the system. So when I claimed in the original posting that the systems were vanilla, this was not entirely correct - a collegue of mine had built and installed a copy of the mono system in /usr/local for some experimenting. So the system hosted two slightly different versions of the mono runtime. Removing the system from /usr/local solved the problem. Or rather, stopped it from occurring. Monodevelop is trying to be smart - it looks all over the system for dlls and loads everything. It might be a more robust architecture if monodevelop sticks to the standard mono installation per default, and then allows configuration of alternative location of the runtime system that the user might wish to use. But I realize that this is not a high-priority request - it is a pretty rare situation that a single installation holds more than one mono runtime system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364831 Title: monodevelop on trusty fails with TypeLoadException. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monodevelop/+bug/1364831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
