On Wed, 26 Jan 2022 03:50:53 +0200 Spiky Caterpillar wrote:
>
> Chromium complains about stack smashing whenever started. I'm
starting it from
> an xterm, and the output when starting to a blank tab with Google as
the search
> engine is:
>
> [122740:122740:0126/025300.330856:ERROR:gpu_init.cc(457)] Passthrough
is not supported, GL is disabled, ANGLE is
> [122696:122727:0126/025301.818616:ERROR:nss_util.cc(286)] After
loading Root Certs, loaded==false: NSS error code: -8018
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
>
[122696:122727:0126/025304.329684:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
>
[122696:122727:0126/025304.329873:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
> *** stack smashing detected ***: terminated
The stack smashing errors are related to building with the clang-11
compiler; the reason you don't see them with unstable's version of
chromium is because unstable uses clang-13. Similarly, upstream google's
chromium builds against some clang-14 pre-release. I could disable stack
protection from the stable builds of chromium, but stack protection
could potentially be useful for actual security bugs. So for now, I'm
planning to just leave it enabled and ignore the messages.
At some point, it is likely that clang-13 will be backported to stable
(similar to how clang-11 was backported to oldstable, which allowed
firefox-esr to use it instead of oldstable's clang-7). Once that
happens, I plan to use clang-13 for building chromium in stable, and the
messages will go away.
> [122448:122448:0126/025217.558330:ERROR:gpu_init.cc(457)] Passthrough
is not supported, GL is disabled, ANGLE is
> [122405:122461:0126/025219.779173:ERROR:nss_util.cc(286)] After
loading Root Certs, loaded==false: NSS error code: -8018
>
[122405:122432:0126/025221.869024:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
>
[122405:122432:0126/025221.869057:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
> *** stack smashing detected ***: terminated
>
[...]
> hole - and the fact that they appear linked to third-party network
service
> integration makes them seem a bit ominous.
The nss_util.cc error is unrelated to the stack smashing errors, and
it's also one that I haven't seen before. It's pretty odd; it's from
LoadNSSModule("Root Certs", "libnssckbi.so", nullptr) failing to load
that library. I see that you have libnss3 (from stable) installed, so
I'm wondering what's going on. That error is coming from libnspr4
(PR_GetError), and I couldn't find it in the source code but I did find
it on a mozilla developer webpage as SEC_ERROR_UNKNOWN_PKCS11_ERROR. It
seems to say that it's failing to load a certificate, so maybe there's
something wrong your root certificates? I'm not entirely sure where it's
finding the root certificates, they might be built into the nss3 library
or they might be in /etc/ssl/certs/.
Do you have the ca-certificates package installed? Does https work
normally in the browser?
