Bug 2026 - Monodevelop opens urls in wrong browser on some GNOME systems
Summary: Monodevelop opens urls in wrong browser on some GNOME systems
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8
Hardware: PC Linux
: Lowest normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-11-14 11:09 UTC by mattpepin
Modified: 2012-05-01 14:51 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

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 for Bug 2026 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description mattpepin 2011-11-14 11:09:57 UTC
When I run an ASP.NET project, Monodevelop automatically starts Firefox, which is not my default browser. I use Google Chrome and this is the default browser in my Gnome Preferences. Monodevelop ignores this and still starts Firefox. There should also be a checkbox to be able to choose if you want Monodevelop to start the browser automatically.
Comment 1 Mikayla Hutchinson [MSFT] 2012-04-28 09:32:46 UTC
MonoDevelop uses Gnome.Url.Show to open URLs via the default handler on Linux. Sounds like libgnome is broken on your distro.
Comment 2 mattpepin 2012-05-01 12:35:05 UTC
Hmm, then it's broken in Opensuse 11.4, 12.1 and Ubuntu.
Comment 3 Mikayla Hutchinson [MSFT] 2012-05-01 12:41:18 UTC
I suppose the fix is to have GnomePlatform P/Invoke gtk_show_uri on GTK+ 2.14 and later. Maybe we could remove the GNOME# dependency completely at this point?
Comment 4 Andres G. Aragoneses 2012-05-01 13:05:36 UTC
I added a binding API to gtk_show_uri into gtk-sharp master branch (the code actually came from Hyena). Maybe we should backport that addition to gtk-sharp 2-12 branch?
Comment 5 Mikayla Hutchinson [MSFT] 2012-05-01 13:27:41 UTC
You can't do that, GTK# 2.12 API is frozen. But it's trivial to add the P/Invoke into GnomePlatform. GnomePlatform already has various GIO P/Invokes.

I would recommend:
a) Make GnomePlatform depend on GTK+ 2.14 (you can check it at runtime, e.g. show a dialog if Gtk.Global.CheckVersion fails), no point in continuing to support ancient GTK+ versions.
b) Remove GNOME# dependencies from GnomePlatform - GTK+ 2.14 has everything we need IIRC
c) Port remaining GNOME# dependent features in GnomePlatform to P/Invokes to the equivalent GTK+ 2.14 APIs
Comment 6 Andres G. Aragoneses 2012-05-01 14:34:34 UTC
(In reply to comment #5)
> a) Make GnomePlatform depend on GTK+ 2.14

If you go this route, why not creating a new Gtk# branch called "2-14" and add the new method there? Seems much cleaner to me than going the PInvoke route (yes I know MD team has this long term plans of maybe not depending on gtk-sharp at all, but we're not there yet...)

> ...check it at runtime, e.g. show a dialog if Gtk.Global.CheckVersion fails)

And what to say in the dialog? Wouldn't it be better to depend on 2.14 anyway? (You want new versions of programs with features/bugfixes? You then need to upgrade ;) )
Comment 7 Andres G. Aragoneses 2012-05-01 14:35:29 UTC
(In reply to comment #6)
> And what to say in the dialog? Wouldn't it be better to depend on 2.14 anyway?

I meant, at compile time.
Comment 8 Mikayla Hutchinson [MSFT] 2012-05-01 14:51:44 UTC
GTK# 2.x is frozen at 2.12 API.