Package: beep Version: 1.4.3-2 Followup-For: Bug #922667 Dear Maintainer,
First of all, as soon as the package was updated to 1.4.3-2, I removed the upstream udev rule and let it use the provided one. I see there is a small difference between them, but I can not explain what that change actually does. The problem is that that difference, imho, makes beep partialy broken. It does work... most of the time, so let me mention my use cases in which it does not work. a) As I have said above, I mainly use beep as an audible notification for transmission-daemon. The user debian-tranmission is on the beep group as seen below $ id debian-transmission uid=110(debian-transmission) gid=110(debian-transmission) groups=110(debian- transmission),999(beep) but no beep is heard when it is supposed to. b) Executing beep as a regular user, who is in the beep group obviously, works... if the user is logged in locally. Executing it as a the same user, connected via ssh, still pops up the "could not open any device" error and getfacl reports the same as above for the ownership stuff # getfacl /dev/input/by-path/platform-pcspkr-event-spkr getfacl: Removing leading '/' from absolute path names # file: dev/input/by-path/platform-pcspkr-event-spkr # owner: root # group: input user::rw- group::rw- other::--- Both these issues are completely solved when using the upstream udev rule, so I think your rule needs some fixing. Thanks for listening :) p.s. mini rant: I also noticed that the updated package still does not make the beep group, so it is one more step for the user to do. Other packages do that all the time (that's why I still have a debian-tor group although I have removed removed torbrowser ~2 years ago), so I don't think it will be hard or pointless to have a beep group as well. Special groups are mandatory for various reasons. And, because I had a small discussion about it with a fellow (and more advanced) debian and beep user, if you consider a "security flaw" to have beep running as a non-root user, why package beep at all? Plus, if I have to do all that stuff by hand in order to make it "simply" work, why do I still have debian and not gentoo (or arch at the very least)? -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages beep depends on: ii libc6 2.28-8 beep recommends no packages. beep suggests no packages. -- no debconf information
