What were you trying to do that didn't work?

What is the impact of this issue to you?

the output of podman events is  truncated when --events-backend journald, there is no secret id in the output, but if --events-backend is file, the output containes the secret id.

[root@kvm-03-guest02 ~]# podman --events-backend file events --stream=false
2025-08-20 06:26:27.422572496 -0400 EDT secret create 716893a109f8eed7ff95c5983

[root@kvm-03-guest02 ~]# podman --events-backend journald events --stream=false
2025-08-20 06:26:47.145475184 -0400 EDT secret create 

Please provide the package NVR for which the bug is seen:

podman-5.6.0-1.el10.x86_64

How reproducible is this bug?:

Steps to reproduce

[root@kvm-03-guest02 ~]# printf "secretdata" | podman --events-backend file secret create mysecret -
716893a109f8eed7ff95c5983
[root@kvm-03-guest02 ~]# podman --events-backend file events --stream=false
2025-08-20 06:26:27.420832676 -0400 EDT system refresh
2025-08-20 06:26:27.422572496 -0400 EDT secret create 716893a109f8eed7ff95c5983
[root@kvm-03-guest02 ~]# printf "secretdata" | podman --events-backend journald secret create mysecret1 -
30f3dbce52f1c956deebd5e7a
[root@kvm-03-guest02 ~]# podman --events-backend journald events --stream=false
2025-08-20 06:26:47.145475184 -0400 EDT secret create 
[root@kvm-03-guest02 ~]# 
[root@kvm-03-guest02 ~]# journalctl | grep "secret create"
Aug 20 06:26:47 kvm-03-guest02.lab.eng.rdu2.dc.redhat.com podman[1436]: 2025-08-20 06:26:47.145475184 -0400 EDT m=+0.046107387 secret create 30f3dbce52f1c956deebd5e7a

Expected results

when  --events-backend journald, the output of podman events, should contain the secret id like below:

2025-08-20 06:26:27.422572496 -0400 EDT secret create 30f3dbce52f1c956deebd5e7a

Actual results