Hi,
Am 21.10.22 um 21:23 schrieb Thorsten Glaser:
On Fri, 21 Oct 2022, Rene Engelhard wrote:
Maybe time to get hardware from this or last century even?
Excuse me! That’s so totally not acceptable.
Debian runs on such machines, and I personally also have an EeePC,
and, to reduce electronic wa
On Fri, 21 Oct 2022, Rene Engelhard wrote:
> Maybe time to get hardware from this or last century even?
Excuse me! That’s so totally not acceptable.
Debian runs on such machines, and I personally also have an EeePC,
and, to reduce electronic waste, reusing of older machines is
perfectly fine. So
Am Fri, 21 Oct 2022 15:21:11 +0200
schrieb Rene Engelhard :
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 t
Processing commands for cont...@bugs.debian.org:
> found 1022173 1:7.0.4-4+deb11u3
Bug #1022173 [libreoffice] Arbitrary and frequent 100% CPU load symptom with
Libreoffice Writer 1:7.0.4
Bug #964549 [libreoffice] libreoffice: 100% CPU with LibreOffice
Marked as found in versions libreoffice/1:7.0
Processing commands for cont...@bugs.debian.org:
> reassign 1022173 libreoffice
Bug #1022173 [libreoffice-writer] Arbitrary and frequent 100% CPU load symptom
with Libreoffice Writer 1:7.0.4
Bug reassigned from package 'libreoffice-writer' to 'libreoffice'.
No longer marked as found in versions l
Processing commands for cont...@bugs.debian.org:
> severity 1022173 minor
Bug #1022173 [libreoffice-writer] Arbitrary and frequent 100% CPU load symptom
with Libreoffice Writer 1:7.0.4
Severity set to 'minor' from 'important'
> forcemerge 964549 1022173
Bug #964549 [libreoffice] libreoffice: 100%
severity 1022173 minor
forcemerge 964549 1022173
thanks
Hi,
Am 21. Oktober 2022 14:39:13 MESZ schrieb Robin :
>Looks possibly like a regression of a bug reported in 2020 already for an
>older Libreoffice release:
>#964549
Well, that one never was handled at all, actually. It's open still.
L
Processing commands for cont...@bugs.debian.org:
> notfound 1022173 1:7.0.4-4+deb11u3_bpo10+1
Unknown command or malformed arguments to command.
> found 1022173 1:7.0.4-4+deb11u3
Bug #1022173 [libreoffice-writer] Arbitrary and frequent 100% CPU load symptom
with Libreoffice Writer 1:7.0.4
Marked
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 :
>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
Th
Originally I've written:
“—When Libreoffice is ideling in its document selection launch (where you can
select previously used documents from a screen) without a document being opened
in one of its components, this issue doesn't happen at all.”
This is not true as I found out meanwhile. True is i
Package: libreoffice-writer
Version: 1:7.0.4-4+deb11u3_bpo10+1
Severity: important
When editing a Document in Libreoffice everything is fine, even when it's a
very large document > 150 pages and this lasts some hours. But the behaviour
described below is independent of document size.
When minim
11 matches
Mail list logo
