** Changed in: coreutils (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2103489
Title:
"who" command is not listing the users
Status in The Ubuntu-power-systems project:
Confirmed
Status in Release Notes for Ubuntu:
Fix Released
Status in coreutils package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Won't Fix
Status in coreutils source package in Plucky:
In Progress
Status in systemd source package in Plucky:
Won't Fix
Status in coreutils source package in Questing:
In Progress
Status in systemd source package in Questing:
Won't Fix
Status in coreutils package in Debian:
Fix Released
Bug description:
SRU Justification:
------------------
[ Impact ]
* The small but well known and popular tool 'who',
included in the coreutils package,
is not built in the correct way in Ubuntu 25.04,
hence does not work properly
and just prints nothing when executed on 25.04.
* In Ubuntu, systemd is no longer built with utmp support.
Among other things, this means that systemd’s default
/usr/lib/tmpfiles.d/systemd.conf no longer creates /run/utmp.
* To solve this situation coreutils needs to be build
with '--enable-systemd' in dh_auto_configure
and also requires libsystemd-dev as Build-Depends.
[ Test Plan ]
* Install a plain Ubuntu 25.04 on any supported architecture,
since this bug was first opened on ppc64el,
ideally test this on ppc64el as well.
* Verify the default coreutils package version with
$ apt-cache policy coreutils
It should report: Installed: 9.5-1ubuntu1
* Just type and execute 'who' to recreate the error situation:
$ who
$
* Now install the modified package
(from proposed, here in this example from my PPA)
and verify that it is the currently installed package:
$ apt-cache policy coreutils
It should report the new version, like "Installed: 9.5-1ubuntu1.1"
* Now 'who' should work fine again and prints an output similar to:
$ who
ubuntu sshd pts/0 2025-04-24 08:51 (10.xxx.xxx.xxx)
* Since building with '--enable-systemd' has also an affect on
the pinky, users, and uptime binaries (because all call read_utmp()
as well), it's reasonable to test these on top:
* executing 'pinky ubuntu' with package 9.5-1ubuntu1 leads to:
$ pinky ubuntu
Login Name TTY Idle When Where
but with the modified package:
$ pinky ubuntu
Login Name TTY Idle When Where
ubuntu ubuntu sshd pts/0 2025-04-25 16:24
10.xxx.xxx.xxx
* executing 'users' with package 9.5-1ubuntu1 leads to:
$ users
$
but with the modified package:
$ users
ubuntu
* executing 'uptime' with package 9.5-1ubuntu1 leads to:
$ uptime
16:40:23 up 9 days, 4:11, 2 users, load average: 0.00, 0.00, 0.00
and with the modified package:
$ uptime
16:40:52 up 9 days, 4:10, 2 users, load average: 0.00, 0.00, 0.00
(so uptime was actually not affected)
[ Where problems could occur ]
* Due to the previous entry in the Release Notes,
one may think that this is not going to be fixed in 25.04
and might already have accepted ot worked around this.
* The new Build-Depends might have been forgotten,
in this case the above test would not lead to a working
package and 'who' command.
* Adding '--enable-systemd' could lead to unforeseen changes in behavior,
but this is very unlikely. Autopkgtests may help to verify.
* Since the code itself stays unchanged and only package meta data
gets modified, there are barely more problems that may occur.
[ Other Info ]
* A test build was done in PPA (for all architectures we support)
and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2103489
* The test package was successfully verified
(like described in the Test Plan above).
* Since the development of the Q release ('Questing') was just opened,
this might need to be uploaded to 'Questing' first before
we can SRU to Plucky/25.04.
__________
== Comment: #0 - Kowshik Jois B S <kowshik.j...@in.ibm.com> - 2025-03-17
09:06:44 ==
---Problem Description---
"who" command is not listing the users.
---Steps to Reproduce---
1. Install Ubuntu25.04 on a PowerVM LPAR
2. Execute "who" command
---uname output---
Linux ubhost2504 6.14.0-10-generic #10-Ubuntu SMP Wed Mar 12 16:05:46 UTC
2025 ppc64le ppc64le ppc64le GNU/Linux
root@ubhost2504:~# ls /run/utmp
ls: cannot access '/run/utmp': No such file or directory
Additional details:
root@ubhost2504:~# systemctl restart systemd-logind.service
root@ubhost2504:~# sleep 5
root@ubhost2504:~# ls /run/utmp
ls: cannot access '/run/utmp': No such file or directory
root@ubhost2504:~#
root@ubhost2504:~# apt list --installed | grep -E
"coreutils|procps|util-linux|sysvinit"
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
coreutils/plucky,now 9.5-1ubuntu1 ppc64el [installed,automatic]
procps/plucky,now 2:4.0.4-4ubuntu5 ppc64el [installed,automatic]
sysvinit-utils/plucky,now 3.14-1ubuntu1 ppc64el [installed,automatic]
util-linux/plucky,now 2.40.2-14ubuntu1 ppc64el [installed]
root@ubhost2504:~
root@ubhost2504:~# apt list --installed | grep -E "util-
linux|systemd|login"
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
libnss-systemd/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
libpam-systemd/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
libsystemd-shared/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
libsystemd0/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
login.defs/plucky,now 1:4.16.0-7ubuntu1 all [installed,automatic]
login/plucky,now 1:4.16.0-2+really2.40.2-14ubuntu1 ppc64el
[installed,automatic]
python3-systemd/now 235-1build5 ppc64el [installed,upgradable to: 235-1build6]
systemd-cryptsetup/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
systemd-hwe-hwdb/plucky,now 256.4.1 all [installed,automatic]
systemd-resolved/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
systemd-sysv/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
systemd-timesyncd/now 257.2-3ubuntu1 ppc64el [installed,upgradable to:
257.3-1ubuntu3]
systemd/now 257.2-3ubuntu1 ppc64el [installed,upgradable to: 257.3-1ubuntu3]
util-linux/plucky,now 2.40.2-14ubuntu1 ppc64el [installed]
root@ubhost2504:~#
root@ubhost2504:~# whoami
root
root@ubhost2504:~# tty
/dev/hvc0
root@ubhost2504:~#
Contact Information = kowshik.j...@in.ibm.com
Machine Type = P10 Rainier
---Debugger---
A debugger is not configured
Userspace tool common name: systemd
The userspace tool has the following bit modes: 64-bit
The file /run/utmp is missing.
Create the file by running:
# touch /run/utmp
Adjust the ownership and permissions:
# chown root:utmp /run/utmp; chmod g+w /run/utmp
Log out from the system and log back in.
root@ubhost2504:~# who
root pts/0 2025-03-18 06:03 (10.231.203.30)
Correct. That file is missing and it should get auto generated upon
reboot. But in this case it is not happening.
Manual creation of the file will solve the issue temporarily but once
the machine gets rebooted, the existing file will gets deleted(this is
expected) and after reboot the file will be missing again(this is a
bug. regeneration of that file should happen automatically after
reboot but is not happening)
We are not seeing /var/run/utmp .. installed systemd/plucky,now
257.3-1ubuntu3 ppc64el [installed,automatic]
but these file is missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2103489/+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
