Skip to content

Conversation

fugidev
Copy link
Member

@fugidev fugidev commented Sep 15, 2025

Description

Don't enable the main GTK theme by default for GTK 4, as this uses an unsupported workaround and causes some issues, so it should be used with care and as an informed decision by the end user.

Also see #4770 (comment), #5133

Supersedes #5206

Checklist

  • Change is backwards compatible.

  • Code formatted with nix fmt or
    nix-shell -p treefmt nixfmt deadnix keep-sorted --run treefmt.

  • Code tested through nix run .#tests -- test-all or
    nix-shell --pure tests -A run.all.

  • Test cases updated/added. See example.

  • Commit messages are formatted like

    {component}: {description}
    
    {long description}
    

    See CONTRIBUTING for more information and recent commit messages for examples.

  • If this PR adds a new module

    • Added myself as module maintainer. See example.
    • Generate a news entry. See News
    • Basic tests added. See Tests
  • If this PR adds an exciting new feature or contains a breaking change.

    • Generate a news entry. See News

@khaneliman
Copy link
Collaborator

Not terribly a fan of rug-pulling theming on users, though. Testing the branch breaks my theme on my launcher application and I only knew what it was related to because I was knowingly testing the branch.

However, I do understand how it's seen as a hack and some would prefer it to be opt in for gtk4...

I think at minimum, this would need a news entry explaining the situation.

This is not officially supported and causes issues in some cases.
Also adds a warning to the option.
@fugidev
Copy link
Member Author

fugidev commented Sep 17, 2025

You're right, a news entry is needed. I've added one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants