-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
beep fails, but exits 0 (unless strace'd) #8
Comments
Afair you can't debug/strace a setuid as non-root |
Do not run beep as setuid-root or via sudo-root. See #11 for details. In January 2019, I have changed beep to prioritize the new speaker API which does not require setuid-root or sudo-root, fixed the bugs from #11 and others, and published the updated code on https://github.com/spkr-beep/beep where release 1.4.4 is current. A number of distributions are using the new code base at this time: Arch Linux, Debian unstable, Fedora 28 and later, Ubuntu whatever-is-tracking-Debian-unstable. Please update to beep-1.4 or later, and if the problem persists, you can run a proper Your problem might just be the hardware audio mixer input for the PC speaker (going to your laptop speakers) being turned to 0. |
gzip embeds a timestamp in the compressed data unless the --no-name parameter is used. We are merging this to record it in the history, but will stop compressing the man page at all so that distribution packages can use their respective favoured compression format.
Not sure how to debug this yet, so I'm just providing some info that I'm guessing is at least bug worthy: the exit status should be non-zero, I believe (as you can see errors occur, via
strace
)beep
itself:$ beep -v beep-1.3 $ beep # exits 0, no sound
strace
d, changes exit status:Some more info, in case it's helpful:
The text was updated successfully, but these errors were encountered: