Error about fedora-gdm-logo.png during ujust update

[woutercoppens]

Describe the bug

❯ ujust update ===> Running recipe update`...
LockLayering=false
note: automatic updates (stage) are enabled
==== AUTHENTICATING FOR org.projectatomic.rpmostree1.upgrade ====
Authentication is required to update software
Authenticating as: wouter
Password:
==== AUTHENTICATION COMPLETE ====
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable-daily
Checking out tree 510b4cf... done
Enabled rpm-md repositories: updates fedora fedora-multimedia updates-archive
Importing rpm-md... done
rpm-md repo 'updates' (cached); generated: 2026-01-06T01:08:16Z solvables: 18438
rpm-md repo 'fedora' (cached); generated: 2025-10-23T03:37:20Z solvables: 77664
rpm-md repo 'fedora-multimedia' (cached); generated: 2026-01-03T10:30:30Z solvables: 420
rpm-md repo 'updates-archive' (cached); generated: 2026-01-06T02:00:40Z solvables: 21271
Resolving dependencies... done
Checking out packages... done
error: Checkout fedora-logos-42.0.1-2.fc43.noarch: Hardlinking fd/57c11f7dbc00b368b7e6af4e7d259436736fd7af9aa3fa08aae8e420f3b3a2.file to fedora-gdm-logo.png: File exists
Looking for updates…

Nothing to do.
✔︎ JSON API cask.jws.json Downloaded 15.3MB/ 15.3MB
✔︎ JSON API formula.jws.json Downloaded 32.0MB/ 32.0MB
`

What did you expect to happen?

No errors during ujust update

Output of bootc status

❯ sudo bootc status
● Booted ostree
           Commit: 8bac411f547d2de9b95ce13451313f7dd9704d63d8cbc97b11b4fa468f8e2e6f

  Rollback ostree
           Commit: 47ffe50ba59308773db8c6538656fa8fbe2022afc629648bc330152cce2b658b

Output of groups

❯ groups
wouter wheel dialout docker incus-admin libvirt

Extra information or context

ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable

[renner0e]

you probably layered a package that depends on the fedora logos. We are now using OCI artifacts instead of RPMs for those.

rpm-ostree reset and you will be able to upgrade successfully

[woutercoppens]

❯ rpm-ostree reset ==== AUTHENTICATING FOR org.projectatomic.rpmostree1.bootconfig ==== Authentication is required to change boot configuration Authenticating as: wouter Password: ==== AUTHENTICATION COMPLETE ==== ==== AUTHENTICATING FOR org.projectatomic.rpmostree1.install-uninstall-packages ==== Authentication is required to install and remove software Authenticating as: wouter Password: ==== AUTHENTICATION COMPLETE ==== ==== AUTHENTICATING FOR org.projectatomic.rpmostree1.override ==== Authentication is required to override base OS software Authenticating as: wouter Password: ==== AUTHENTICATION COMPLETE ==== Staging deployment... done Freed: 1,4 GB (pkgcache branches: 1) Removed: cockpit-ws-353.1-1.fc43.x86_64 cockpit-ws-selinux-353.1-1.fc43.x86_64 sscg-4.0.3-2.fc43.x86_64 Changes queued for next boot. Run "systemctl reboot" to start a reboot

After the reboot was the error gone.

I tried to reinstall cockpit-ws again:

❯ rpm-ostree install cockpit-ws ==== AUTHENTICATING FOR org.projectatomic.rpmostree1.install-uninstall-packages ==== Authentication is required to install and remove software Authenticating as: wouter Password: ==== AUTHENTICATION COMPLETE ==== Checking out tree 510b4cf... done Enabled rpm-md repositories: updates fedora fedora-multimedia updates-archive Updating metadata for 'updates'... done Updating metadata for 'fedora-multimedia'... done Updating metadata for 'updates-archive'... done Importing rpm-md... done rpm-md repo 'updates'; generated: 2026-01-06T01:08:16Z solvables: 18438 rpm-md repo 'fedora' (cached); generated: 2025-10-23T03:37:20Z solvables: 77664 rpm-md repo 'fedora-multimedia'; generated: 2026-01-03T10:30:30Z solvables: 420 rpm-md repo 'updates-archive'; generated: 2026-01-06T02:00:40Z solvables: 21271 Resolving dependencies... done Will download: 1 package (1,6 MB) Downloading from 'fedora'... done Importing packages... done Checking out packages... done error: Checkout fedora-logos-42.0.1-2.fc43.noarch: Hardlinking fd/57c11f7dbc00b368b7e6af4e7d259436736fd7af9aa3fa08aae8e420f3b3a2.file to fedora-gdm-logo.png: File exists

[woutercoppens]

I mostly use my PC headless and use cockpit-ws to easily inspect the status of my podman containers.

[woutercoppens]

'❯ sudo find / | grep fedora-gdm-logo.png
[sudo] password for wouter:
find: ‘/run/user/1000/gvfs’: Permission denied
find: ‘/run/user/60578/doc’: Permission denied
578090: /sysroot/ostree/repo/extensions/rpmostree/private/commit/usr/share/pixmaps/fedora-gdm-logo.png
933516: /sysroot/ostree/deploy/default/deploy/385d78a37c92a33e6abc13eab779b2a9f0d6e1175484cd43972da1ab56093ac8.0/usr/share/pixmaps/fedora-gdm-logo.png
1135549: /sysroot/ostree/deploy/default/deploy/510b4cfc4cd1632af4f43eeee560512ae682983d6ff1179b01d5183edf01d100.0/usr/share/pixmaps/fedora-gdm-logo.png
1337557: /usr/share/pixmaps/fedora-gdm-logo.png
`

[repires]

Replicated

rpm-ostree install cockpit-ws

Output:

Checking out tree 07b886d... done
Enabled rpm-md repositories: updates fedora fedora-multimedia updates-archive
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'fedora-multimedia'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'updates'; generated: 2026-01-06T01:08:16Z solvables: 18438
rpm-md repo 'fedora'; generated: 2025-10-23T03:37:20Z solvables: 77664
rpm-md repo 'fedora-multimedia'; generated: 2026-01-03T10:30:30Z solvables: 420
rpm-md repo 'updates-archive'; generated: 2026-01-06T02:00:40Z solvables: 21271
Resolving dependencies... done
Will download: 4 packages (2.8 MB)
Downloading from 'fedora'... done
Downloading from 'updates'... done
Importing packages... done
Checking out packages... done
error: Checkout fedora-logos-42.0.1-2.fc43.noarch:
Hardlinking fd/57c11f7dbc00b368b7e6af4e7d259436736fd7af9aa3fa08aae8e420f3b3a2.file
to fedora-gdm-logo.png: File exists


⸻
sudo bootc status
mount: /etc/fstab: parse error at line 1 -- ignored

● Booted image: ghcr.io/ublue-os/bluefin-dx:stable
  Digest: sha256:61b76466b145688f7426da1eabe06797fac70989bbc8690f1a8e149430e3e090 (amd64)
  Version: 43.20260106 (2026-01-06T01:46:50Z)

  Rollback image: ghcr.io/ublue-os/bluefin-dx:stable
  Digest: sha256:e32adc140296dac9f277f8e8ed5b2b7f32c25c52db49feee53f1ab5899c948b5 (amd64)
  Version: 43.20251230.1 (2025-12-30T01:46:09Z)

[tulilirockz]

This PR is related #3959, I think we remove fedora-logos here now

[repires]

Alternative is to run as a container

Local tested system and working without the fedora-logos:
Booted image: ghcr.io/ublue-os/bluefin-dx:stable
Digest: sha256:61b76466b145688f7426da1eabe06797fac70989bbc8690f1a8e149430e3e090 (amd64)
Version: 43.20260106 (2026-01-06T01:46:50Z)

---

All steps are based on official Cockpit and Podman documentation.

⸻

1. Prerequisites

You need:
• systemd
• podman
• sudo/root access

Verify:

podman --version
systemctl --version

References:
• https://podman.io/docs
• https://cockpit-project.org/running.html

⸻

2. Enable SSH password authentication (required by Cockpit)

Cockpit authenticates via SSH.

Create the config file:

sudo mkdir -p /etc/ssh/sshd_config.d
sudo tee /etc/ssh/sshd_config.d/02-enable-passwords.conf >/dev/null <<'EOF'
# File managed manually for Cockpit
PasswordAuthentication yes
EOF

Restart and enable SSH:

sudo systemctl restart sshd
sudo systemctl enable sshd

Reference:
• https://cockpit-project.org/guide/latest/authentication.html

⸻

3. Pull the Cockpit container image

Cockpit provides an official container image:

sudo podman pull quay.io/cockpit/ws:latest

Reference:
• https://quay.io/repository/cockpit/ws

⸻

4. Install the Cockpit systemd service from the container

The image includes systemd runlabels.

Install the service:

sudo podman container runlabel INSTALL quay.io/cockpit/ws

This installs cockpit.service on the host.

Reference (runlabels):
• https://docs.podman.io/en/latest/markdown/podman-runlabel.1.html

⸻

5. Create and start the Cockpit container

Run the container using the provided label:

sudo podman container runlabel RUN quay.io/cockpit/ws

The container will be named:

cockpit-ws

⸻

6. Enable and start Cockpit

sudo systemctl enable --now cockpit.service
sudo podman start cockpit-ws

Verify:

systemctl status cockpit.service
podman ps

⸻

7. Access Cockpit

Open a browser:

http://localhost:9090

Login with:
• A local Linux user
• Password-based SSH authentication

Official guide:
• https://cockpit-project.org/guide/latest/

⸻

8. Disable or uninstall (optional)

Disable (keep installed)

sudo systemctl disable --now cockpit.service
sudo podman stop cockpit-ws

Uninstall completely

sudo systemctl disable --now cockpit.service
sudo rm -f /etc/systemd/system/cockpit.service
sudo podman stop -i cockpit-ws
sudo podman rm -f cockpit-ws
sudo rm -f /etc/ssh/sshd_config.d/02-enable-passwords.conf
sudo systemctl restart sshd

⸻

Security note (important)

Cockpit exposes a privileged admin interface:
• Restrict port 9090 with a firewall if needed
• Prefer VPN or localhost-only access

Security docs:
• https://cockpit-project.org/guide/latest/feature-security.html

---

Ai assisted by Claude

[mshappe]

Seeing this problem just trying to run ujust update on bluefin.

[renner0e]

this should be fixed with the next image, but these kinda things can just happen if you layer packages