debcrafters-packages team mailing list archive

[Ubuntu SRU Bot <2111107@xxxxxxxxxxxxxxxxxx>]

All autopkgtests for the newly accepted systemd (257.4-1ubuntu3.2) for plucky have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.32.0-0ubuntu5.3 (amd64, arm64, ppc64el)
avahi/0.8-16ubuntu2 (s390x)
cups/2.4.12-0ubuntu1 (s390x)
dbus-broker/36-1ubuntu0.25.04.1 (s390x)
dracut/106-2ubuntu5 (amd64)
gnome-remote-desktop/48.0-1 (s390x)
incus/6.0.3-4 (armhf)
initramfs-tools/0.147ubuntu1.1 (s390x)
libsoup3/3.6.5-1ubuntu0.2 (ppc64el)
linux-realtime/6.14.0-1010.10 (amd64)
netplan.io/1.1.2-2ubuntu1.1 (arm64, s390x)
samba/2:4.21.4+dfsg-1ubuntu3.4 (ppc64el)
sks/1.1.6+git20210302.c3ba6d5a-4.1 (amd64, arm64, armhf, ppc64el, s390x)
systemd/257.4-1ubuntu3.2 (amd64, ppc64el)
util-linux/2.40.2-14ubuntu1.1 (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/plucky/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2111107

Title:
  systemd user scope fails to connect

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Plucky:
  Fix Committed

Bug description:
  [ Impact ]

   * Running `systemd-analyze --user verify` causes further calls to the systemd user scope to fail with `Failed to connect to user scope bus via local transport: Connection refused`.
   * This bug only exists on the version of systemd shipped in Plucky, and is already fixed upstream.

  [ Test Plan ]

   * Run `systemd --user status` or another systemd command targeting the user scope and observe normal output.
   * Run `systemd-analyze --user verify /usr/lib/systemd/user/systemd-tmpfiles-setup.service` which should run normally.
   * Running `systemd --user status` or another systemd command targeting the user scope afterwards should not fail.

  [ Where problems could occur ]

   * The fix for this bug effects the systemd manager, but only when running in test mode.
   * More specifically, running `systemd-analyze --user verify` or any other command that starts the manager in test mode should still work as expected.

  [ Other Info ]

   * Upstream issue: https://github.com/systemd/systemd/issues/36540
   * Upstream fix: https://github.com/systemd/systemd/pull/36719

  [ Original Description ]

  Using systemd --user for several user-level services. Upgraded to
  25.04 yesterday and noticed an issue today. Sometimes systemctl --user
  commands, threw a "Connection refused", which was new to me.

  Example:
  user@host:~$ systemctl --user daemon-reload
  Failed to connect to user scope bus via local transport: Connection refused

  So I went to look online and found this workaround in this thread for Arch ( https://bbs.archlinux.org/viewtopic.php?id=302556 ):
  unset XDG_RUNTIME_DIR
  systemctl --user daemon-reexec

  I know it's a different distro, but still wanted to mention it,
  especially since we're also using systemd 257 and this should be fixed
  in 258. The mentioned upstream bugreport:
  https://github.com/systemd/systemd/issues/36540

  ProblemType: Bug
  DistroRelease: Ubuntu 25.04
  Package: systemd 257.4-1ubuntu3
  ProcVersionSignature: Ubuntu 6.14.0-15.15-generic 6.14.0
  Uname: Linux 6.14.0-15-generic x86_64
  ApportVersion: 2.32.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: sway
  Date: Fri May 16 15:49:11 2025
  InstallationDate: Installed on 2022-05-14 (1098 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-15-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   ------
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to plucky on 2025-05-15 (1 days ago)
  dmi.bios.date: 08/21/2024
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: L3.47
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrL3.47:bd08/21/2024:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.logrotate.d.apport: [modified]
  modified.conffile..etc.systemd.journald.conf: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2023-01-22T12:04:04.279288
  mtime.conffile..etc.systemd.journald.conf: 2022-08-13T22:29:21.911636

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2111107/+subscriptions