** Changed in: ubuntuwsl
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1871129
Title:
htop is blank when using in focal
rafaeldtinoco@wsl1:~$ sudo apt-mark hold libc6
libc6 set on hold.
rafaeldtinoco@wsl1:~$ dpkg -l libc6
hi libc6:amd642.31-0ubuntu8+lp1871129~1 amd64GNU C Library: Shared
libraries
Not sure how much time upstream will take to fix this bug, so make sure
to mark libc6 as "hold" so it
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1871129
Reminder: this is just a temporary workaround as we wait upstream fix.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
This is a "hotfix" for the issue. I'm preparing a PPA so people can use
it but it won't be the final fix. It is more likely that WSL1 will have
to support CLOCK_REALTIME eventually =).
** Patch added: "glibc_2.31-0ubuntu8+lp1871129~1.debdiff"
** Also affects: wsl (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wsl (Ubuntu)
Status: New => Confirmed
** Changed in: glibc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: htop (Ubuntu)
Status: Opinion => Invalid
** Changed in: htop (Ubuntu)
Commit to blame in glibc:
commit 3537ecb49cf7177274607004c562d6f9ecc99474
Author: Adhemerval Zanella
Date: Tue Nov 5 21:37:44 2019 +
Refactor nanosleep in terms of clock_nanosleep
The generic version is straightforward. For Hurd, its nanosleep
implementation is moved to
At our side we *could* change this clock from CLOCK_REALTIME to
CLOCK_MONOTONIC but =) that does not seem the right thing to do to
fix WSL1 because it does not behave properly with REALTIME clocks. Let's
wait upstream bug for now...
** Changed in: htop (Ubuntu)
Status: Confirmed =>
The issue is happening because WSL is currently not POSIX compliant and
any call to glibc that uses CLOCK_REALTIME will fail with EINVAL (-1)
(such as clock_gettime() or clock_nanosleep()). It is likely that a
glibc change has made this to appear (instead of the htop different
version).
Upstream