On Fri, Aug 28, 2009 at 08:44:44AM -0400, Dominique Brazziel <[email protected]> wrote: > If, instead of running the 'iceweasel' script, the 'firefox-bin' > executable is invoked directly, as documented in the mozilla knowledge > base (see entry for '-new-tab' at > http://kb.mozillazine.org/Command_line_arguments), the problem does not > occur. Note that with both methods the page is opened in a new tab, > the only issue is the segfaults and core dumps generated. A message is > written to the kernel log: > > firefox-bin[14435]: segfault at b781f1b5 ip b7d53d91 sp bfdb3d34 error 4 > in libc-2.9.so[b7d24000+158000] > > > There are a couple of issues here: > 1. The '-new-tab' option is not documented in > the command line help for iceweasel or firefox-bin. > > 2. The default command for 'open link in new tab' > for iceweasel is 'iceweasel -new-tab "%s"', so > if conditions exists where invoking the script > instead of the executable directly could cause > a segfault and perhaps fail to open the new tab, > the user is left wondering why. > > 3. 'update-manager' just started failing to open > clickable bug report links in 'iceweasel' because > of this problem. 'update-manager' uses 'gnome-open' > to open the clickable URL, and I assume 'gnome-open' > interrogates the preferred browser settings to get > the command 'iceweasel -new-tab "%s"'. I can see > the command was issued via 'lastcomm', but the > bug report page is never displayed.
4. No third party application in its right might should be using the -new-tab option. There is a preference for users to choose how they want third party applications url openings to be treated. Third party applications shouldn't override this preference by using -new-tab. Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
