This bug was fixed in the package busybox - 1:1.30.1-4ubuntu6.3
---------------
busybox (1:1.30.1-4ubuntu6.3) focal; urgency=medium
* cherry-pick settimeofday for glibc v2.31+ compatibility fix for upstream
(LP: #1888543)
-- Balint Reczey <rbal...@ubuntu.com> Wed, 11 Nov 2020 13:15:02 +0100
** Changed in: busybox (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: busybox (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1888543
Title:
hwclock: fails to set time on glibc 2.31
Status in busybox package in Ubuntu:
Fix Released
Status in busybox source package in Focal:
Fix Released
Status in busybox source package in Groovy:
Fix Released
Status in busybox package in Debian:
Confirmed
Bug description:
[Impact]
* With glibc 2.31, hwclock from busybox is unable to set the system time
due to the changes in settimeofday behavior.
[Test Case]
* Run:
sudo busybox hwclock -s
* It should succeed in the fixed version
[Where problems could occur]
* The fix calls the originally called glibc function twice, instead of
passing both non-NULL parameters at once. If this compiles there should be no
other issue.
[Original Bug Text]
With glibc 2.31, hwclock from busybox is unable to set the system time
due to the changes in settimeofday behavior.
The problem has been reported upstream in [1] which also contains a
patch.
hwclock from busybox is important as it's used on the Raspberry Pi to set the
system
time when an RTC is present.
This bug applies to focal and groovy.
[1] https://bugs.busybox.net/show_bug.cgi?id=12756
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
