Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.
Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.
Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.
Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.
Created attachment 23892 [details] solution Description of Problem: When I hit F5 in monodevelop Steps to reproduce the problem: 1. Open attached solution, hit F5 Actual Results: Message: "Cannot start a process because filename has not been provided" Expected Results: Application started. How often does this happen? Alsways. Additional Information: Solution in attach. This solution works without issues in Monodevelop 5.10 === MonoDevelop === Version 7.0.1 (build 24) Installation UUID: 7eb9353b-08e2-41fe-aa3e-e11596ce3667 Runtime: Mono 5.0.1 ((HEAD/5077205 Wed May 24 10:08:34 UTC 2017) (64-bit) GTK+ 2.24.29 (Ambiant-MATE theme) === NuGet === Version: 4.0.0.2323 === .NET Core === Runtime: Not installed SDK: Not installed MSBuild SDKs: /app/lib/mono/msbuild/15.0/bin/Sdks === Build Information === Release ID: 700010024 Git revision: 7ab1ca2ced6f584e56b7a0d4d321d00775cd95c9 Build date: 2017-05-24 10:46:46+00 === Operating System === Linux Linux 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64
Is this a flatpak install?
yes, this is install from flatpak
I'm suspecting this is flatpack specific, hence moving to "Linux packaging" component.
This is a duplicate of 44182 *** This bug has been marked as a duplicate of bug 44182 ***