[Bug]: Helium uses GTK instead of Qt toolkit on KDE, ignoring system font weight

Open
#427 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, shell
Domain
desktop

Research direction

The issue names commit d06a1563 ('patches: disable gtk/qt themes') as the change that introduced the regression, so start by reading that patch in the repository's patches directory. Check how the kDefault toolkit choice resolves to GTK before Qt, and confirm that --ui-toolkit=qt gives the expected weight. Done means KDE system font weight is applied by default, verified by comparing the tab and search bar fonts before and after.

Written by the indexing model from the issue text.

Description

bug
Version

0.19.1.2

Have you tested that this is not an upstream issue or an issue with your configuration?
  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description

On KDE, Helium uses the system font for tabs, the search bar and others, but it does not use the system font weight.

How to Reproduce?
  1. Set KDE's font to a font with non-Regular weight
  2. Launch Helium
  3. Fonts dont follow the weight specified by the system
Actual behavior

The font uses the Regular weight instead of the specified weight.

Expected behavior

Should use the specified weight of the font.

Additional context

Before
Image

After

Image

Was introduced with patches: disable gtk/qt themes, using kDefault makes it try gtk first, so it never uses qt by default, but can be forced via --ui-toolkit=qt

Dominant language
Shell
Stars
1.1k
Forks
63
Avg merge
28m
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.