Closed
Bug 310633
Opened 20 years ago
Closed 20 years ago
Initial load of my.yahoo (home page) fails with beaglePageLoad alert
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jgeldman, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.2 (like Gecko)
Build Identifier: from opensuse 10 online update
I just upgraded to 1.07. my.yahoo.com is my home page. This is repeatable now,
but I'm about to dump caches & also reboot - I haven't rebooted since online
update.
When firefox is started, an alert pops up with the following message (warning
hand copied - cut/paste doesn't work on alert box):
beaglePageLoad: beagleWriteContent failed: [Exception... "Component returned
failure code: 0x80004005 (NS_ERROR_FAILURE)
[ns[WebBrowserPersist.saveDocument]" nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: *JS frame :: chrome://beagle/content/beagle/Overlay.js ::
beagleWriteContent :: line 119" data:no]
Reproducible: Always
Steps to Reproduce:
1.bring it up
2.
3.
Expected Results:
not fail & alert 8-?
default theme
the alert pops up with any page. OK'ing the alert, and the page is usable, but
any page gets the alert back
| Reporter | ||
Comment 1•20 years ago
|
||
reboot & cache clear didn't help
mozilla.org page (and seemingly everything else) brings up the alert, BUT this
page didn't.
Got the build info now:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
| Reporter | ||
Comment 2•20 years ago
|
||
I am running the extension beagle on this machine. (I didn't remember that) I
haven't able to uninstall it yet - it reports that it will be, but on restarting
firefox, it is still there.
I don't think this is a "firefox" problem.
beagle version 0.1 is reported in the about page for the extension, but version
0.2 on the extension panel itself.
Comment 3•20 years ago
|
||
Problems with Beagle don't need to get filed on bugzilla.mozilla.org. It's shown
in the error that this is an error in Beagle's code -- something we have no
control over.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•