I think the script will still work most of the time so severity is not
too high.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870824
Title:
Errors in script
Public bug reported:
In line 42 and 46 Command Substitution is used wrongly because the shell
expects to execute what it returns. See attached patch.
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "Patch that fixes the two errors"
@Julian I had considered that. This could be more easily done with
"on_ac_power || return 1" - there is no need for full "if...then...fi".
But both those solutions would have different semantics than what the
script _apparently_ intends to do: on_ac_power returns 0 on AC, 1 on
battery and 255 if
I forgot to mention one thing about the patch: the current behavior is
that when on_ac_power returns 255 the current version of the script
returns with that non zero error code and does not execute
/usr/lib/apt/apt.systemd.daily. The patched version will execute
/usr/lib/apt/apt.systemd.daily and
** Patch added: "Suggested patch to fix"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+attachment/5034117/+files/apt-compat-3.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Produces this output:
$ sh check_power_test.sh
+ echo begin
begin
+ check_power 0
+ exit 0
+ return 0
+ check_power 1
+ exit 1
+ [ 1 -ne 1 ]
+ return 1
+ echo ignore
ignore
+ check_power 255
+ exit 255
+ [ 255 -ne 1 ]
+ return 0
+ echo end
end
** Attachment added: "Demonstration of behavior of
Public bug reported:
I accidentally stumbled across this. If in line 22 on_ac_power returns a
non zero exit code the next line is never reached. Instead, the shell
terminates immediately with that non zero exit code because of "set -e"
in line 3. In this script it does not pose a problem because
Not sure whether I am also affected - at least I see the same errors in
.xsession-errors:
openConnection: connect: No such file or directory
cannot connect to brltty at :0
upstart: upstart-event-bridge main process (6906) terminated with status 1
upstart: upstart-event-bridge main process ended,
#23 that is actually the case with me. There is an issue in the Intel
video support that starts to annoy me. And I cannot install LTS
enablement stack to get a newer kernel so I need to upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is not a bug (see comment 3).
** Changed in: bash (Debian)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090293
Title:
Crash on using exec
To manage
The original description does not describe a bug. When doing exec echo
0 in a terminal, the shell's process will be replaced with a process
doing echo and after echo terminates the terminal also closes. This
behavior is as specified and as intended. That is not a crash.
The second description is
Information missing for this bug report. What does hang mean?
** Changed in: bash (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090293
Title:
Crash
12 matches
Mail list logo
