Closed mckaygerhard closed 8 months ago
after many test i cannnot reproduce it, desktop used for testing was KDE from debian 11..
I did many tests too, but I had not same problem.
My hypothesis is that message is by bash itself (it communicate to user about background process killed. To see it, you have to type Enter
and bash communicate you that.
If that is the case, we can't do anything about: it's normal bash behavior.
Unless anyone gives a suggestion... ;)
Other little tests done on this issue: my previous hypothesis
My hypothesis is that message is by Bash itself (it communicate to user about background process killed). To see it, you have to type Enter and bash communicate you that.
is correct.
Reason is that Bash tells to user that it has killed previous background process, its PID and its name. To "fix" this, you should to force Bash to be "quiet", e.g. redirecting StdErr to /dev/null, but I don't recommend it, especially for troubleshooting matter.
found a small error, only happened in older versions ooof zenity:
raised this:
but event using
${wait_for__PID}
it raised..there is no problem usinig kdialog or yad, dialog just send text and that's normal not tested with xdialog