about:about gives strange error

Bug #238660 reported by Thinboy00
6
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Fix Released
Medium
firefox-3.0 (Ubuntu)
Won't Fix
Low
Unassigned
firefox-3.5 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: firefox-3.0

If you navigate to "about:foobar", Firefox tells you "the URL is not valid and cannot be loaded." If you try "about:" it shows you the info from Help -> About
If you navigate to "about:about" Firefox redirects you to jar:file:///usr/lib/xulrunner-1.9/chrome/toolkit.jar!/content/global/aboutAbout.html and tells you that it cannot be located (File not Found). This behavior also occurs if you do in a terminal gksudo "firefox about:about".

To reproduce:
1. Go to about:about in the Location bar

What happens:
File not Found

What should happen:
Either it should behave identically to about:foobar (link doesn't work, you need to use the location bar) or it should give a listing of all about: URIs.

ProblemType: Bug
Architecture: i386
Date: Mon Jun 9 15:14:56 2008
DistroRelease: Ubuntu 8.04
Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: i386
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-17-generic i686

Tags: apport-bug
Revision history for this message
In , Philringnalda (philringnalda) wrote :

Related to, but *not* a duplicate of, bug 220253 - we could avoid the 404 without being sensible enough to have a real about:about.

Revision history for this message
In , Reed Loden (reed) wrote :

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

Revision history for this message
In , Mozilla2007 (mozilla2007) wrote :

This still affects FF3 Beta4. Will there be a fix for this at the final release? No real showstopper, but ugly though...

Revision history for this message
In , Beltzner (beltzner) wrote :

Not gonna block the final release, no.

Revision history for this message
In , Baffclan (baffclan) wrote :

patch for fix by Paul Rouget
attachment 307698 (bug 421280)

Revision history for this message
In , Moo (moo) wrote :

Yeah, I noticed that too, was going to come and submit it, but you beat me to it.

Its not horrible, but still ugly...

Revision history for this message
In , Dewildt-gmail (dewildt-gmail) wrote :

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

Revision history for this message
In , Philringnalda (philringnalda) wrote :

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

Revision history for this message
In , Reed Loden (reed) wrote :

glandium, can you re-attach your patch here and request review? Thanks!

Revision history for this message
In , Mh+mozilla (mh+mozilla) wrote :

Actually, I'm wondering... since everyone except firefox wants it, why not have it in toolkit and let firefox unregister it ?

Revision history for this message
In , Philringnalda (philringnalda) wrote :

We could call that approach "the bug 365852 solution," if not for the fact that it's already wontfixed.

Revision history for this message
In , Mh+mozilla (mh+mozilla) wrote :

Created attachment 322062
patch removing about:about

Okay, so this is the patch I originally sent to #434842, with an additionnal hunk to make it more complete.

Revision history for this message
Thinboy00 (thinboy00) wrote :

Binary package hint: firefox-3.0

If you navigate to "about:foobar", Firefox tells you "the URL is not valid and cannot be loaded." If you try "about:" it shows you the info from Help -> About
If you navigate to "about:about" Firefox redirects you to jar:file:///usr/lib/xulrunner-1.9/chrome/toolkit.jar!/content/global/aboutAbout.html and tells you that it cannot be located (File not Found). This behavior also occurs if you do in a terminal gksudo "firefox about:about".

To reproduce:
1. Go to about:about in the Location bar

What happens:
File not Found

What should happen:
Either it should behave identically to about:foobar or it should give a listing of all about: URIs.

ProblemType: Bug
Architecture: i386
Date: Mon Jun 9 15:14:56 2008
DistroRelease: Ubuntu 8.04
Package: firefox-3.0 3.0~rc1+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: i386
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-17-generic i686

Revision history for this message
Thinboy00 (thinboy00) wrote :
Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 238660] [NEW] about:about gives strange error

On Mon, Jun 09, 2008 at 07:21:01PM -0000, Thinboy00 wrote:
> Public bug reported:
>
> Binary package hint: firefox-3.0
>
> If you navigate to "about:foobar", Firefox tells you "the URL is not valid and cannot be loaded." If you try "about:" it shows you the info from Help -> About
> If you navigate to "about:about" Firefox redirects you to jar:file:///usr/lib/xulrunner-1.9/chrome/toolkit.jar!/content/global/aboutAbout.html and tells you that it cannot be located (File not Found). This behavior also occurs if you do in a terminal gksudo "firefox about:about".
>
> To reproduce:
> 1. Go to about:about in the Location bar
>
> What happens:
> File not Found
>
> What should happen:
> Either it should behave identically to about:foobar or it should give a listing of all about: URIs.
>

 status confirmed
 importance low

 - Alexander

Changed in firefox-3.0:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

On Mon, Jun 09, 2008 at 09:42:18PM -0000, Alexander Sack wrote:
>
> status confirmed
> importance low
>

We should try if the same issue exists when using upstream
builds. Anyone can try?

 affects firefox
 incomplete

 - Alexander

Revision history for this message
John Vivirito (gnomefreak) wrote :

Alexander Sack wrote:
> On Mon, Jun 09, 2008 at 09:42:18PM -0000, Alexander Sack wrote:
>
>> status confirmed
>> importance low
>>
>>
>
> We should try if the same issue exists when using upstream
> builds. Anyone can try?
>
> affects firefox
> incomplete
>
> - Alexander
>
>
> ** Also affects: firefox
> Importance: Undecided
> Status: New
>
>
Ill test it on upstream since i have to update my upstream package
anyway. Also never start firefox with sudo gksu gksudo or any of the
other ways to use "root" I would suggest since you did that to please
start with a clean profile as it can and will screw your firefox up.
Ok will test in a few minutes and report here about outcome.

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

Revision history for this message
John Vivirito (gnomefreak) wrote :

This happens on upstream RC2 build. Im looking for an upstream bug report now.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Reported bug upstream after not being able to find one already reported

Changed in firefox:
importance: Undecided → Unknown
status: New → Unknown
Changed in firefox:
status: Unknown → New
Revision history for this message
In , Cbook (cbook) wrote :

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

Revision history for this message
John Vivirito (gnomefreak) wrote :

found a duplicate of our bug updated link

Changed in firefox:
status: Unknown → Confirmed
Revision history for this message
In , longsonr (longsonr) wrote :

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

Revision history for this message
In , Dtownsend (dtownsend) wrote :

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

Revision history for this message
In , Achchuthan (achchuthan) wrote :

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

Thinboy00 (thinboy00)
description: updated
Revision history for this message
In , Sgautherie-bz (sgautherie-bz) wrote :

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.2pre) Gecko/2008070706 GranParadiso/3.0.2pre] (nightly) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1a1pre) Gecko/2008070703 Minefield/3.1a1pre] (nightly) (W2Ksp4)

(Bug still there)

Revision history for this message
In , Davemgarrett (davemgarrett) wrote :

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

Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

I'm not sure I see why this patch makes sense. Is firefox the only thing setting MOZ_XUL_APP? Would it make more sense to remove about:about from here altogether and let apps that do want it register it? That was suggested in bug 365852 too, no?

In any case, I'm clearly not qualified to review this, since I don't know what he MOZ_XUL_APP define actually means.

Revision history for this message
In , Mh+mozilla (mh+mozilla) wrote :

(In reply to comment #19)
> I'm not sure I see why this patch makes sense. Is firefox the only thing
> setting MOZ_XUL_APP? Would it make more sense to remove about:about from here
> altogether and let apps that do want it register it? That was suggested in bug
> 365852 too, no?

Actually, it seems that most applications except firefox want it... I know firefox is the big boy, but i don't think that grants bothering all other applications.

> In any case, I'm clearly not qualified to review this, since I don't know what
> he MOZ_XUL_APP define actually means.

MOZ_XUL_APP should be defined for any application using toolkit.

Revision history for this message
In , Mh+mozilla (mh+mozilla) wrote :

Personally, I would just move the aboutAbout.html file in toolkit and have it installed. If firefox maintainers really don't like this page, they can unregister it from somewhere in browser/

Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

> MOZ_XUL_APP should be defined for any application using toolkit.

In which case this patch would disable about:about for all toolkit-using apps, no? That doesn't seem to match the first part of comment 20 well....

I would be fine with adding aboutAbout to toolkit. But I'm not a toolkit peer.

Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

Comment on attachment 322062
patch removing about:about

I can't even set review- on that request (or review+, for that matter)...

Revision history for this message
In , Dtownsend (dtownsend) wrote :

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

Revision history for this message
In , Mike Connor (mconnor) wrote :

nice to have, not a big deal either way.

Revision history for this message
In , Xymuu (xymuu) wrote :

still not fixed

Revision history for this message
In , Zeniko (zeniko) wrote :

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

Revision history for this message
Mackenzie Morgan (maco.m) wrote :

Still reproducible in Intrepid, and it's definitely upstream (reproducible on OSX).

Revision history for this message
In , Dtownsend (dtownsend) wrote :

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

Revision history for this message
In , Dtownsend (dtownsend) wrote :

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

Revision history for this message
In , Reed Loden (reed) wrote :

Created attachment 344013
patch - v1

As per bug 451909, all apps set MOZ_XUL_APP now, so let's just kill this unused code.

Changed in firefox:
status: Confirmed → In Progress
Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

Reed, I'm not sure I follow. Doesn't this just remove about:about?

Revision history for this message
In , Reed Loden (reed) wrote :

(In reply to comment #31)
> Reed, I'm not sure I follow. Doesn't this just remove about:about?

Yes, I thought everybody had gotten rid of their implementations for this (meaning we could just remove it), but apparently SeaMonkey still has it... should I just #ifdef it only for SeaMonkey instead?

Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

I don't think we want an #ifdef here. We should't need an ifdef to do what comment 19 suggests.

Also, see comment 20 about non-Firefox about:about impls...

Revision history for this message
In , Philringnalda (philringnalda) wrote :

I sort of thought the point of http://mxr.mozilla.org/comm-central/source/suite/browser/nsAboutAbout.js was that SeaMonkey didn't trust Firefox not to do exactly this, and so they implemented it themselves, and now removing the docshell redirect is only going to screw over Camino, and only if they move to mozilla-central rather than going to WebKit.

Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

Yeah, if the patch doesn't break seamonkey, and if xulrunner apps (which is what I assume Mike Hommey was talking about) don't care, then it's fine.

Revision history for this message
In , Reed Loden (reed) wrote :

(In reply to comment #35)
> Yeah, if the patch doesn't break seamonkey, and if xulrunner apps (which is
> what I assume Mike Hommey was talking about) don't care, then it's fine.

What XULRunner apps (besides SeaMonkey) implement about:about? I don't know of any... so, I think we're fine.

Revision history for this message
In , Bzbarsky (bzbarsky) wrote :

Comment on attachment 344013
patch - v1

OK, let's do this, then. Please check whether this makes aboutAbout.xhtml unused, and remove it if so (that is, if Seamonkey has forked it).

Please keep an eye out for breakage.

Revision history for this message
In , Reed Loden (reed) wrote :
Revision history for this message
In , Baffclan (baffclan) wrote :

cannot reproduce with Firefox/20081024020852-trunk/WinXP

Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.1b2pre) Gecko/20081024 Minefield/3.1b2pre firefox

thanks for fixing this.
-> v.

Revision history for this message
In , Antoine-mechelynck-gmail (antoine-mechelynck-gmail) wrote :

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081024 SeaMonkey/2.0a2pre - Build ID: 20081024000423

Trying to browse to about:about leaves the content area blank, with the following messages in the Error Console:

[X] Error: [Exception... "'JavaScript component does not have a method named:
           "getURIFlags"' when calling method: [nsIAboutModule::getURIFlags]"
           nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"
           location: "JS frame ::
               chrome://communicator/content/contentAreaClick.js ::
               addToUrlbarHistory :: line 262" data: no]
    Source File: chrome://communicator/content/contentAreaClick.js Line: 262

[X] Error: [Exception... "'JavaScript component does not have a method named:
           "getURIFlags"' when calling method: [nsIAboutModule::getURIFlags]"
           nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"
           location: "JS frame :: chrome://global/content/bindings/browser.xml ::
               loadURIWithFlags :: line 186" data: no]
    Source File: chrome://global/content/bindings/browser.xml Line: 186

The latter one happens twice.

Now I'm going to test a recent tinderbox-build (maybe this nightly didn't include the fix).

Revision history for this message
In , Antoine-mechelynck-gmail (antoine-mechelynck-gmail) wrote :

(In reply to comment #40)
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081024
> SeaMonkey/2.0a2pre - Build ID: 20081024000423
>
[...]
>
> Now I'm going to test a recent tinderbox-build (maybe this nightly didn't
> include the fix).

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081024 SeaMonkey/2.0a2pre - Build ID: 20081024091143

Nope, no change. Should I REOPEN or file a specific bug for SeaMonkey?

Revision history for this message
In , Reed Loden (reed) wrote :

(In reply to comment #41)
> Nope, no change. Should I REOPEN or file a specific bug for SeaMonkey?

Sounds like a SeaMonkey-only bug to me, so file a new bug for SeaMonkey.

Revision history for this message
In , Antoine-mechelynck-gmail (antoine-mechelynck-gmail) wrote :

(In reply to comment #42)
> (In reply to comment #41)
> > Nope, no change. Should I REOPEN or file a specific bug for SeaMonkey?
>
> Sounds like a SeaMonkey-only bug to me, so file a new bug for SeaMonkey.

Filed bug 461552.

Changed in firefox:
status: In Progress → Fix Released
Revision history for this message
John Vivirito (gnomefreak) wrote :

With 3.0.4 and 3.1 is still a problem 3.1 is expected since it is no where near beta.

Revision history for this message
In , Davemgarrett (davemgarrett) wrote :

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

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

This is fixed upstream now.

Changed in firefox-3.0:
status: Confirmed → Fix Committed
Revision history for this message
In , Patrick-hendriks+bugzilla (patrick-hendriks+bugzilla) wrote :

Re comment 44: possibly the dupe wasn't really a dupe, but a regression?

Using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090404 Minefield/3.6a1pre, i'm getting a "The URL is not valid and cannot be loaded". Can anyone please check if this still works or if this has regressed?

Revision history for this message
In , Philringnalda (philringnalda) wrote :

That is precisely what you should get: the fix was to make about:about just like about:foopygoats, because neither one is supported in Firefox. Bug 469896 was filed about 3.0.x, where this wasn't and won't be fixed, so there it gives a file not found error instead of a proper (for an about: URL that isn't supported) "not valid and cannot be loaded" error.

Revision history for this message
In , John Vivirito (gnomefreak) wrote :

I can confirm on 3.5

Revision history for this message
Micah Gersten (micahg) wrote :

This has been fixed in Firefox 3.5

Changed in firefox-3.5 (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
Revision history for this message
Micah Gersten (micahg) wrote :

Firefox 3.0 is only receiving Security Updates and major bug fixes at this point.

Changed in firefox-3.0 (Ubuntu):
status: Fix Committed → Won't Fix
Changed in firefox:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.