lighthouse: Lighthouse does not work on Debian (Tracing.start wasn't found)
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.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 34 (1 by maintainers)
@patrickhulce wrote:
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).
I am running Chronium 72.0.3626.96 on Debian stretch
I am running Chromium: Version 72.0.3626.109 (Developer Build) built on Debian buster/sid, running on Debian buster/sid (64-bit)
@marekdedic
From what I can see in the ticket here, it doesn’t seem you are talking to/with the Debian maintainers? So I’ve asked them: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922431#16 .
Looking at a similar bug in Debian, it looks like Tracing was intentionally disabled. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922431
@AnnoyingTechnology correct AFAIK it’s just the Chromium build that’s modified and distributed through debian, not the official Google Chrome build, that’s affected by this.
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.
2/2 Debian so far, if it’s Debian-specific that would certainly explain the difficulty reproducing on our end.
@eMPee584 @samimussbach are you both debian as well?
This is simply not true. The original source format of catapult’s scripts are just located outside of the Chromium repo. I’m assuming they are referring to the third party scripts of catapult which are checked in pre-bundled, yet each is accompanied by the corresponding license, version, and documentation links where to find the original source.
I’m not sure I would agree with your assertion that a project has a responsibility to compel all its forks to support all of its features. The beauty of open source is that when Debian has a philosophical disagreement where no intermediate steps can come between the published package and the true source, then it’s free to fork and modify the project however it wishes in pursuit of that goal. Claiming that a project is not open source simply because it uses the bundles that other open source projects provide does a disservice to the community.
Thanks for finding that @xxv! There’s not really anything that can be done on our side then. Leaving this open as a reference, but no expectation that this can be fixed by the Lighthouse team.
@Hoten For me the problem appear whatever the url is, even on this issue page
yes Debian here too indeed 😏
On February 27, 2019 6:18:09 PM GMT+01:00, Patrick Hulce notifications@github.com wrote:
– Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
yes, indeed I am on current debian testing as well