# A red padlock icon blinks on \`fastfetch\` result

**URL:** <https://universal-blue.discourse.group/t/a-red-padlock-icon-blinks-on-fastfetch-result/2065>\
**Category:** Bazzite\
**Created:** [June 2, 2024, 4:13pm UTC](https://universal-blue.discourse.group/t/a-red-padlock-icon-blinks-on-fastfetch-result/2065 "2024-06-02T16:13:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dhplakmal](https://avatars.discourse-cdn.com/v4/letter/d/9de053/32.png) [@dhplakmal](https://universal-blue.discourse.group/u/dhplakmal)\
**Post date:** [June 2, 2024, 4:13pm UTC](https://universal-blue.discourse.group/t/a-red-padlock-icon-blinks-on-fastfetch-result/2065/1 "2024-06-02T16:13:59Z")

</div>

I recently rebased to Bazzite from Bluefin. In the fastfetch result, I remember on Bluefin, I had a closed padlock icon that didn’t blink. But after making the switch, it’s blinking in red colour on Bazzite.

As per this doc [here](https://universal-blue.discourse.group/t/bazzite-buzz-14/1217), it indicates whether the image is signed or not. I’m not sure what it means. I used the following command to rebase.

```auto
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable

```

Could someone give some directions on how to get this sorted? or can I simply ignore it?

 ![Screenshot from 2024-06-02 21-41-34](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/b/b4628205b355fbee0fec33b511321c4b7af05cc7.png)

---

<div class="post-metadata">

**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\
**Post date:** [June 2, 2024, 4:15pm UTC](https://universal-blue.discourse.group/t/a-red-padlock-icon-blinks-on-fastfetch-result/2065/2 "2024-06-02T16:15:41Z")

</div>

You can’t rebase to our signed images from stock Fedora Atomic Desktop, so we give the unsigned image command. You can sign your image with this command:

```command
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable

```

---

<div class="post-metadata">

**Author:** ![mel226](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/mel226/32/1577_2.png) [@mel226](https://universal-blue.discourse.group/u/mel226)\
**Post date:** [June 2, 2024, 4:19pm UTC](https://universal-blue.discourse.group/t/a-red-padlock-icon-blinks-on-fastfetch-result/2065/3 "2024-06-02T16:19:39Z")

</div>

Pretty sure you’re supposed to rebase to the signed image: `rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable` as documented [here](https://universal-blue.discourse.group/t/bazzite-inital-setup-and-installation-for-htpc-setups/1145#option-1-rebasing-from-a-fedora-atomic-desktop-image-recommended-39). That padlock indicates you’re on unsigned, once you’re on the signed image the padlock will calm down.

---

<div class="post-metadata">

**Author:** ![dhplakmal](https://avatars.discourse-cdn.com/v4/letter/d/9de053/32.png) [@dhplakmal](https://universal-blue.discourse.group/u/dhplakmal)\
**Post date:** [June 2, 2024, 4:30pm UTC](https://universal-blue.discourse.group/t/a-red-padlock-icon-blinks-on-fastfetch-result/2065/4 "2024-06-02T16:30:15Z")

</div>

Thanks all, doing the above sorted it out.