Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#69424 - [brltty] Update 6.2 breaks dracut with 'brltty-lsinc: missing file' errors

Attached to Project: Arch Linux
Opened by Alexander Michalopoulos (Nocifer) - Sunday, 24 January 2021, 12:42 GMT
Last edited by David Runge (dvzrv) - Wednesday, 05 May 2021, 10:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Waiting on Response   Reopened
Assigned To David Runge (dvzrv)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 5
Private No

Details

As of version 6.2, rebuilding the initramfs with dracut results in the following:

dracut: *** Including module: brltty ***
brltty-lsinc: missing file
brltty-lsinc: cannot open file: /etc/brltty/Input/al/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/bm/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/bn/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/cn/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/eu/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/fs/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hd/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hm/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/ht/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hw/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/ic/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/mt/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/pg/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/pm/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/sk/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/vo/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/md/*.ktb: No such file or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/mm/*.ktb: No such file or directory

The "missing" files can all be found at /usr/share/brltty/Input/ instead.
This task depends upon

Comment by Xuanrui Qi (xuanrui) - Monday, 25 January 2021, 18:57 GMT
I do not know if this related, but if I boot using dracut, I get syntax errors in /usr/lib/dracut/hooks/cmdline/05-brltty-start.sh, and I couldn't boot my system anymore.
Comment by David Runge (dvzrv) - Tuesday, 26 January 2021, 22:57 GMT
@Nocifer: Thanks for the report. I have just pushed 6.2-4, which removes the dracut support again.

It would be immensely helpful if you and @xuanrui could help testing the functionality for an upcoming (upstream) release.
I'm not sure yet whether the dracut integration will live in a split package or how it is best handled, but I'll surely move the package to testing first. May I ping you then to try it?
Comment by Júlio Dutra (dutrajulio) - Tuesday, 26 January 2021, 23:36 GMT
The upstream package solved some weird messages during the boot process.
Comment by Alexander Michalopoulos (Nocifer) - Wednesday, 27 January 2021, 10:45 GMT
@dvzrv Sure, I'd be happy to help. Just hit me up when you need to.
Comment by David Runge (dvzrv) - Thursday, 28 January 2021, 20:11 GMT
@Nocifer, @xuanrui (and anyone else interested in testing): brltty 6.3-1 is in [testing] now.
Please give it a spin and report back, if the issues are resolved.
Comment by Alexander Michalopoulos (Nocifer) - Friday, 29 January 2021, 11:29 GMT
Alright, I just tested 6.3-1. Dracut didn't complain when building the initramfs, but on reboot I got the following errors:

dracut-pre-pivot: brltty: kernel module not installed: uinput
dracut-pre-pivot: brltty: pid file open error: /run/brltty.pid: No such file or directory
...
dracut-cmdline: brltty: kernel module not installed: uinput

The error about uinput is easily fixed by adding

add_drivers+=" uinput "

to /usr/share/brltty/Initramfs/cmdline; the PID error is probably not something I can control from my side.
Comment by Alexander Michalopoulos (Nocifer) - Friday, 29 January 2021, 12:01 GMT
OK, scratch the above:

At first, when I had brltty complain about uinput missing, I actually added it through a .conf file in /etc/dracut.conf.d/ rather than through /usr/share/brltty/Initramfs/cmdline.

Afterwards, I discovered the existence of /usr/share/brltty/Initramfs/cmdline, and I made the previous comment before proceeding to move uinput's inclusion from the former file to the latter one, being certain that the behavior would be the same. Well... no. I got the following error on reboot (along with the one about the PID):

dracut-cmdline: //lib/dracut/hooks/cmdline/05-brltty-start.sh: line 33 error


I then removed add_drivers+=" uinput " from /usr/share/brltty/Initramfs/cmdline and the new error disappeared... but the error about uinput missing did not come back! So now I can build the initramfs seemingly without uinput included, and no errors are produced. The only error I've been getting in all cases is the one about the PID file.

So either I'm doing something wrong (possible, since dracut is something new to me) or there's something weird going on here.
Comment by Júlio Dutra (dutrajulio) - Friday, 29 January 2021, 16:49 GMT
Building the initramfs are now showing the "no such file or directory" messages. The system is bootable but, using plymouth, the splashscreen flick and show the following messages:

dracut-cmdline[338]: BRLTTY 6.3 rev BRLTTY-6.3 [http://brltty.app/]
dracut-cmdline[338]: brltty: executing as the invoking user: root

The shutdown stucks some time waiting for the brltty process ends.
Comment by David Runge (dvzrv) - Wednesday, 03 February 2021, 19:35 GMT
Many thanks for testing!
I believe the remaining issues should be cleared up with upstream.
I'm relieved to hear that booting is not broken using dracut anymore :)
Comment by rootpeer (rootpeer) - Wednesday, 05 May 2021, 09:27 GMT
This is not fixed. The /etc/brltty directory is still missing.

This breaks booting with encrypted zfs. brltty, which is now a dependency of qemu, never starts so the password prompt for the encryption never shows and the system fails to boot.

Probably the same happens with LUKS.
Comment by David Runge (dvzrv) - Wednesday, 05 May 2021, 10:10 GMT
@rootpeer: Well, the directory below /etc/brltty is not supposed to be there. That is the point.

Also: brltty has been a dependency for qemu for *a long time* and I fail to see what this has to do with dracut boot issues.

Please provide information on what exactly is the output that you are seeing. If it is not the same as the output described by @Nocifer please open a new ticket. However, please note that ZFS is not supported.
Comment by Nickolay (neothefox) - Wednesday, 30 June 2021, 15:02 GMT
It is trivial to avoid brltty entirely by simple adding
omit_dracutmodules+=" brltty "
to dracut configuration.
Comment by Daniel Gray (dngray) - Monday, 12 July 2021, 08:10 GMT
> This breaks booting with encrypted zfs. brltty, which is now a dependency of qemu, never starts so the password prompt for the encryption never shows and the system fails to boot.

I use LUKS. The password prompt does appear, though I do see "
dracut-cmdline[338]: BRLTTY 6.3 rev BRLTTY-6.3 [http://brltty.app/]", so I doubt that is the same issue.

> The shutdown stucks some time waiting for the brltty process ends.

I do get hangs on shut down, and uninstalling qemu, and it's dependency brltty, made the problem go away as does: omit_dracutmodules+=" brltty "

Loading...