Re: Bug#1006187: bullseye-pu: package espeakup/0.80-20+deb11u1

[Cyril Brulebois]

Samuel Thibault  (2022-03-14):
> No because in d-i espeakup is started by hand, the systemd service file
> is not installed in the .udeb.
> 
> d-i doesn't usually start large amounts of process in parallel so it's
> not a problem there.

No objections anyway, thanks.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Bug#1006187: bullseye-pu: package espeakup/0.80-20+deb11u1

[Samuel Thibault]

Adam D. Barratt, le lun. 14 mars 2022 20:19:02 +, a ecrit:
> Control: tags -1 + confirmed d-i
> 
> On Sun, 2022-02-20 at 21:35 +0100, Samuel Thibault wrote:
> > Users have reported that when they are building large packages in
> > parallel, or generally loading the system a bit, the espeakup screen
> > reader becomes very laggy. This is because espeakup gets scheduled
> > only along other the parallel processes. Worse, if the system goes
> > OOM, espeakup might get killed by the OOM killer.
> > 
> > This is not a regression with respect to previous releases.
> > 
> > In the case of the brltty screen reader, we fixed this by making
> > brltty niced to -10 and its OOM score set to -900.
> 
> Does this have any impact on the udeb?

No because in d-i espeakup is started by hand, the systemd service file
is not installed in the .udeb.

d-i doesn't usually start large amounts of process in parallel so it's
not a problem there.

Samuel

Re: Bug#1006187: bullseye-pu: package espeakup/0.80-20+deb11u1

[Adam D. Barratt]

Control: tags -1 + confirmed d-i

On Sun, 2022-02-20 at 21:35 +0100, Samuel Thibault wrote:
> Users have reported that when they are building large packages in
> parallel, or generally loading the system a bit, the espeakup screen
> reader becomes very laggy. This is because espeakup gets scheduled
> only along other the parallel processes. Worse, if the system goes
> OOM, espeakup might get killed by the OOM killer.
> 
> This is not a regression with respect to previous releases.
> 
> In the case of the brltty screen reader, we fixed this by making
> brltty niced to -10 and its OOM score set to -900.
> 

Does this have any impact on the udeb?

Regards,

Adam