Description of problem:
Every time I use podman, it spews some incorrect warning messages:

% podman images
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1001` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs    


From what I gathered around the internet, the message is related to missing DBUS_SESSION_BUS_ADDRESS, but I have it defined (it is Fedora 34 Workstation session):

% echo $DBUS_SESSION_BUS_ADDRESS                     
unix:path=/run/user/1001/bus,guid=817e9ffcfb383869ad17ea8360e7428a


Using strace I can confirm podman is not striping ",guid=…" part when trying to open D-Bus connection:

newfstatat(AT_FDCWD, "/run/user/1001/bus,guid=817e9ffcfb383869ad17ea8360e7428a", 0xc00060a378, 0) = -1 ENOENT (No such file or directory)

In reality, ""/run/user/1001/bus" socket exists and should be used; ""/run/user/1001/bus,guid=817e9ffcfb383869ad17ea8360e7428a" does not exist, thus the error.


Version-Release number of selected component (if applicable):
podman-3.2.3-1.fc34.x86_64

How reproducible:
always

Steps to Reproduce:
1. podman images
2.
3.

Actual results:
Throws incorrect warnings.

Expected results:
Should not print any WARN[0000] lines.

Additional info:
Should remove ",guid=…" part from DBUS_SESSION_BUS_ADDRESS before connecting to D-Bus.