monolith-os/monolith
1
1
Fork 0
Code Issues Pull requests Projects Releases 40 Packages 20 Wiki Activity Actions 2

Overwrite Fedora's distributor logos so About shows the Monolith mark #36

Merged
TheDarkWizard merged 1 commit from fix-about-logo into main 2026-07-02 21:51:48 +00:00
Conversation 1 Commits 1 Files changed 2 +10
TheDarkWizard commented 2026-07-02 10:51:51 +00:00
Owner
Copy link

Follow-up to #29: the LOGO os-release key made it into the image (verified on a booted 20260702 deployment, the icon resolves fine through the GTK icon theme), but GNOME Settings never looks at it for the About header. Fedora compiles gnome-control-center with distributor-logo file paths baked in (confirmed in the binary: /usr/share/pixmaps/fedora_logo_med.png for light mode, /usr/share/pixmaps/fedora_whitelogo_med.png for dark mode) and the LOGO key is only the fallback when those files are missing. That's why About still showed the Fedora wordmark.

Replace both files with the Monolith mark, the same approach Bazzite and Bluefin use. The existing white greeter logo covers dark mode; light mode gets a committed dark-tinted variant (same 189x128 mark, RGB flooded to #3d3846 with alpha preserved), since the white original would be invisible on a light background. The #29 icon-name plumbing stays for anything else that reads LOGO.

Follow-up to #29: the LOGO os-release key made it into the image (verified on a booted 20260702 deployment, the icon resolves fine through the GTK icon theme), but GNOME Settings never looks at it for the About header. Fedora compiles gnome-control-center with distributor-logo file paths baked in (confirmed in the binary: /usr/share/pixmaps/fedora_logo_med.png for light mode, /usr/share/pixmaps/fedora_whitelogo_med.png for dark mode) and the LOGO key is only the fallback when those files are missing. That's why About still showed the Fedora wordmark. Replace both files with the Monolith mark, the same approach Bazzite and Bluefin use. The existing white greeter logo covers dark mode; light mode gets a committed dark-tinted variant (same 189x128 mark, RGB flooded to #3d3846 with alpha preserved), since the white original would be invisible on a light background. The #29 icon-name plumbing stays for anything else that reads LOGO.
Overwrite Fedora's distributor logos so About shows the Monolith mark
All checks were successful
PR Rebase Hint / Post rebase command (pull_request) Successful in 25s
Details
bluebuild / Build GNOME NVIDIA (pull_request) Successful in 42m4s
Details
bluebuild / Build GNOME (pull_request) Successful in 29m5s
Details
bluebuild / Generate Release (pull_request) Has been skipped
Details
bluebuild / Release (pull_request) Successful in 0s
Details
67a4c23000
 
The os-release LOGO key from #29 never reaches the Settings > About
header: Fedora builds gnome-control-center with distributor-logo paths
baked in (fedora_logo_med.png light, fedora_whitelogo_med.png dark) and
LOGO is only the fallback when those files are missing. Replace both
files with the Monolith mark instead, the same trick Bazzite and
Bluefin use. The white greeter logo covers dark mode; a committed
dark-tinted variant covers light mode, where white would be invisible.
forgejo-actions commented 2026-07-02 11:12:22 +00:00
Copy link

🧪 Test this PR on a real install

Once the build checks on this PR pass, a signed test image is published for each edition. Pick the one matching your hardware and, from an existing Monolith install (which already has the signing policy), rebase onto it:

gnome

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome:pr-36-44
systemctl reboot

gnome-nvidia

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-36-44
systemctl reboot

The tags are rebuilt on every new commit here, so rpm-ostree upgrade pulls the latest build. When you're done testing, return to your edition's released image (:latest).

The test tags stop updating once this PR is merged or closed.

### 🧪 Test this PR on a real install **Once the build checks on this PR pass**, a signed test image is published for each edition. Pick the one matching your hardware and, from an existing Monolith install (which already has the signing policy), rebase onto it: **`gnome`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome:pr-36-44 systemctl reboot ``` **`gnome-nvidia`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-36-44 systemctl reboot ``` The tags are rebuilt on every new commit here, so `rpm-ostree upgrade` pulls the latest build. When you're done testing, return to your edition's released image (`:latest`). _The test tags stop updating once this PR is merged or closed._
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
dependencies
Pull requests that update a dependency file

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
github_actions
Pull requests that update GitHub Actions code

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
monolith-os/monolith!36
No description provided.