Whenever I try to start Monodevelop 4.0 (from the Mono Factory repository) on OpenSUSE 12.3 x64 (KDE 4.10.1), it fails. No errors, no messages of any kind no splash screen, just nothing. When I start it in konsole, it just immediately exits with code 0. I’m currently using it with Mono 3.0 from the standard OpenSUSE repos.
I have tried monodevelop 3.0.6 from the OpenSUSE repo and it fails with the following error on konsole:
Unhandled Exception:System.IO.FileNotFoundException: Could not load file or assembly 'Mono.Addins, Version=0.6.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' or one of its dependencies.
File name: 'Mono.Addins, Version=0.6.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'
at MonoDevelop.Startup.MonoDevelopMain.Main (System.String] args) [0x00000] in /home/abuild/rpmbuild/BUILD/monodevelop-3.0.6/src/core/MonoDevelop.Startup/MonoDevelop.Startup/MonoDevelopMain.cs:16
[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not load file or assembly 'Mono.Addins, Version=0.6.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' or one of its dependencies.
File name: 'Mono.Addins, Version=0.6.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'
at MonoDevelop.Startup.MonoDevelopMain.Main (System.String] args) [0x00000] in /home/abuild/rpmbuild/BUILD/monodevelop-3.0.6/src/core/MonoDevelop.Startup/MonoDevelop.Startup/MonoDevelopMain.cs:16
Missing method get_IsInitialized in assembly /usr/lib/monodevelop/bin/MonoDevelop.Ide.dll, type Mono.Addins.AddinManager
As for version 4.0, I do have output from trying to start it with MONO_LOG_LEVEL set to “debug” (pastebin link).
The error you focused on was for monodevelop 3, which I can settle for but I’d prefer to have version 4 working. I ran zypper verify to ensure all dependencies are satisfied, and they are. Regardless, the output of zypper se is in a pastebin here.
Mixing factory with stable is never a good idea. I don’t know why you aren’t getting any output from MD3 but I’m not surprised MD4 is crashing. You could try a dup to mono factory (zypper dup --from Mono:Factory), or file a bug report on MD3. Attachmate dropped the Mono team last year, so there’s some question as to who’s handling bugs right now, but it’s worth getting it documented.
Am 28.03.2013 20:26, schrieb chief sealth:
> Attachmate dropped the Mono
> team last year, so there’s some question as to who’s handling bugs right
> now,
answer: Xamarin
parts of the original development group are now at a new company which
is dedicated to mono development (and the former employer is now a
customer of that company)
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500
Am 28.03.2013 20:50, schrieb Martin Helm:
> (and the former employer is now a customer of that company)
oouch, I did not want to write “a customer” but “a consumer”
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500
“Customer” might be apt, Xamarin is focused mainly on commercial products for mobile devices. It would still be a good idea to report this on their bug tracker,
So the original issue was that MD3 was crashing and MD4 was giving no output at all. I manually installed my own Mono.Addins DLLs into /usr/lib/monodevelop/bin with MD3 installed and it stopped crashing and started giving no output at all (like MD4). Then I tried switching all mono packages to the versions from the Mono:Factory repo (except using YaST rather than zypper), and that did nothing for the no-output thing.
I’ll be reporting a bug to Xamarin tonight. Thanks for your suggestions, guys. I’ll update this thread if I learn anything from Xamarin.