-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Chrome apps don't have the correct icons in the launcher #5
Comments
What does the .desktop say for the Icon field? |
Here's the #!/usr/bin/env xdg-open
[Desktop Entry]
Version=1.0
Terminal=false
Type=Application
Name=Chrome Remote Desktop
Exec=/opt/google/chrome/google-chrome --profile-directory=Default --app-id=gbchcmhmhahfdphkhkmpfmihenigjmpp
Icon=chrome-gbchcmhmhahfdphkhkmpfmihenigjmpp-Default
StartupWMClass=crx_gbchcmhmhahfdphkhkmpfmihenigjmpp The icons come from
|
@ibeliever It depends on the theme, I logged the requested icon and the resulting QIcon from the Fluid icon theme image provider with Papirus GTK:
Somehow Papirus GTK provides an icon for Chrome apps. There are icons like chrome.svg and chrome-okdgofnjkaimfebepijgaoimfphblkpd.svg though I don't know how this should affect the lookup exactly. If I use Adwaita I can see the icon correctly and the log reports:
My Chrome application is this page and as you can see here it shows the GH icon: It might also be a Qt bug but I'm not sure what should I report since it works with Adwaita. |
Yeah, it looks like somehow Paper is falling back to a generic Chrome icon instead of the original icons when a Paper version of the icon isn't found. I think the original issue was that I didn't have the Hawaii icon theme installed (I've since changed the theme in dconf). |
Though, that only happens in qmlOS - they properly fall back to the original icons in GNOME. |
QIcon might have some issue with hicolor. This is a simple program:
Set XDG_DATA_DIRS=$HOME/.local/share:/usr/share, build and run. This is the output:
Uncomment the line that sets the theme to hicolor, build and run:
|
The text was updated successfully, but these errors were encountered: