Bug 381787

Summary:	Konsole stopped working with MonoDevelop
Product:	[Applications] konsole	Reporter:	ger.fox07
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	ger.fox07, justin.zobel
Priority:	NOR
Version:	17.04.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description ger.fox07 2017-06-29 08:32:20 UTC

On a pretty fresh Tumbleweed install on which I did nothing fancier than to install a few packages, simple "Hello World" application in MonoDevelop cannot be debugged. When I push the debug button, MonoDevelop simply replies "Could not connect to debugger".
Googling this I found out that there was a similar issue under Gnome, that could be solved by unsetting GNOME_DESKTOP_SESSION_ID, which causes MonoDevelop to use a terminal other than GNOME's standard terminal. See https://superuser.com/questions/669444/monodevelop-cannot-connect-to-debugger
They say it's related to the gnome terminal not supporting a certain command line argument anymore.
Under KDE doing the same with KDE_SESSION_VERSION does the trick.
However, this is only a workaround because the different console that MonoDevelop uses instead of konsole is pretty unusable.

Things work fine with the same MonoDevelop version on openSUSE 42.1

Comment 1 Kurt Hindenburg 2017-06-30 00:49:49 UTC

I have no control over KDE_SESSION_VERSION; I wonder why this affects MonoDevelop and Konsole.

Did you follow this comment on the link and did it work while leaving KDE_SESSION_VERSION as is?

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

Comment 2 ger.fox07 2017-06-30 07:34:02 UTC

The reason this affects MonoDevelop is that it makes MonoDevelop use something other than konsole for the debugging session. So unsetting KDE_SESSION_VERSION does not fix the problem, it merely works around it.

I did follow that comment, but only to find that mono-mcs (the Mono C# compiler) is already installed.

So in summary: Mono debugging fails on openSUSE Tumbleweed if and only if MonoDevelop tries to use konsole for output.

I'm not terribly sure this really is the fault of konsole. It could be a bug in MonoDevelop or some other part of KDE as well. But hunting this down needed to start somewhere...

Comment 3 Justin Zobel 2020-11-03 01:42:32 UTC

Thanks for taking the time to report the bug and apologies for the delayed response. 

Are you able to confirm if this issue still persists between MonoDevelop and Konsole?

Comment 4 Bug Janitor Service 2020-11-18 04:33:44 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2020-12-03 04:34:02 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!