monodevelop crashes on creating a new project

[EarlOfPudding]

When I try to create a new project, MonoDevelop crashes on clicking the "Create" button. I also tried to start MonoDevelop as root or create a different kind of project or change the path but nothing changed.
I can although open existing projects.

Currently I'm running Ubuntu 17.04 with the 4.8.0-46 kernel because the 4.10 kernel makes problems. Maybe that's the reason why MonoDevelop crashes.

I also opened MonoDevelop in terminal to see if I can get more informations about the problem. You can find the error message and output from the terminal as a file below.

Now these are some system informations:

'uname -a' says:
Linux Commodore-C64 4.8.0-46-generic #49-Ubuntu SMP Fri Mar 31 13:57:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

'lsb_release -a' says:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty

'apt-cache policy monodevelop' says:
monodevelop:
  Installiert: 5.10.0.871-2
  Installationskandidat: 5.10.0.871-2
  Versionstabelle:
 *** 5.10.0.871-2 500
        500 http://at.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
        500 http://at.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
        100 /var/lib/dpkg/status

'apt-cache policy mono-runtime' says:
mono-runtime:
  Installiert: 4.6.2.7+dfsg-1ubuntu1
  Installationskandidat: 4.6.2.7+dfsg-1ubuntu1
  Versionstabelle:
 *** 4.6.2.7+dfsg-1ubuntu1 500
        500 http://at.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: monodevelop 5.10.0.871-2
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Fri Apr 14 11:43:51 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-12-03 (131 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: monodevelop
UpgradeStatus: Upgraded to zesty on 2017-04-12 (1 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marko Hrastovec (marko-hrastovec)]

Hi,

I have the same problem. I first tried to open a project and monodevelop always crashed. After that I tried to create a new one and the result is the same.

[Marko Hrastovec (marko-hrastovec)]

I had quite big problems, because my disk crashed and I installed a new system and now I cannot open solutions. It was strange for me, that in another computer with the same version of monodevelop I can open projects.

After some tests I found out an interesting detail. If I open a solution with displaying file open dialog by selecting Open from menu or startup screen, the monodevelop crashes. On another computer I never open it that way. I always use recently used solutions, which are shown on the startup screen. I did not know why one monodevelop is working and another is not. When I tried to open a solution the same way, it crashed too.

The workaround for me now is to copy ~/.recently.used file to a new computer and open a project from startup page. In that way, monodevelop does not crash. I hope all other functions will work.

Unfortunately, I have no idea, how to make a new project.

This is a very nasty bug, which prevents users to use MonoDevelop in Ubuntu 17.04. I have tried it on two computers and got the same error on both. So I can pretty surely claim that it is repeatable on any Ubuntu 17.04 with Monodevelop that is provided their by default.

[Marko Hrastovec (marko-hrastovec)]

Another workaround is also to create a project/solution some other way. Then open it by calling and adding the solution filename as command line parameter:

monodevelop <solution file>

[John Cornell (john-wayne-cornell)]

this bug appears to be with the nuget interface trying to fill missing dependencies.

My workaround was to use fatpak.

sudo apt-get install flatpak
flatpak install --user --from https://download.mono-project.com/repo/monodevelop.flatpakref

and run with

flatpak run com.xamarin.MonoDevelop

this fixed the missing dependancies and the ubuntu store version then worked correctly

I believe a simpler fix would be

sudo apt-get install gtk-sharp2 gnome-sharp2

and then re running monodevelop but I am unable to verify.

[eniorm (eniorm)]

I have the same problem.
I installed monodevelop with this command:
$ sudo apt-get install -y monodevelop mono-complete gtk-sharp3 libmono-cairo4.0-cil

But IDE still crashing when I create new project or when I try to open a project.

Any idea?

[Reverend Fuzzy (pastor-t)]

I had the same problem this morning, and was close to changing to some other development environment, until an memory came to me.

I remembered the night before, I had been doing some system maintenance, and for some odd reason, I felt a need to rename the projects folder from "mono projects" to "mono-projects".

So before trying to open a previous project again, I opened the preferences window for MonoDevelop, (edit>preferences) and under the "Projects>Load/Save" section, there it was... it still had the original folder name in the "Default Solution location" text-box.

So I added the hyphen, saved it, and restarted MonoDevelop ... now it's back to working like a champ.

Hope that helped, or at least gave someone the hint needed to find their own solution.

[Selmi (selmi)]

i had the same problem

installation of gtk-sharp2 gnome-sharp2 from comment #6 didn't helped
installation of all suggested packages for monodevelop also didn't helped
change of default project director from comment #8 helped

interesting fact may be that directory which was set as default didn't existed at all. when i was creating new solution i set directory somewhere else, but monodevelop crashed. solution was partially created (first only folders, after installing of additional packages there were also files in them, but .sln with zero length and .csproj was prefixed with #temp or something like it)

when i changed default path and then created new solution then its path was already set in 'create new solution' windows and everything works correctly

[salvadoRevol (salvador-evol)]

I tried to change the "Default solution location" and I'm not getting the crash anymore. Good catch Selmi!