Bug#922667: beep: Error: could not open any device

2019-03-12 Thread Rhonda D'Vine
Hey there. :) On 3/12/19 5:13 PM, jim_p wrote: > 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

Bug#922667: beep: Error: could not open any device

2019-03-12 Thread jim_p
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

Bug#922667: beep: Error: could not open any device

2019-02-23 Thread GSR
Package: beep Followup-For: Bug #922667 Before it worked fine via sound card speakers as normal user, now not even root can get beeps. I understand the user perms setup part being not done yet, but not why root fails too (the only difference is if it prints "Error: Could not open any device" or

Bug#922667: beep: Error: could not open any device

2019-02-21 Thread Hugh Morris
Hello I don't yet understand all the above, but I, too, was puzzled when my beeping scripts went silent. Hugh Morris

Bug#922667: beep: Error: could not open any device

2019-02-20 Thread jim_p
Package: beep Version: 1.4.3-1 Followup-For: Bug #922667 Dear Maintainer, The instructions did work after a cold boot, done several hours after writing the previous message. It seems a simple reboot was not enough :P I installed acl by hand because it was not already installed, not even as a

Bug#922667: beep: Error: could not open any device

2019-02-20 Thread Rhonda D'Vine
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

Bug#922667: beep: Error: could not open any device

2019-02-19 Thread jim_p
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

Bug#922667: beep: Error: could not open any device

2019-02-19 Thread Rhonda D'Vine
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 >

Bug#922667: beep: Error: could not open any device

2019-02-18 Thread jim_p
Package: beep Version: 1.4.3-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, 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