Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #8277

Closed (moved)
(moved)
Open
Created Feb 19, 2013 by cypherpunks@cypherpunks

failed to get DOMWin for ... spammed to the console

I'm runnning Firefox 18.0.2 on Ubuntu 12.04LTS-64bits.

When I use sabnzb, I can see sometimes, on the console where sabnzdb is launched (sabnzd launches firefox when it starts), a lot of spam from httpseverywhere, linked to the SSL Observartory.

I have outputs like:

failed to get DOMWin for https://trac.torproject.org/tor.css

failed to get DOMWin for https://trac.torproject.org/projects/tor/chrome/common/css/ticket.css

failed to get DOMWin for https://blahblahblah....

SSL Observatory: Cert submission failure 0:

It does not seem to disrupt Firefox, but I'm not sure the observatory really works as it report a failure (but usually... at least on Linux, a return code of 0 would mean all OK and not a failure, so the message is very unclear).

I'm quite annoyed anyway to be spammed in the console, although it might be a side effect as firefox has been launched from the command line (due to launching it through sabnzb)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking