Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65492 - [glibc] [lib32-glibc] sleep: cannot read realtime clock: Invalid argument
Attached to Project:
Arch Linux
Opened by Hugo Ferreira (hferreira) - Friday, 14 February 2020, 00:26 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Monday, 17 February 2020, 06:39 GMT
Opened by Hugo Ferreira (hferreira) - Friday, 14 February 2020, 00:26 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Monday, 17 February 2020, 06:39 GMT
|
DetailsDescription:
After upgrading glibc to version 2.31-1 the sleep command started throwing out the error: sleep: cannot read realtime clock: Invalid argument Downgrading to the previous version "solves" the issue. Additional info: * package version: glibc-2.31-1 Steps to reproduce: Upgrade glibc to 2.31-1. Do a sleep 0 on the shell |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Monday, 17 February 2020, 06:39 GMT
Reason for closing: Works for me
Monday, 17 February 2020, 06:39 GMT
Reason for closing: Works for me
Comment by freswa (frederik) -
Friday, 14 February 2020, 00:32 GMT
Cannot reproduce. Can you please give us an `uname -a`?
Comment by Max Cole (wrvsrx) -
Monday, 17 February 2020, 01:23 GMT
It can be reproduced in WSL 1. Maybe it only happens in WSL.