> Chromium complains about stack smashing whenever started. Versions of packages chromium-sandbox depends on: Versions of packages chromium-common recommends: Versions of packages chromium-common depends on: Versions of packages chromium recommends: Versions of packages chromium depends on:
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE not set Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) System Information (stable, shows bug):ĪPT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Integration makes them seem a bit ominous. Hole - and the fact that they appear linked to third-party network service Ordinarily I wouldn't bother reporting a bug that appears fixed in unstable,īut the stack smashing messages seem like they may be a sign of a security I'll include the system info for the unstable version in this message 99-1 (which pulls in an updated libc, among other I also don't see stack smashing messages if I switch to unstable and upgradeĬhromium to. Revision 963308, linux binary downloaded from 's recommended
I don't see stack smashing messages running Chromium 1.0 (Build The stack smashing messages go away when I upgrade to. If I set the default search engine to Debian, I get: (Note: I disabled hardware acceleration to see if it would make the stack More "*** stack smashing detected ***: terminated" lines. With Google as the default search engine, opening a new tab will give me two If you don't see the END: message, this is /1216328. *** stack smashing detected ***: terminated After loading Root Certs, loaded=false: NSS error code: -8018 Passthrough is not supported, GL is disabled, ANGLE is I'm starting it fromĪn xterm, and the output when starting to a blank tab with Google as the search X-Debbugs-Cc: complains about stack smashing whenever started.
0 kommentar(er)
