Control: tag -1 - upstream Control: severity -1 normal Hi.
On 2/19/19 6:46 AM, jim_p wrote: > After today's upgrade to version 1.4.x, beep no longer works and pops the > above > error. After checking its man page, I found out that it tries to access these > devices, in that specific order > > /dev/input/by-path/platform-pcspkr-event-spkr > /dev/tty0 > /dev/vc/0 > > and although I have the 1st one (the pc speaker), beep does not seem to be > able > to access it. > If I am correct. from the new developer's page in github, I found out that > there is this udev rule that needs to be present. > > https://github.com/spkr-beep/beep/blob/master/90-pcspkr-beep.rules > > If so, please add the above udev rule to your package. I would suggest to install the apt-listchanges package and/or read the NEWS file that I added specifically about this. For a start, this is not an upstream bug, it's a packaging decision. Secondly, it doesn't render the package unusable, it can be used by root without any troubles. I'm not totally convinced that I want (or should) add the udev rule. It's on admin discretion to do so. I might consider it though. I will have to update the package due to build error on arm64 anyway. Will locally try it out, but I'll discuss it first with others if that is a reasonable approach, permission wise. Thanks for understanding, Rhonda
