Description of problem: Monodevelop doesn't start, by running /usr/bin/monodevelop on x86_64. Version-Release number of selected component (if applicable): mono-core-2.4.2.3-2.fc12.x86_64 gtk-sharp2-2.12.9-1.fc12.x86_64 mono-data-2.4.2.3-2.fc12.x86_64 gnome-sharp-2.24.0-6.fc12.x86_64 gnome-desktop-sharp-2.26.0-4.fc12.x86_64 mono-data-sqlite-2.4.2.3-2.fc12.x86_64 mono-addins-0.4-8.20091702svn127062.1.fc12.x86_64 mono-web-2.4.2.3-2.fc12.x86_64 mono-nunit-2.4.2.3-2.fc12.x86_64 monodoc-2.4.2.3-2.fc12.x86_64 mono-winforms-2.4.2.3-2.fc12.x86_64 monodevelop-2.1.0-2.fc12.x86_64 How reproducible: try starting monodevelop Steps to Reproduce: start monodevelop from CLI to see its output Actual results: WARNING: Cannot find Mozilla directory containing libgtkembedmoz.so. Some Addins may not be able to function. Please set MOZILLA_FIVE_HOME to your Mozilla directory. Cannot open assembly '/usr/lib/monodevelop/bin/MonoDevelop.exe': No such file or directory. Expected results: monodevelop should start. Additional info: If I run monodevelop directy (mono /usr/lib64/monodevelop/bin/MonoDevelop.exe) it works. The start script should be adjusted to x86_64.
*** Bug 528952 has been marked as a duplicate of this bug. ***
I've fixed the problem in CVS and created a new build: https://koji.fedoraproject.org/koji/buildinfo?buildID=139492 Please can you test whether it fixes your issue? If all testing turns out well, I'll request to tag it for F-12 final.
The upstream monodevelop script seems to work already. But your changed line in the new build (${0%%/bin/monodevelop}/lib64/monodevelop/bin/MonoDevelop.exe) works also. Why does it work now with lib and lib64?? (I'm still on x86_64 and have no x86 mono stuff installed...) I will try to test your version today and let you know!
(In reply to comment #3) > The upstream monodevelop script seems to work already. > But your changed line in the new build > (${0%%/bin/monodevelop}/lib64/monodevelop/bin/MonoDevelop.exe) works also. > > Why does it work now with lib and lib64?? Which exact upstream monodevelop script you mean? Even the unpatched scripts looks like that it should not work on x86_64: EXE_PATH="${0%%/bin/monodevelop}/lib/monodevelop/bin/MonoDevelop.exe" > (I'm still on x86_64 and have no x86 mono stuff installed...) Can you check, whether there is (for whatever reason ;) ) a file named: /usr/lib/monodevelop/bin/MonoDevelop.exe on your system? > I will try to test your version today and let you know! Did you already had a chance to test the new build? Since F12 final is approaching quickly, I'd like to get some feedback and then it can be tagged for F12. ;-)
Sorry for the delay... Now, I just found some time to lay my fingers on monodevelop again. 1st: It was my fault: I installed monodevelop from source (in /usr/local) which I ran... :-) 2nd: Upstream monodevelop (monodevelop-2.1.0-2.fc12.x86_64) does not start at all. 3rd: Your build starts fine, but I can't compile a simple hello world. (It tells me, I have no Mono / .NET 3.5 installed.) 4th: I have no /usr/lib/monodevelop/bin/MonoDevelop.exe, see 1st. Hope that helps! Cheers, Jakob
Same here, using monodevelop-2.1.0-3.fc12.x86_64.rpm: Upon startup, these messages are printed: WARNING: Cannot find Mozilla directory containing libgtkembedmoz.so. Some Addins may not be able to function. Please set MOZILLA_FIVE_HOME to your Mozilla directory. pp SCAN: SetupDomain WARNING: [MonoDevelop.NUnit,2.1.0] Could not load some add-in assemblies: File '/usr/lib64/monodevelop/AddIns/NUnit/nunit.core.dll' not found. ERROR: Errors found in add-in '/usr/lib64/monodevelop/AddIns/NUnit/MonoDevelop.NUnit.dll: ERROR: The file '/usr/lib64/monodevelop/AddIns/NUnit/nunit.core.dll' referenced in the manifest could not be found. ERROR: The file '/usr/lib64/monodevelop/AddIns/NUnit/nunit.core.interfaces.dll' referenced in the manifest could not be found. ERROR: The file '/usr/lib64/monodevelop/AddIns/NUnit/nunit.framework.dll' referenced in the manifest could not be found. ERROR: The file '/usr/lib64/monodevelop/AddIns/NUnit/nunit.util.dll' referenced in the manifest could not be found. WARNING: The add-in 'MonoDevelop.MonoDeveloperExtensions,2.1.0' is trying to extend '/MonoDevelop/NUnit/TestProviders', but there isn't any add-in defining this extension point WARNING: The add-in 'MonoDevelop.MonoDeveloperExtensions,2.1.0' is trying to extend '/MonoDevelop/NUnit/TestProviders/MonoTestProvider', but there isn't any add-in defining this extension point WARNUNG [2009-11-05 08:27:53Z]: Inotify watch limit is too low (8192). MonoDevelop will switch to managed file watching. See http://monodevelop.com/Inotify_Watches_Limit for more info. WARNUNG [2009-11-05 08:27:53Z]: Error creating composed icon gtk-execute___asm2__debug-overlay-22.png at size Button. Icon __asm2__debug-overlay-22.png is 20x20, expected 22x22. When trying to build a simple hello world project (completely created by the wizard), it fails with this message: WARNUNG [2009-11-05 08:28:46Z]: mscorlib assembly not found for framework '3.5'. The framework may not be installed.
(In reply to comment #6) > When trying to build a simple hello world project (completely created by the > wizard), it fails with this message: > > WARNUNG [2009-11-05 08:28:46Z]: mscorlib assembly not found for framework > '3.5'. The framework may not be installed. Please can you create a tarball of the complete hello world project directory (after you've tried to compile and execute it) and attach it to this bug report. I hope this will give me enough information to locate the problem - thanks!
Created attachment 367781 [details] Monodevelop - Helloworld This is the whole project directory.
I've just recognized that there is another bug especially dealing with the remaining problem that it is not possible to compile a project on x86_64 system: https://bugzilla.redhat.com/show_bug.cgi?id=528955 Since the original problem of this bug (monodevelop can't be started) is actually solved, I'll use the other one ( #528955 ) to deal with the compile problem (I've already found the root cause and I'll provide another test package soon). Please add yourself to its CC: list.
I agree, the original problem is solved. Thank you very much! Should we close the bug?
(In reply to comment #10) > I agree, the original problem is solved. Thank you very much! > Should we close the bug? This will happen automatically when the update is pushed out. Please can you have a look at the new build referenced in https://bugzilla.redhat.com/show_bug.cgi?id=528955 whether the compile problem is fixed as well? Please add the comment then to that bug.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 539382 has been marked as a duplicate of this bug. ***
monodevelop-2.1.0-4.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.