Re: Bug#1022173: Arbitrary and frequent 100% C PU load symptom with Libreoffice Writer 1:7.0.4

notfound 1022173 1:7.0.4-4+deb11u3_bpo10+1
found 1022173 1:7.0.4-4+deb11u3
tag 1022173 + moreinfo
thanks

Am 21. Oktober 2022 14:39:13 MESZ schrieb Robin <[email protected]>:
>Package: libreoffice-writer
>Version: 1:7.0.4-4+deb11u3_bpo10+1

No. You even say the correct version below:

1:7.0.4-4+deb11u3~bpo10+1

The _ is just because the UI displays the ~ wrongly.

In a related note, read the docs. https://backports.debian.org/Instructions/ clearly says:

"Report Bugs

Please report bugs in backported packages to the backports mailing list and NOT to the Debian BTS!
"


>CPU threads: 1; 
(...)
> $ lscpu
> Architecture: i686
> CPU op-mode(s): 32-bit
> Byte Order: Little Endian
> Address sizes: 32 bits physical, 32 bits virtual
> CPU(s): 1
> On-line CPU(s) list: 0
> Thread(s) per core: 1
> Core(s) per socket: 1
> Socket(s): 1
> NUMA node(s): 1
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 13
> Model name: Intel(R) Pentium(R) M processor 1.73GHz

Wow.
Maybe time to get hardware from this or last century even?

>$ lsb_release -a
>No LSB modules are available.
>Distributor ID:	Debian
>Description:	Debian GNU/Linux 10 (buster)
>Release:	10
>Codename:	buster

Buster is out of life. 

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?

(Btw, you want to upgrade to deb11u4 backport whenever it is approved immediately to fix a security bug)
Regards

Rene
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.