Hi, do you have the acl package installed? Because the suggested udev rule makes use of ACLs. And after adding the udev rule you probably need to restart because it only triggers on activating the device.
So yes, the documentation could be better for the steps needed, and we'll think about improving that. Personally I'm not too keen on adding an additional dependency on the acl package, no matter how useful it is. The main reason for the update was to get the security issues fixed, and given the state of the release making it extra comfortable for end users to get it working for regular users instead of only for root wasn't the priority. I hope you can understand that. Rhonda On 2/20/19 8:36 AM, jim_p wrote: > Package: beep > Version: 1.4.3-1 > Followup-For: Bug #922667 > > Dear Maintainer, > > I tried adding my user to the beep group, but nothing changed. Then I read > everything in /usr/share/doc/beep/INSTALL.md and here are my thoughts, > > Before adding my user to the beep group, I had to create that group. I did > that, but still no beep. Why? > > Because before making the group, I had to make the relevant udev rule. I > created it too, I rebooted, bust still no beep. Why? > > Because I also had to change the device permissions, but I have no idea how to > to that. I tried whatever is suggested in the instructions but all I get is > this bit > > # ls -lH /dev/input/by-path/platform-pcspkr-event-spkr > crw-rw---- 1 root input 13, 67 Feb 20 09:00 > /dev/input/by-path/platform-pcspkr- > event-spkr > > # 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::--- > > Maybe I am doing something wrong. But I think most, if not all, of this stuff > can be ommited if you provide the udev rule, make the group and change the > device permissions upon the install of the package. > On top of that, I think all that setup is a tedius job for something that, for > me at least, is used for a few milliseconds each time (I use beep to make an > audible notification for when transmission-daemon completes a download). The > 1.3.x version was literally plug-n-play, because, after installing it, I could > use pcspkr with it instantly, with no extra setup at all. > > > > -- 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-7 > > beep recommends no packages. > > beep suggests no packages. > > -- no debconf information >
