Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QT Theme #217

Open
LinusDierheimer opened this issue Jun 3, 2023 · 7 comments
Open

QT Theme #217

LinusDierheimer opened this issue Jun 3, 2023 · 7 comments

Comments

@LinusDierheimer
Copy link

Since version 108, Chrome allows to use QT as an alternative theme provider to GTK: https://bugs.chromium.org/p/chromium/issues/detail?id=1317782. You might still need to pass the flag --enable-features=AllowQt tho.

On native chrome, this does work really well. On flatpak, clicking the Use QT button under Settings -> Theme does nothing. There is no usefull log, but strace shows that it is trying to dlopen a lot of qt libs that are missing from the flatpak.

I think QT should be shipped with the flatpak too, because it integrates much better with the KDE Plasma desktop, which is widley used.

@jh-devv
Copy link

jh-devv commented Sep 21, 2023

+1

@jh-devv
Copy link

jh-devv commented Sep 21, 2023

This could also fix this:
Screenshot_20230921_150542

@BlueTree242
Copy link

I hope this is fixed soon

@ssleert
Copy link

ssleert commented May 30, 2024

+1

@LinusDierheimer
Copy link
Author

Update: --enable-features=AllowQt is no longer needed, QT is enabled by default now, and chrome even prefers QT on KDE by default now. So this is even more important.

@Bohne13
Copy link

Bohne13 commented Sep 28, 2024

Update: --enable-features=AllowQt is no longer needed, QT is enabled by default now, and chrome even prefers QT on KDE by default now. So this is even more important.

So this bug report should be closed?

@LinusDierheimer
Copy link
Author

LinusDierheimer commented Sep 28, 2024

Update: --enable-features=AllowQt is no longer needed, QT is enabled by default now, and chrome even prefers QT on KDE by default now. So this is even more important.

So this bug report should be closed?

No, it now effects every user on QT based desktops, not just user who explicitly enabled support for QT in chrome. Much more users will now see the disadvantage of the flatpak over native chrome versions.

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

No branches or pull requests

5 participants