David, since you are on Ubuntu and also use Chromium, can you reproduce this?

I can reproduce it. extbrowser module is using x-www-browser to start the default browser. So the explanation is that chromium is not set as a default browser for x-www-browser. Using "sudo update-alternatives --config x-www-browser" to set Chromium as a default one resolves this issue. I do not know anything about background though - why are we using x-www-browser and why it does not get updated automatically when I set default browser via "Default Applications" in Ubuntu's "All Settings". WORKSFORME?

> I do not know anything about background 

I do not know either - Denis, do you know? And is there another way to detect the default browser on Ubuntu than x-www-browser?

Requiring users to do "sudo update-alternatives --config x-www-browser" does not sound like an acceptable resolution - could we do a better job at detecting the default browser?

Taking over, I will try to look at it.

What I plan to do:
- "x-www-browser" is wrong - it works only on Debian (and its derivates), moreover it is a _system_ preferred browser, not a user preferred browser (user can prefer different browser than system administrator, of course);
- the proper way should be using XDG, it should work on all distros (at least I hope so).

(In reply to comment #0)
> The setting of Options / General / Web Browser is <Default System Browser>. My
> system's browser is set to Chromium.

Tondo, what you get if you run the following command, please?

xdg-settings get default-web-browser

Thanks.

Should be fixed I hope, please verify. Thanks.

http://hg.netbeans.org/web-main/rev/605e2b8f23b0

BTW I just noticed why x-www-browser was preferred - see issue #146603. However, I prefer the current fix which is IMHO correct.

If anyone (perhaps David as the reporter of issue #146603 ;) feels that URLs from JAR files should be handled, please reopen and I will add a check for the URL (open URLs from JAR using x-www-browser; use xdg-open for the rest).

Thanks.

(In reply to comment #7)
> (open URLs from JAR using x-www-browser; use xdg-open for the rest).

It would be better to use directly ChromeBrowser class etc. but not sure if it is doable (the code is a bit complicated).

Thanks.

(In reply to comment #7)
> BTW I just noticed why x-www-browser was preferred - see issue #146603.

After discussion with Petr, it seems that it should work with JAR URLs even with my fix. In any case, I will test it tomorrow and reopen if not.

Thanks.

Integrated into 'main-silver', will be available in build *201307172300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/605e2b8f23b0
User: Tomas Mysik <tmysik@netbeans.org>
Log: #221803 - <Default System Browser> not recognizing my default system browser

*** Bug 216412 has been marked as a duplicate of this bug. ***

(In reply to comment #5)
> Tondo, what you get if you run the following command, please?
> 
> xdg-settings get default-web-browser

tonda@tonda-latitude:~$ xdg-settings get default-web-browser
chromium-browser.desktop

Will it work also with other window managers?

Thanks.

(In reply to comment #12)
> Will it work also with other window managers?

XDG is window manager independent, AFAIK all (common) distros support it.

Thanks.

(In reply to comment #7)
> If anyone (perhaps David as the reporter of issue #146603 ;) feels that URLs
> from JAR files should be handled

Detecting system browser correctly is more important than opening jar:// URLs.

(In reply to comment #14)
> Detecting system browser correctly is more important than opening jar:// URLs.

I was too fast, sorry. It works correctly for URLs from JAR/ZIP files.

Thanks.