[Bug 1640318] Please test proposed package

Timo Aaltonen tjaalton at ubuntu.com
Fri Dec 9 11:04:26 UTC 2016


Hello errors.ubuntu.com, or anyone else affected,

Accepted update-notifier into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.168.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1640318

Title:
  /usr/lib/update-notifier/package-data-
  downloader:OSError:process_download_requests:/usr/lib/update-notifier
  /package-data-
  downloader at 305:process_download_requests:print_exc:print_exception

Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-notifier source package in Xenial:
  Fix Committed
Status in update-notifier source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ------
  Crash reports are being generated when update-notifier is trying to print a message which isn't really necessary to print.  This crash its reporting process is wasting resources of users and the Error Tracker.

  Test Case
  ---------
  We haven't figure out exactly how the crash is happening but given the volume of errors which we are receiving we can verify it the crash is no longer occurring by checking the errors bucket in this bug report after a couple of weeks.

  Regression Potential
  --------------------
  Its possible that there is something terrible causing stdout to disappear and that we are hiding that by no longer printing when it isn't there.  However, there is insufficient information in the crash reports to sort out why its not available and we'd rather conserve resources by not causing the crashes.

  Original Description
  --------------------
  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier.  This problem was most recently seen with package version 3.172, the problem page at https://errors.ubuntu.com/problem/140b42227c613c32a42f8ad1d4537e8f3dd82dc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1640318/+subscriptions



More information about the foundations-bugs mailing list