Bug#922431: chromium: URL chrome://tracing does not work any more
Sebastien Helleu
Version: 72.0.3626.81-1
Severity: normal
Dear Maintainer,
With chromium version 72.0.3626.81, the URL chrome://tracing does not work any more.
It displays this error:
-----
This site can’t be reached The webpage at chrome://tracing/ might be temporarily down or it may have moved permanently to a new web address.
ERR_INVALID_URL
-----
The extension Lighthouse, depending on this tracing feature does not work any more.
The error is: "Protocol error (Tracing.start): 'Tracing.start' wasn't found".
It is a regression, it was OK with chromium version 72.0.3626.53.
I reported the bug in Chromium bug tracker, but they answered it might be an issue
with Debian packaging (since the same version works fine on Ubuntu).
The chromium bug is: https://bugs.chromium.org/p/chromium/issues/detail?id=931143
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii chromium-common 72.0.3626.81-1
ii libasound2 1.1.8-1
ii libatk-bridge2.0-0 2.30.0-4
ii libatk1.0-0 2.30.0-2
ii libatomic1 8.2.0-20
ii libatspi2.0-0 2.30.0-7
ii libavcodec58 7:4.1.1-1
ii libavformat58 7:4.1.1-1
ii libavutil56 7:4.1.1-1
ii libc6 2.28-7
ii libcairo-gobject2 1.16.0-2
ii libcairo2 1.16.0-2
ii libcups2 2.2.10-3
ii libdbus-1-3 1.12.12-1
ii libdrm2 2.4.97-1
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat1 2.2.6-1
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.1-2
ii libfreetype6 2.9.1-3
ii libgcc1 1:8.2.0-20
ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7
ii libglib2.0-0 2.58.3-1
ii libgtk-3-0 3.24.5-1
ii libharfbuzz0b 2.3.1-1
ii libicu63 63.1-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libjsoncpp1 1.7.4-3
ii liblcms2-2 2.9-3
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.20-1
ii libnss3 2:3.42.1-1
ii libopenjp2-7 2.3.0-1.1
ii libopus0 1.3-1
ii libpango-1.0-0 1.42.4-6
ii libpangocairo-1.0-0 1.42.4-6
ii libpci3 1:3.5.2-1
ii libpng16-16 1.6.36-5
ii libpulse0 12.2-4
ii libre2-5 20190101+dfsg-2
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.2.0-20
ii libva2 2.4.0-1
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux2 0.6.1-2
ii libwebpmux3 0.6.1-2
ii libx11-6 2:1.6.7-1
ii libx11-xcb1 2:1.6.7-1
ii libxcb1 1.13.1-2
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-2
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-7+b3
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.32-2
ii libxss1 1:1.2.3-1
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages chromium recommends:
ii chromium-sandbox 72.0.3626.81-1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii x11-utils 7.7+4
ii xdg-utils 1.1.3-1
Versions of packages chromium-common recommends:
ii chromium-sandbox 72.0.3626.81-1
ii dunst [notification-daemon] 1.3.2-1
ii fonts-liberation 1:1.07.4-9
ii libgl1-mesa-dri 18.3.3-1
pn libu2f-udev <none>
pn upower <none>
Versions of packages chromium-sandbox depends on:
ii libatomic1 8.2.0-20
ii libc6 2.28-7
ii libgcc1 1:8.2.0-20
ii libstdc++6 8.2.0-20
-- no debconf information
Sébastien Helleu
>
> Tracing is disabled in debian starting with 72.0.3626.81-1. Its
> implementation relies on many sourceless javascript files.
>
> Best wishes,
> Mike
Then maybe the "Audits" tab in DevTools could be removed? (not sure if that's
easy to do that).
Because it seems broken when you try to perform an audit on a site, there's an
error: "Ah, sorry! We ran into an error: Protocol error (Tracing.start):
'Tracing.start' was not found".
I spent many hours to understand it was related to the latest version available
in Debian, so I think this can confuses other people as well.
--
Sébastien Helleu
web: weechat.org / flashtux.org
irc: FlashCode @ irc.freenode.net
Tomas Pospisek
you wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922431#10:
>> On Fri, Feb 15, 2019 at 2:54 PM Sebastien Helleu wrote:
>> With chromium version 72.0.3626.81, the URL chrome://tracing does not
>> work any more.
>
> implementation relies on many sourceless javascript files.
>
> Best wishes,
> Mike
JS files.
Would it be possible to list (or give an example of) JS files, that are
missing source code? Maybe upstream can help if they know what file you
are referring to?
Thanks,
*t
[1] https://github.com/GoogleChrome/lighthouse/issues/7246#issuecomment-485432683)
Sascha Wolke
any changes on this? The tracing and the auditing tools are very helpful
in website/webapps development. Would be nice to get them working again.
@mike: If any help to find the sources is required, just name them and i
am going to find them.
Thanks
Sascha
Michael Gilbert
> @mike: If any help to find the sources is required, just name them and i
> am going to find them.
stripped out of the debian source package.
Best wishes,
Mike
Andrew Stone
> The sourceless files are in third_party/catapult/tracing, which is now
> stripped out of the debian source package.
Connor Clark
https://github.com/GoogleChrome/lighthouse/issues/7246#issuecomment-548015096