Barney Posted December 14, 2023 Posted December 14, 2023 I've installed Armbian 23.11.1 Bookworm on a FriendlyElec ZeroPi. On the cmdline the linux command who gives the following output: dgs pts/1 1011643795265722162 (172.20.10.14) Usually it should be (as on a Debian Bookworm distribution): dgs pts/0 2023-12-14 10:43 (172.20.10.14) Instead of showing date and time the Armbian who command outputs this long integer number. Why? Is this a bug or do I miss any configuration? PS: the locale settings is identical on both devices, date shows on both devices the correct time. 0 Quote
Gunjan Gupta Posted December 14, 2023 Posted December 14, 2023 Upstream bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036335 0 Quote
Barney Posted December 15, 2023 Author Posted December 15, 2023 @Gunjan Gupta thanks for your reply. The bug has been reported for Raspbian GNU/Linux bookworm/sid. It seems to be specific for the armv7l architecture. On a x86_64 device with Debian 12.2 the who command correctly shows datetime. The bug has been reported in May 2023 (about 7 months ago). Any correction in sight? 0 Quote
Gunjan Gupta Posted December 15, 2023 Posted December 15, 2023 7 hours ago, Barney said: The bug has been reported in May 2023 (about 7 months ago). Any correction in sight? The bug is in core-utils package, so only developers of core-utils can comment about that. 7 hours ago, Barney said: It seems to be specific for the armv7l architecture. It works for me on my nanopi duo2 which is also a Allwinner H3 based board. So not sure what triggers it. May be it has to do something with timezone, or whether daylight saving time is followed or not. In my case, we don't follow daylight saving time in my country. 0 Quote
Barney Posted December 17, 2023 Author Posted December 17, 2023 Am 15.12.2023 um 19:29 schrieb Gunjan Gupta: It works for me on my nanopi duo2 which is also a Allwinner H3 based board. So not sure what triggers it. May be it has to do something with timezone, or whether daylight saving time is followed or not. I played around with the timezone settings, but without success. Seems to be very tricky to find the culprit. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.