Re: [erledigt] Re: Chromium lahmt seit dem letzten Update…
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Am Sonntag, den 05.07.2020, 10:07 +0200 schrieb Horst Felder:
> Danke für die Bestätigung, das es nicht an einem lokalen Problem lag…
>
> Zu meiner Freude konnte ich eben ein update einspielen (da es die
> gleiche Versionsnummer hat, aber alles wieder wie üblich funkt,
> vermute ich mal das beim compilieren was schief gegangen ist)…
>
> Ente gut, alles gut! :)
Als Ergänzung füge ich mal die passende Meldung von debian-security-announce
an. Kurzfassung - ja, es wurden ein paar Compileroptimierungen vergessen.
Meldung:
> -------------------------------------------------------------------------
> Debian Security Advisory DSA-4714-2 security@debian.org
> https://www.debian.org/security/ Michael Gilbert
> July 04, 2020 https://www.debian.org/security/faq
> -------------------------------------------------------------------------
>
> Package : chromium
> Debian Bug : 964145
>
> The previous update for chromium released as DSA 4714-1 was mistakenly
> built without compiler optimizations. This caused high CPU load and
> frequent crashes. Updated chromium packages are now available that
> correct this issue.
>
> For the oldstable distribution (stretch), security support for chromium
> has been discontinued.
>
> For the stable distribution (buster), this problem has been fixed in
> version 83.0.4103.116-1~deb10u2.
>
> We recommend that you upgrade your chromium packages.
>
> For the detailed security status of chromium please refer to
> its security tracker page at:
> https://security-tracker.debian.org/tracker/chromium
>
> Further information about Debian Security Advisories, how to apply
> these updates to your system and frequently asked questions can be
> found at: https://www.debian.org/security/
>
> Mailing list: debian-security-announce@lists.debian.org
- --
MfG Richi
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEERqPC1cUAShrzNBXW+NRy+KEKcZgFAl8B2VgACgkQ+NRy+KEK
cZjD0hAArfJ9urvMQhgaprtEpqqI6liWHD2K6ofMRuBFvNKYJ5ilnsVZ5t574UbA
pW43Dq40lzinJYqu/uRsSAe8Epq/FAu6zOCIMF3q87t3hjuwjvnPUVSImShy1cdn
LlSyguDtiPwszZSbiquEDvwVcotbCSgyZl+tD6STF+yzaTS22zdZl2ewKQKQro53
OZV84BE1cDZ545ohq9bxyQDoHZ+vuFzra7hyGFLABzmso1Wln3lxfgiyxgtVXC0Y
IvqvgmtCQkoYVyK1nB4j/EMdrQd4++8d9z5HtqEcsXjQ26IojvDmu93+4LyJFW1T
8966qaDU48bQPvQWFo31jIyz3CPYj0tbh0Qv7qGyMLR3kQoPbvPJY54QQSiG93w+
1KS7AhrB3FXSxoQcpiwT8SgNJu+AjX8GdDJzdkqoTgoFEFTQzdggSt4L5fbxSVdH
wK3MxjDvk7sRXD9YiFySTESnQR2B8wxNAYR01++rV4BoD6oF3Baq4X4FCdsURiLn
yihDzU18y8ShzQZR7ofp7w2o7TW6djlh/wEoNoUfjFvdp+9DTsChirFveu4vDEsk
Vkk8gb4NKZ1LKqI6xAtueaNhe3FKtNG+tEFYdRAjf3yRzZK3t51Teah1kjKBsQwa
/SqZuS3GIJz97gMZNakGOa/ZVdofu55u+3niPk4RtYSXfq5kyRM=
=eLjk
-----END PGP SIGNATURE-----
Reply to: