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 231961 - Chromium is opened instead of Chrome
Summary: Chromium is opened instead of Chrome
Status: RESOLVED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Extbrowser (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: issues@web
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-27 20:41 UTC by Vladimir Riha
Modified: 2013-06-27 21:26 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2013-06-27 20:41:05 UTC 
For some reason, whenever I run project in Chrome with NB integration, Chromium with NB integration is started instead (the same for plain Chrome). Also, in Tools|Options, path to Chrome browser is set to Chromium. Pahts are:

Chrome: C:\Users\vlriha\AppData\Local\Chromium\Application\chrome.exe
Chromium: C:\Users\vlriha\AppData\Local\Chromium\Application\chrome.exe
System default: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe


What is quite interesting (for me) is that IDE checks Chrome if the extension is installed. So I installed extension to Chrome, IDE is OK with that and yet it tries to run Chromium.


I tried both 64b and 32b JDKs. I'm not aware of doing anything that could cause this in OS setting. I'll try it once more with W8 I usually use as "windows". I also tried older Build 201306181109 and it works there. This seems to be Windows specific issue




Product Version: NetBeans IDE Dev (Build 201306262301)
Java: 1.7.0_15; Java HotSpot(TM) Client VM 23.7-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_15-b03
System: Windows 7 version 6.1 running on x86; Cp1252; en_US (nb)
Comment 1 Vladimir Riha 2013-06-27 21:26:30 UTC 
I'm sorry for false alert, I was trying all trunk builds from this week and again the reported 201306262301 and I can't reproduce it anymore, weird.