Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using Ubuntu 13.10 (with Gnome 3.10.1) and MonoDevelop 3.0.3.2.

Before switching to GDM and Gnome 3 MonoDevelop worked just fine, but after switching I get this popup: "Could not connect to debugger" (as the picture shows, first the "Waiting.." popup pops up, then the could not connect (all this happens instantly)).

I am aware you can use the internal console (Project -> Options -> General) but it does not do it for me. I want the Gnome-terminal as I'm used to.

Does anyone know a fix to this? (Yes, I've tried reinstalling (including apt-get purge and removing the settings in ~/home)

enter image description here

share|improve this question

This is due to a recent gnome-terminal change. Recent gnome-terminal no longer accepts the --disable-factory argument.

Install the xterm package, then in a gnome-terminal session do the following:

$ unset GNOME_DESKTOP_SESSION_ID
$ monodevelop

This will cause monodevelop to use xterm as its external terminal and all should be well.

share|improve this answer

this little trick , works on my debian 8 (Cinnamon)

  1. Go to Solution Options via Project > ProjectName Options
  2. Under Run > General Section disable the Run on external Console for both Debug and Release Configuration

now it should work for you.

share|improve this answer

What is happening here that Mono is trying to open mcs to execute the console program. But since the mcs is not installed in the system, it keeps giving that error message. You just need to install mcs and that's all.

Open up the terminal and type this command: sudo apt-get install mono-mcs

This will probably solve the issue.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .