Follow-up confirmation — Ubuntu 26.04.1 LTS (November 16, 2026) I have reproduced the same dual-autostart issue again on November 16, 2026, after receiving the latest available GNOME Session updates from the official Ubuntu repositories.
System environment: - Ubuntu 26.04.1 LTS (Resolute Raccoon) - Linux kernel: 7.0.0-43-generic - gnome-software: 50.0-1 - gnome-software-common: 50.0-1 - gnome-session-bin: 50.1-0ubuntu0.1 - gnome-session-common: 50.1-0ubuntu0.1 - ubuntu-session: 50.1-0ubuntu0.1 The installed package versions match the current candidates reported by apt-cache policy. Findings: During GNOME session startup, gnome-session-service successfully launches GNOME Software through the XDG autostart mechanism. The working instance starts at 10:20:47 (local time) with PID 9569: /usr/bin/gnome-software --gapplication-service It runs under: app-gnome-org.gnome.Software-9569.scope The process successfully owns the D-Bus name org.gnome.Software, as verified using: busctl --user status org.gnome.Software One second later, at 10:20:48, systemd attempts to start gnome- software.service. The competing processes (PIDs 9736, 9971, and 10127) all fail with the same message: Unable to acquire bus name 'org.gnome.Software' After three unsuccessful attempts, systemd reports: gnome-software.service: Start request repeated too quickly. gnome-software.service: Failed with result 'exit-code'. The unit remains in the following state: ActiveState=failed SubState=failed Result=exit-code The systemd unit is pulled in by the GNOME session services target: WantedBy=gnome-session-services.target The XDG autostart entry remains present at: /etc/xdg/autostart/org.gnome.Software.desktop Both startup mechanisms invoke the same executable with the --gapplication-service argument. Conclusion: The original dual-autostart race condition remains reproducible on Ubuntu 26.04.1 LTS with gnome-session 50.1-0ubuntu0.1 and gnome-software 50.0-1. GNOME Software itself remains operational through the first instance, but the competing systemd service consistently enters the failed state. No workaround has been applied. No systemd units, XDG autostart files, or distribution-provided configuration files have been modified. I am keeping the original configuration intact while awaiting an official fix. Thank you for investigating this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167534 Title: Flatpak updates via GNOME Software daily; its failed unit is a harmless Ubuntu dual-autostart race I worked around locally and staged as a Launchpad report for you to submit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2167534/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
