** Description changed: + [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/.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654008 Title: /usr/bin/update-manager:OverflowError:/usr/bin/update-manager@117 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1654008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
