-
Notifications
You must be signed in to change notification settings - Fork 28
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
Comments
+1 |
I hope this is fixed soon |
+1 |
Update: |
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. |
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 underSettings -> 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.
The text was updated successfully, but these errors were encountered: