This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 216412 - Netbeans opens Chromium instead of Default System Browser, Firefox
Summary: Netbeans opens Chromium instead of Default System Browser, Firefox
Status: RESOLVED DUPLICATE of bug 221803
Alias: None
Product: ide
Classification: Unclassified
Component: Extbrowser (show other bugs)
Version: 7.2
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-05 19:57 UTC by BullfrogBlues
Modified: 2013-07-18 09:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BullfrogBlues 2012-08-05 19:57:41 UTC
Netbeans does not open Default System Browser.

NOTE
====

You can fix this behaviour by adding the option `-J-Dorg.netbeans.modules.extbrowser.UseDesktopBrowse=true` to `netbeans_default_options` in `netbeans-{VERSION}/etc/netbeans.conf`.  

CONFIGURATION
=============

Product Version: NetBeans IDE 7.2 (Build 201207171143)
Java: 1.7.0_03; OpenJDK 64-Bit
System: Linux version 3.2.0

- Ubuntu 12.04 64bit with Chromium + Firefox installed 

- Ubuntu Default Web Browser is set to Firefox

    > System Settings 
    > Details 
    > Default Applications 
    > Web = Firefox Web Browser

- Netbeans Web browser is set to Default System Browser

    > General 
    > Web Browser = Default System Browser


TO REPRODUCE
============

Run any command that should open browser, e.g. 

    - Run > Run File (Shift + F6)
    - Debug > Debug File (Ctrl + Shift + F5)
    etc...

EXPECTS
=======

Opens Firefox

ACTUAL
======

Opens Chromium
Comment 1 Mondane 2013-01-11 12:16:27 UTC
Confirmed on Ubuntu 12.10 64-bit with 

Another workaround is to set the used browsers via Tools > Options > General > Web Browser.
Comment 2 Tomas Mysik 2013-07-18 09:17:10 UTC
Should be fixed now, see issue #221803.

Thanks.

*** This bug has been marked as a duplicate of bug 221803 ***