See https://github.com/spkr-beep/beep/blob/master/PERMISSIONS.md. Due to recent security bugs, beep now aborts immediately if run setuid or setgid:
beep: Error: Running setuid or setgid, which is not supported for security reasons.
beep: Error: Set up permissions for the pcspkr evdev device file instead.
(and it exits with status 1)
I'm not sure which upstream version introduced this change, but I encountered it after upgrading from app-misc/beep-1.3-r3 to 1.4.9. The ebuild for 1.4.9 still supports the suid USE flag, and sets the setuid bit on the binary if the USE flag is enabled.
At a bare minimum it should drop that support and stop setting setuid/setgid.
An even better solution would be if the ebuild optionally setup a "beep" group (or call it whatever) and the device permissions, as recommended on that PERMISSIONS.md page, so that the end user wouldn't have to do all that manually.
As Michael stated, the replacement for "suid" USE flag is an appropriate udev rule file.
The package upstream even suggests a few.
The bug has been closed via the following commit(s):
Author: Alessandro Barbieri <firstname.lastname@example.org>
AuthorDate: 2021-02-22 01:02:52 +0000
Commit: Michał Górny <email@example.com>
CommitDate: 2021-09-23 08:17:03 +0000
app-misc/beep: capabilities added, suid removed
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Alessandro Barbieri <firstname.lastname@example.org>
Signed-off-by: Michał Górny <email@example.com>
app-misc/beep/beep-1.4.9-r1.ebuild | 57 ++++++++++++++++++++++++++++++++++++++
1 file changed, 57 insertions(+)