Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lighthouse does not work on Debian (Tracing.start wasn't found)

See original GitHub issue

Initial URL: http://localhost:8080/Server.html Chrome Version: 72.0.3626.81 Error Message: Protocol error (Tracing.start): ‘Tracing.start’ wasn’t found Stack Trace:

Error: Protocol error (Tracing.start): 'Tracing.start' wasn't found
    at Function.fromProtocolMessage (chrome-devtools://devtools/remote/serve_file/@ac8b982e05014492d1bd7d317628a4f22a97ffa0/audits2_worker/audits2_worker_module.js:1341:121)
    at callback.resolve.Promise.resolve.then._ (chrome-devtools://devtools/remote/serve_file/@ac8b982e05014492d1bd7d317628a4f22a97ffa0/audits2_worker/audits2_worker_module.js:998:253)

yeah no dice running audit on my local zim wiki huh.

Issue Analytics

State:
Created 5 years ago
Comments:34 (1 by maintainers)

Top GitHub Comments

6reactions

tpocommented, Oct 30, 2019

@patrickhulce wrote:

We have no affiliation and no ability to fix the Chromium on Debian build, so if you want to use Lighthouse there I suppose you’ll just need to use Google Chrome.

What should “We have “no affiliation” with Debian” exactly mean? Aren’t you using Debian at Google/Chrome? Isn’t Debian, just incidentally Open Source? Does basing your stuff on Open Source imply any moral responsiblity or is that just a “no affiliation” relation? Aren’t there Google/Chrome developers that are also Debian developers, so that in fact they (and the Chrome/Google collective) have upload rights and would be able to fix what’s broken from within Debian? I think if there is good will on your part, then there is a path for you and you can drop the “no affiliation/blame shifting game” without loss.

Also: “[we have] no ability to fix the Chromium on Debian build”. You do. The problem that Debian has has been known in this thread clearyl: some parts from which Chromium is built are not available in their original source format (but only as minified js).

So what is needed is for someone to do the work: identifiy which parts are affected, add the original sources or link to them and make sure that those parts get built from their original sources.

The “we’re not responsible” game will not bring anybody further. Doing the work will (including Chrome/Google).

5reactions

partulajcommented, Feb 27, 2019

I am running Chronium 72.0.3626.96 on Debian stretch

Top Results From Across the Web

chromium: URL chrome://tracing does not work any more

Forwarded to https://github.com/GoogleChrome/lighthouse/issues/7246 ... is: "Protocol error (Tracing.start): 'Tracing.start' wasn't found".

Albatroz Jeremias: "tracing is not enabled on open source version of ...

Lighthouse does not work on Debian (Tracing.start wasn't found) · Issue #7246 · GoogleChrome/lighthouse. Initial URL: http://localhost:8080/Server.html ...

931143 - URL chrome://tracing does not work on Debian

Issue 931143: URL chrome://tracing does not work on Debian ... The error is: "Protocol error (Tracing.start): 'Tracing.start' wasn't found".

Optimize website speed using Lighthouse - Microsoft Edge ...

This tutorial teaches you how to use DevTools to find ways to make your websites load faster. This tutorial uses the Lighthouse tool....

Lighthouse: .../tracing-start-wasnt-found.yaml | Fossies

As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) Ansible YAML source code syntax...