group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1654008@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package update-manager - 1:16.10.9

---------------
update-manager (1:16.10.9) yakkety; urgency=medium

  * Use a 64 bit integer for launch-time instead of a 32 bit one which won't
    work someday. (LP: #1654008)

 -- Brian Murray <brian@xxxxxxxxxx>  Fri, 17 Mar 2017 15:41:35 -0700

** Changed in: update-manager (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

** Changed in: update-notifier (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1654008

Title:
  /usr/bin/update-manager:OverflowError:/usr/bin/update-manager@117

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Fix Released
Status in update-notifier source package in Trusty:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in update-notifier source package in Xenial:
  Fix Released
Status in update-manager source package in Yakkety:
  Fix Released
Status in update-notifier source package in Yakkety:
  Fix Released
Status in update-manager source package in Zesty:
  Fix Released
Status in update-notifier source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  The launch-time key is only designed to hold a 32 bit integer and some day that won't work.  Additionally, a lot of people (based off the quantity of crash reports) seem to have their clocks misconfigured (or are living in the future!) which is causing a crash when update-manager tries to write the last launch time.

  [Test Case]
  1) In a terminal run 'faketime -f '+43y' /usr/bin/update-manager'.
  2) Observe a traceback

  With the version of update-manager from -proposed you will no longer
  receive a traceback.  The update-notifier change just supports reading
  the 64 bit integer key and there are no crashes yet because its not
  trying to read a 64 bit as 32 bits.

  [Regression Potential]
  Its possible the breaks and depends are incorrect and that people would receive a crash trying to read a 64 bit key as 32 bits. So double check those carefully.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager.  This problem was most recently seen with package version 1:16.10.8, the problem page at https://errors.ubuntu.com/problem/6d5b9fd57622f69dc32248c49512ee8fe29b24b3 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-manager/+bug/1654008/+subscriptions