this issue persist jason@server03:~$ pgrep check-new-re 765 1925 1952 3852 4072 5238 5467 5646 6464 6753 9409 12877 14336 15288 16599 17057 18756 20018 20029 20174 20255 20726 22315 22523 22855 24292 24876 25964 26093 27981 28489 29387 30350 32556 jason@server03:~$ pgrep check-new-re | wc -l 34 jason@server03:~$ ps -ef | grep check-new-re root 765 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 1925 1 0 Feb04 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 1952 1 0 Mar11 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 3852 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 4072 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5238 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5467 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 5646 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 6464 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 6753 1 0 Jan21 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 9409 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 12877 1 0 Feb25 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 14336 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 15288 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 16599 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 17057 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 18756 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20018 1 0 Mar18 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20029 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20174 1 0 Jan28 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20255 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 20726 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22315 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22523 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 22855 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 24292 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 24876 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 25964 1 0 Jan14 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 26093 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 27981 1 0 Mar04 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 28489 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 29387 1 0 Feb18 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 30350 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q root 32556 1 0 2017 ? 00:00:00 /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q every week it runs and leaves behind another process, this is crazy. What is causing this bug, and how do I fix it?