Error: 'Error opening input stream (invalid filename?)' when calling method: [nsIObserver::observe] = NS_ERROR_XPC_JS_THREW_STRING

RESOLVED INVALID

Status

()

--
minor
RESOLVED INVALID
13 years ago
10 years ago

People

(Reporter: philip.chee, Assigned: janv)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060506 MultiZilla/1.8.2.0e Mnenhy/0.7.4.0 SeaMonkey/1.5a
(Erk! I can't cut and paste with this trunk build ?!?)

Error: 'Error opening input stream (invalid filename?)' when calling method: [nsIObserver::observe] = NS_ERROR_XPC_JS_THREW_STRING
Source file: chrome://global/content/bindings/tree.xml
Line: 82

<http://lxr.mozilla.org/seamonkey/source/xpfe/global/resources/content/bindings/tree.xml#81>

This is the line that fails:
        !/Mac/.test(navigator.platform)

This doesn't affect Firefox because their version of tree.xml uses #ifdef/#endif in the preprocessor.

Currently filing under "XP Toolkit/Widgets: Trees" but possibly should be moved to the JavaScript Engine component.
That's a strange error. What does this code have to do with the observer service? Or streams? Are you that's the line that's throwing the exception?
(Reporter)

Comment 2

13 years ago
What fun. As well as testing on a new profile, I've just installed a trunk build into a different location. Using this installation, I don't get the error.

comparing the two %Appdir%/chrome/ directories I seem to have a few extra .jar files in the problematic installation:

en-{mac|unix|win}.jar, US.jar, content-packs.jar. Looks like I'll need to do some housekeeping.

Marking this bug as invalid.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
(Reporter)

Comment 3

13 years ago
Just for reference: It was the greasemonkey.js in the components directory.

Updated

10 years ago
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: xptoolkit.trees → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.