[Bug 1870824] Re: Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh
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 /usr/lib/avahi/avahi-daemon-check-dns.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1870824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870824] [NEW] Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh
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" https://bugs.launchpad.net/bugs/1870824/+attachment/5346540/+files/diff-1.patch -- 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 /usr/lib/avahi/avahi-daemon-check-dns.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1870824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24
@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 the power status cannot be determined. The current code of the script indicates that in this case /usr/lib/apt/apt.systemd.daily should be executed and _only_ be omitted if on_ac_power returns exactly 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742378 Title: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24
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 terminate with whatever exit code that process generates. On a side note, "which" can be replaced by "type" which is POSIX compatible and a shell built in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742378 Title: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24
** 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. https://bugs.launchpad.net/bugs/1742378 Title: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742378] Re: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24
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 the patch" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+attachment/5034118/+files/check_power_test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742378 Title: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742378] [NEW] Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24
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 the shell is asked to exit anyway if check_power() returns non zero but it works differently than is apparently intended (concluding from the logic). I will attach a suggest patch and a demo illustrating that the patch works as the original script seems to intend to. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742378 Title: Slight glitch in /etc/cron.daily/apt-compat Ubuntu 16.04.3 in apt-1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432317] Re: [systemd] should now depend on systemd/upstart, not upstart-bin
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, respawning upstart: upstart-event-bridge main process (6907) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6914) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6919) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6920) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6922) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6929) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6933) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6934) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6936) terminated with status 1 upstart: upstart-event-bridge main process ended, respawning upstart: upstart-event-bridge main process (6938) terminated with status 1 upstart: upstart-event-bridge respawning too fast, stopped This is Xubuntu 15.10: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily $ uname -a Linux babelfish 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Any ideas? Should I be reporting another issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432317 Title: [systemd] should now depend on systemd/upstart, not upstart-bin To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1432317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534374] Re: unable to upgrade to 15.04 due to libstdc++6 SRU
#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 Ubuntu. https://bugs.launchpad.net/bugs/1534374 Title: unable to upgrade to 15.04 due to libstdc++6 SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1534374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090293] Re: Crash on using exec
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1090293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090293] Re: Crash on using exec
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 very unclear. There is no console output and hangs could mean anything. If this describes a but it is certainly a different bug because crash != hangs and there is no process replacement involved. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1090293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090293] Re: Crash on using exec
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 on using exec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1090293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
