After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 370779 - Can't open new browser window with Web/Home button on keyboard
Can't open new browser window with Web/Home button on keyboard
Status: RESOLVED DUPLICATE of bug 322795
Product: gnome-control-center
Classification: Core
Component: [obsolete] Preferred applications
2.16.x
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-04 23:24 UTC by Mikel Ward
Modified: 2007-01-15 18:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Mikel Ward 2006-11-04 23:24:35 UTC 
Please describe the problem:
I am using Ubuntu 6.10 with Firefox 2.0.

If I set Firefox as my preferred web browser and choose the "Open link with web browser default" option, I am able to press the Web/Home button on my keyboard to get a new browser window.

If I choose the "Open link in new window" option, the Web/Home button does nothing.

The custom command field changes to firefox -remote "openurl(%s,new-window)" after selecting "Open link in new window".

I'm guessing pressing the Web/Home button calls this, but %s is replaced by an empty string, which Firefox regards as an error.

Based on the very limited output of "firefox -help", I think GNOME should invoke firefox -browser if there is no URL.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Mikel Ward 2006-11-04 23:31:34 UTC 
This is related to comment 1 in bug 322795.
Comment 2 Jens Granseuer 2007-01-15 18:39:31 UTC 
(In reply to comment #0)
> I'm guessing pressing the Web/Home button calls this, but %s is replaced by an
> empty string, which Firefox regards as an error.

Actually, the problem is that the -remote argument causes an error if there is not already a browser window open. So this is exactly the same issue as bug 322795.

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