Bug#1035813: brltty: Fails to start on early boot

2023-05-14 Thread Sebastian Humenda
Hi

Samuel Thibault schrieb am 10.05.2023,  1:49 +0200:
>Sebastian Humenda, le mar. 09 mai 2023 15:53:05 +0200, a ecrit:
>> On my Debian Bookworm system, I've configured BRLTTY with speech output over
>> espeak-ng and a USB braille device. However, I am unable to use BRLTTY for my
>> password entry of my encrypted /home partition;
>
>Does it start after that?

Yes, it does. Sometimes even after lightdm has, with Orca, announced that a
password is required.

>> I've enabled the option that BRLTTY is pat of the initramfs, but I suspect it
>> is present, but not started. Is there any other action required?
>
>AFAIK all is needed is enabling it in /etc/default/brltty and running
>update-initramf -u (which prints "Installing BRLTTY into initramfs)

Yes, indeed.

>> I also think that the dependencies of BRLTTY prevent it from being started by
>> systemd at an earlier stage. I'm not familiar with the Systemd boot process,
>> but it could be related to requiring paths like /var/lib/brltty to be mounted
>
>Yes, the brltty service expresses that it needs /var/lib/brlty and
>BrlAPI. But that shouldn't be requiring /home/

Yes, but I thought that sysemd might order the mounts by some means which
would, just as an implementation detail, mount /home before it declares /var
to be present (unlikely though).

>I tried to install a system with an encrypted /home, and brltty does get
>started before the /home passphrase step. You can probably check
>journalctl and other systemd tools to see what is actually happening.

The flood of messages is a bit overwelming. The systemd unit of BRLTTY
(journalctl -u brltty) is obviously not helpful. To you suggest to read
/var/log/syslog from the boot on?

Thanks
Sebastian


signature.asc
Description: PGP signature


Bug#1035813: brltty: Fails to start on early boot

2023-05-09 Thread Samuel Thibault
Sebastian Humenda, le mar. 09 mai 2023 15:53:05 +0200, a ecrit:
> On my Debian Bookworm system, I've configured BRLTTY with speech output over
> espeak-ng and a USB braille device. However, I am unable to use BRLTTY for my
> password entry of my encrypted /home partition;

Does it start after that?

> I've enabled the option that BRLTTY is pat of the initramfs, but I suspect it
> is present, but not started. Is there any other action required?

AFAIK all is needed is enabling it in /etc/default/brltty and running
update-initramf -u (which prints "Installing BRLTTY into initramfs)

> I also think that the dependencies of BRLTTY prevent it from being started by
> systemd at an earlier stage. I'm not familiar with the Systemd boot process,
> but it could be related to requiring paths like /var/lib/brltty to be mounted

Yes, the brltty service expresses that it needs /var/lib/brlty and
BrlAPI. But that shouldn't be requiring /home/

> and /home just unfortunately being earlier.

There is no notion of "earlier" in systemd, just dependencies.

I tried to install a system with an encrypted /home, and brltty does get
started before the /home passphrase step. You can probably check
journalctl and other systemd tools to see what is actually happening.

Samuel



Bug#1035813: brltty: Fails to start on early boot

2023-05-09 Thread Sebastian Humenda
Package: brltty
Version: 6.5-7
Severity: important
Tags: a11y

Hi

On my Debian Bookworm system, I've configured BRLTTY with speech output over
espeak-ng and a USB braille device. However, I am unable to use BRLTTY for my
password entry of my encrypted /home partition; note that / is unencrypted.

I've enabled the option that BRLTTY is pat of the initramfs, but I suspect it
is present, but not started. Is there any other action required?
I also think that the dependencies of BRLTTY prevent it from being started by
systemd at an earlier stage. I'm not familiar with the Systemd boot process,
but it could be related to requiring paths like /var/lib/brltty to be mounted
and /home just unfortunately being earlier. In any case, it would be good to
still have a11y support for entering the pass-phrase, in particular, for cases
where something goes wrong.

Thanks

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages brltty depends on:
ii  init-system-helpers1.65.2
ii  libasound2 1.2.8-1+b1
ii  libbluetooth3  5.66-1
ii  libbrlapi0.8   6.5-7
ii  libc6  2.36-9
ii  libcap21:2.66-3
ii  libdbus-1-31.14.6-1
ii  libexpat1  2.5.0-1
ii  libglib2.0-0   2.74.6-2
ii  libgpm21.20.7-10+b1
ii  libicu72   72.1-3
ii  liblouis20 3.24.0-1
ii  libncursesw6   6.4-2
ii  libpcre2-32-0  10.42-1
ii  libpolkit-gobject-1-0  122-3
ii  libsystemd0252.6-1
ii  libtinfo6  6.4-2
ii  lsb-base   11.6
ii  policykit-1122-3
ii  polkitd122-3
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages brltty recommends:
ii  python3  3.11.2-1+b1

Versions of packages brltty suggests:
ii  brltty-speechd 6.5-7
ii  brltty-x11 6.5-7
pn  console-braille
pn  unicode-cldr-core  

-- Configuration Files:
/etc/default/brltty changed:
ARGUMENTS="-q"
START_IN_INITRAMFS=true


-- no debconf information