Am Fri, 21 Oct 2022 15:21:11 +0200 schrieb Rene Engelhard <r...@debian.org>:
Hello Rene, sorry for having sent this report to the wrong listing. I followed the instructions found here: https://www.debian.org/Bugs/Reporting there was nothing mentioned about different treatment for backports at all, and I'm not that experienced in bug reporting. >Let's merge them since the description sounds familiar enough. Please feel free to assign, move or merge with whatever you consider to be appropriate. >Wow. I have no other system running besides this old but fast 32bit notebook, which is still absolutely fit and fine for everyday work (I'm not compiling or programming, being translator, not programmer). It is even fit for gimp image manipulation of large images, or dual head multimedia display up to 3000kbps and surfing the web fast and fluently, you'd not guess its age. > Buster is out of life. I know, but I'm running LTS until June 2024 on this notebook, since some of its hardware components are not supported properly in bullseye anymore by the drivers. Somebody decided to remove the needed code. > Does it still happen with bullseye? (Assume so since the buster-backports > version is built from bullseye) > Does it happen with the version in bullseye-backports? I'll check this both as soon as possible. Will have to setup a parallel bullseye install here first for testing. Then I can definitely state whether it happens with the non backported bullseye version of Libreoffice also. Maybe I can even run a test on bookworm, but I'm not sure by now whether and when I can free up some time for all this testing in OS versions I have not running or even installed here. > (Btw, you want to upgrade to deb11u4 backport whenever it is approved > immediately to fix a security bug) Many thanks for this security warning, I'll watch out, as always, for the update. Regards Robin
