Monodevelop cannot connect to debugger
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)
ubuntu gnome monodevelop
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
asked Nov 4 '13 at 16:39
user269394
36113
add a comment |
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)
ubuntu gnome monodevelop
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
asked Nov 4 '13 at 16:39
user269394
36113
add a comment |
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)
ubuntu gnome monodevelop
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
asked Nov 4 '13 at 16:39
user269394
36113
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)
ubuntu gnome monodevelop
ubuntu gnome monodevelop
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
asked Nov 4 '13 at 16:39
user269394
36113
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
asked Nov 4 '13 at 16:39
user269394
36113
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
edited Nov 4 '13 at 16:59
heavyd
50.1k12123155
50.1k12123155
asked Nov 4 '13 at 16:39
user269394
36113
asked Nov 4 '13 at 16:39
user269394
36113
asked Nov 4 '13 at 16:39
user269394
36113
36113
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
this little trick , works on my debian 8 (Cinnamon)
- Go to Solution Options via Project > ProjectName Options
- Under Run > General Section disable the Run on external Console for both Debug and Release Configuration
now it should work for you.
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
There is no such option.
– Regis May
Mar 11 '18 at 17:02
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
add a comment |
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.
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
1
For KDE, it'sKDE_SESSION_VERSION, for Mate -MATE_DESKTOP_SESSION_ID
– Dmitry Fedorkov
Oct 12 '16 at 1:20
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
add a comment |
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.
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
answered Mar 9 '16 at 17:35
Dev Gaurav
111
Not true.mcsis installed on my system and it still isn't working.
– starbeamrainbowlabs
Nov 1 '18 at 11:56
add a comment |
su
cd /opt/monodevelop && nano monodevelop.sh
in monodevelop.sh, write:
#!/bin/bash
unset -v GNOME_DESKTOP_SESSION_ID
cd /usr/bin && ./monodevelop-opt #or monodevelop if exist
save the file and:
chmod +x monodevelop.sh
ln -s /opt/monodevelop/monodevelop.sh /usr/local/bin/monodevelop
cd /usr/share/applications/ && nano monodevelop-opt.desktop #or monodevelop.desktop if exist
in the file, set or modify lines: Exec= and TryExec= to:
Exec=monodevelop %F
TryExec=monodevelop
Save the file.
edited Mar 21 '17 at 5:32
G-Man
5,566112357
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
The variable isXDG_SESSION_IDon xfce, but unsetting it simply changed the error message toDebugger operation failed:-/
– starbeamrainbowlabs
Nov 1 '18 at 12:28
add a comment |
protected by Community♦ Dec 19 '18 at 18:46
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
this little trick , works on my debian 8 (Cinnamon)
- Go to Solution Options via Project > ProjectName Options
- Under Run > General Section disable the Run on external Console for both Debug and Release Configuration
now it should work for you.
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
There is no such option.
– Regis May
Mar 11 '18 at 17:02
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
add a comment |
this little trick , works on my debian 8 (Cinnamon)
- Go to Solution Options via Project > ProjectName Options
- Under Run > General Section disable the Run on external Console for both Debug and Release Configuration
now it should work for you.
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
There is no such option.
– Regis May
Mar 11 '18 at 17:02
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
add a comment |
this little trick , works on my debian 8 (Cinnamon)
- Go to Solution Options via Project > ProjectName Options
- Under Run > General Section disable the Run on external Console for both Debug and Release Configuration
now it should work for you.
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
this little trick , works on my debian 8 (Cinnamon)
- Go to Solution Options via Project > ProjectName Options
- Under Run > General Section disable the Run on external Console for both Debug and Release Configuration
now it should work for you.
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
answered Apr 9 '16 at 4:02
Koorosh Ghorbani
22123
22123
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
There is no such option.
– Regis May
Mar 11 '18 at 17:02
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
add a comment |
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
There is no such option.
– Regis May
Mar 11 '18 at 17:02
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
It worked on my arch with KDE ... thanks ;)
– fady mohamed osman
Jul 26 '17 at 10:52
There is no such option.
– Regis May
Mar 11 '18 at 17:02
There is no such option.
– Regis May
Mar 11 '18 at 17:02
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
I don't see "General" under "Run". I only see "Configurations".
– Aaron Franke
Dec 6 '18 at 21:32
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
you dont see that option because this answer belongs to 2016 :))
– Koorosh Ghorbani
Dec 8 '18 at 11:30
add a comment |
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.
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
1
For KDE, it'sKDE_SESSION_VERSION, for Mate -MATE_DESKTOP_SESSION_ID
– Dmitry Fedorkov
Oct 12 '16 at 1:20
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
add a comment |
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.
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
1
For KDE, it'sKDE_SESSION_VERSION, for Mate -MATE_DESKTOP_SESSION_ID
– Dmitry Fedorkov
Oct 12 '16 at 1:20
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
add a comment |
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.
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
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.
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
answered Apr 22 '14 at 20:04
Kayvan Sylvan
21123
21123
1
For KDE, it'sKDE_SESSION_VERSION, for Mate -MATE_DESKTOP_SESSION_ID
– Dmitry Fedorkov
Oct 12 '16 at 1:20
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
add a comment |
1
For KDE, it'sKDE_SESSION_VERSION, for Mate -MATE_DESKTOP_SESSION_ID
– Dmitry Fedorkov
Oct 12 '16 at 1:20
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
1
1
For KDE, it's
KDE_SESSION_VERSION, for Mate - MATE_DESKTOP_SESSION_ID– Dmitry Fedorkov
Oct 12 '16 at 1:20
For KDE, it's
KDE_SESSION_VERSION, for Mate - MATE_DESKTOP_SESSION_ID– Dmitry Fedorkov
Oct 12 '16 at 1:20
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
......but this fix doesn't work with an XFCE desktop :-(
– starbeamrainbowlabs
Oct 11 '18 at 11:41
add a comment |
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.
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
answered Mar 9 '16 at 17:35
Dev Gaurav
111
Not true.mcsis installed on my system and it still isn't working.
– starbeamrainbowlabs
Nov 1 '18 at 11:56
add a comment |
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.
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
answered Mar 9 '16 at 17:35
Dev Gaurav
111
Not true.mcsis installed on my system and it still isn't working.
– starbeamrainbowlabs
Nov 1 '18 at 11:56
add a comment |
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.
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
answered Mar 9 '16 at 17:35
Dev Gaurav
111
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.
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
answered Mar 9 '16 at 17:35
Dev Gaurav
111
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
edited Mar 9 '16 at 19:07
Ben N
29.1k1396143
29.1k1396143
answered Mar 9 '16 at 17:35
Dev Gaurav
111
answered Mar 9 '16 at 17:35
Dev Gaurav
111
answered Mar 9 '16 at 17:35
Dev Gaurav
111
111
Not true.mcsis installed on my system and it still isn't working.
– starbeamrainbowlabs
Nov 1 '18 at 11:56
add a comment |
Not true.mcsis installed on my system and it still isn't working.
– starbeamrainbowlabs
Nov 1 '18 at 11:56
Not true.
mcs is installed on my system and it still isn't working.– starbeamrainbowlabs
Nov 1 '18 at 11:56
Not true.
mcs is installed on my system and it still isn't working.– starbeamrainbowlabs
Nov 1 '18 at 11:56
add a comment |
su
cd /opt/monodevelop && nano monodevelop.sh
in monodevelop.sh, write:
#!/bin/bash
unset -v GNOME_DESKTOP_SESSION_ID
cd /usr/bin && ./monodevelop-opt #or monodevelop if exist
save the file and:
chmod +x monodevelop.sh
ln -s /opt/monodevelop/monodevelop.sh /usr/local/bin/monodevelop
cd /usr/share/applications/ && nano monodevelop-opt.desktop #or monodevelop.desktop if exist
in the file, set or modify lines: Exec= and TryExec= to:
Exec=monodevelop %F
TryExec=monodevelop
Save the file.
edited Mar 21 '17 at 5:32
G-Man
5,566112357
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
The variable isXDG_SESSION_IDon xfce, but unsetting it simply changed the error message toDebugger operation failed:-/
– starbeamrainbowlabs
Nov 1 '18 at 12:28
add a comment |
su
cd /opt/monodevelop && nano monodevelop.sh
in monodevelop.sh, write:
#!/bin/bash
unset -v GNOME_DESKTOP_SESSION_ID
cd /usr/bin && ./monodevelop-opt #or monodevelop if exist
save the file and:
chmod +x monodevelop.sh
ln -s /opt/monodevelop/monodevelop.sh /usr/local/bin/monodevelop
cd /usr/share/applications/ && nano monodevelop-opt.desktop #or monodevelop.desktop if exist
in the file, set or modify lines: Exec= and TryExec= to:
Exec=monodevelop %F
TryExec=monodevelop
Save the file.
edited Mar 21 '17 at 5:32
G-Man
5,566112357
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
The variable isXDG_SESSION_IDon xfce, but unsetting it simply changed the error message toDebugger operation failed:-/
– starbeamrainbowlabs
Nov 1 '18 at 12:28
add a comment |
su
cd /opt/monodevelop && nano monodevelop.sh
in monodevelop.sh, write:
#!/bin/bash
unset -v GNOME_DESKTOP_SESSION_ID
cd /usr/bin && ./monodevelop-opt #or monodevelop if exist
save the file and:
chmod +x monodevelop.sh
ln -s /opt/monodevelop/monodevelop.sh /usr/local/bin/monodevelop
cd /usr/share/applications/ && nano monodevelop-opt.desktop #or monodevelop.desktop if exist
in the file, set or modify lines: Exec= and TryExec= to:
Exec=monodevelop %F
TryExec=monodevelop
Save the file.
edited Mar 21 '17 at 5:32
G-Man
5,566112357
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
su
cd /opt/monodevelop && nano monodevelop.sh
in monodevelop.sh, write:
#!/bin/bash
unset -v GNOME_DESKTOP_SESSION_ID
cd /usr/bin && ./monodevelop-opt #or monodevelop if exist
save the file and:
chmod +x monodevelop.sh
ln -s /opt/monodevelop/monodevelop.sh /usr/local/bin/monodevelop
cd /usr/share/applications/ && nano monodevelop-opt.desktop #or monodevelop.desktop if exist
in the file, set or modify lines: Exec= and TryExec= to:
Exec=monodevelop %F
TryExec=monodevelop
Save the file.
edited Mar 21 '17 at 5:32
G-Man
5,566112357
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
edited Mar 21 '17 at 5:32
G-Man
5,566112357
edited Mar 21 '17 at 5:32
G-Man
5,566112357
edited Mar 21 '17 at 5:32
G-Man
5,566112357
5,566112357
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
answered Feb 21 '17 at 14:09
Jakub Kaliszewski
111
111
The variable isXDG_SESSION_IDon xfce, but unsetting it simply changed the error message toDebugger operation failed:-/
– starbeamrainbowlabs
Nov 1 '18 at 12:28
add a comment |
The variable isXDG_SESSION_IDon xfce, but unsetting it simply changed the error message toDebugger operation failed:-/
– starbeamrainbowlabs
Nov 1 '18 at 12:28
The variable is
XDG_SESSION_ID on xfce, but unsetting it simply changed the error message to Debugger operation failed :-/– starbeamrainbowlabs
Nov 1 '18 at 12:28
The variable is
XDG_SESSION_ID on xfce, but unsetting it simply changed the error message to Debugger operation failed :-/– starbeamrainbowlabs
Nov 1 '18 at 12:28
add a comment |
protected by Community♦ Dec 19 '18 at 18:46
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
