Rpm-ostreed.service: Failed with result 'exit-code', UniversalBlue

After another meltdown from my distro, I’m kicking the tires of UniversalBlue.
This is running in a VM on Pop!_OS.
Thanks for any assistance!

Edit: just created a vm with regular Silverblue and rpm-ostree works, so it is something specific to UBlue. Would still appreciate any advice, or if I need to ask elsewhere, please let me know that too. Thanks!

Not sure what information is pertinent.


Fedora Linux 38.20230419.0 (Silverblue)
GNOME 44.0
Virtualization KVM
Kernel Version Linux 6.2.11-300.fc38.x86_64
[john@fedora ~]$ toolbox enter fedora-toolbox-38 
⬢[john@toolbox john]$ neofetch --off
OS: Fedora Linux 38 (Container Image) x86_64 
Host: KVM/QEMU (Standard PC (Q35 + ICH9, 2009) pc-q35-6.2) 
Kernel: 6.2.11-300.fc38.x86_64 
Uptime: 2 hours, 11 mins 
Packages: 545 (rpm), 6 (flatpak) 
Shell: bash 5.2.15 
Resolution: 2864x2312 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Adwaita [GTK2/3] 
Terminal: conmon 
CPU: 13th Gen Intel i9-13900K (8) @ 2.995GHz 
GPU: 00:01.0 Red Hat, Inc. Virtio GPU 
Memory: 2813MiB / 15978MiB 

Here’s the issue:

[john@fedora ~]$ rpm-ostree status
error: Loading sysroot: Failed to invoke RegisterClient: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.
[john@fedora ~]$ systemctl status rpm-ostreed.service
× rpm-ostreed.service - rpm-ostree System Management Daemon
     Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
     Active: failed (Result: exit-code) since Fri 2023-04-21 17:10:10 EDT; 4s ago
       Docs: man:rpm-ostree(1)
    Process: 45555 ExecStart=rpm-ostree start-daemon (code=exited, status=217/USER)
   Main PID: 45555 (code=exited, status=217/USER)
        CPU: 0

Apr 21 17:10:10 fedora systemd[1]: Starting rpm-ostreed.service - rpm-ostree System Management Daemon...
Apr 21 17:10:10 fedora systemd[1]: rpm-ostreed.service: Main process exited, code=exited, status=217/USER
Apr 21 17:10:10 fedora systemd[1]: rpm-ostreed.service: Failed with result 'exit-code'.
Apr 21 17:10:10 fedora systemd[1]: Failed to start rpm-ostreed.service - rpm-ostree System Management Daemon.

What is that?
Why not just use Fedora’s OS directly? Like Silverblue.

It/they are based on Silverblue.
More info:

1 Like

Please file an issue in our github repo, if we find a bug that’s fedora specific we can cross that bridge when we get there.

Ideally we’re not cluttering Fedora resources with custom image bug reports. :smile: Thanks!

1 Like


1 Like

I have seen the future, and it is ublue :slight_smile:

Have you found a solution? I have the same issue