From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: hdajackretask doesn't check for script's exit code
Date: Mon, 6 Sep 2021 09:17:06 +0200 (CEST) [thread overview]
Message-ID: <20210906071706.3FD92F802E7@alsa1.perex.cz> (raw)
In-Reply-To: <1630912623498121023-webhooks-bot@alsa-project.org>
alsa-project/alsa-tools issue #8 was edited from kroq-gar78:
`hdajackretask` creates a script in `/tmp` before executing it. When `/tmp` is mounted with `noexec`, running that script will fail, but the GUI gives no indication that it failed.
I'm on Ubuntu 18.04.5 with `alsa-tools-gui` package version `1.1.3-1`.
The GUI should check for the exit code of the script, and notify the user appropriately if the script failed to execute.
Also, if this isn't the appropriate place to report a bug, please let me know!
Issue URL : https://github.com/alsa-project/alsa-tools/issues/8
Repository URL: https://github.com/alsa-project/alsa-tools
next parent reply other threads:[~2021-09-06 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1630912623498121023-webhooks-bot@alsa-project.org>
2021-09-06 7:17 ` GitHub issues - edited [this message]
[not found] <1630912631652252913-webhooks-bot@alsa-project.org>
2021-09-06 7:17 ` hdajackretask doesn't check for script's exit code GitHub issues - edited
[not found] <1630912346745320082-webhooks-bot@alsa-project.org>
2021-09-06 7:12 ` GitHub issues - opened
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210906071706.3FD92F802E7@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).