Bug#1041014: systemd-timesyncd: data collected by reportbug, new journal

[Al Ma]

Michael, thanks for taking a look. Last time I started /lib/systemd/systemd-timesyncd directly as root from the command line was several days ago, way before the today upload of the new versions of systemd and systemd-timesyncd to stable. Back then, /lib/systemd/systemd-timesyncd did start, did not print anything and also did not terminate by itself. Hitting Ctrl+C killed/terminated it, leading me back to the usual bash prompt. Is this the expected behavior? If this behavior is still the same after the today upgrade, should I still run strace on the process and post the logs or do something else? (I'm going to check in a few days because I don't always have the laptop on which the bug occurs at my disposal.)
(Wild guess: Presumably, during the upgrade from Debian 11 to Debian 12 some important packages that should be installed in their amd64 versions could have hypothetically been installed, for whatever reason, in i386. This is something I observed today on a different machine during an otherwise uneventful, routine upgrade of dbus. I can try to check via `sudo dpkg -l | awk '/^ii/ && $4 == "i386" { print }'`.)
Gratefully,
AlMa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230722/f37b8109/attachment-0001.htm>