-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Wrong icon. Wrong .desktop file. #31
Comments
Partial solution for the launcher problem would be to be able to pin exact .desktop file in .cache/nwg-dock-pinned but that doesn't solve the problem of showing the wrong icon. I am not sure what is possible here, if I can help with something just let me know. |
What the dock only knows about running clients are their class names, as reported by Hyprland. In the case of thunar, thunar-bulk-rename and thunar-settings, it's exactly the same string: "Thunar".
I can't think of a way to resolve the issue. IMO the problem is on the Thunar side. |
I understand the problem and could ignore Thunar but same happens with emacs, which is something I wouldn't avoid. |
If I understand well, this would be a partial solution. Let me make some experiments. |
Could you clone and |
Well, I'll merge and release this branch one way or another, as the current 0.1.7 version won't work on Hyprland 0.40. Let me know how it behaves on your side. |
Thank you, I'll test today and report back. |
Hi @nwg-piotr did you push? This repo only has master branch? |
D'oh it is merged in master. So launchers are perfect with this update, icon still looks wrong for Thunar. They don't go both trough the same code? |
thunar.desktop contains only one Icon definition: Edit: also to confirm that |
I'll install nwg-icon-picker and try but I am 99% certain that drawer picks the right icon, when I manually follow the paths, finder like icon is the only one named org.xfce.thunar. Let me test and I'll report back. |
Just an idea: you could copy your |
This is super odd, with this test theme I am using Re copying .desktop, I will try but this finder icon is already the only one I have with org.xfce.thunar, even if I copy it it will stay the same. I can try changing to something else but I suspect that's not the solution. |
Wait, why nwg-icon-picker shows finder like icon in the list (the highlighted line) but right below title, top of the window, shows same wrong folder icon as in dock?! Please see my screenshot. |
No idea. It must wait at least till the evening, as I'll have to leave in 15 minutes. For now I only know that thunar icons are a mess. |
I'll try figuring something out, thanks. nwg-icon-picker is a great tool btw, I was almost ready to write something similar. I bet the current problem is something in the line of dock matching icon with class instead of with what .desktop file says. No rush, I'll give it a try too, bit rusty in go but I can manage. |
Most probably. Nwg-drawer just reads all the .desktop files, while the dock only knows the class value. |
In conclusion, wrong icon seems to be deeper problem on the GTK level. Experimenting with nwg-icon-picker, loading icon to pixbuf with Solution: make dang .desktop copy in |
This happens with any program that has multiple .desktop files, including Thunar and emacs. I'll explain on Thunar example.
Thunar file manager has 4 different .desktop files:
When I start thunar.desktop, which contains
Exec=thunar %U
, regular Thunar is started, but (probably due to the same bug I am describing), icon already differs from what nwg-drawer is showing.If I pin this dock icon, it is stored in .cache/nwg-dock-pinned as 'thunar'. When I click on this icon to start Thunar, first .desktop file (partial match?) is executed, so it starts
Exec=thunar --bulk-rename %F
as defined in thunar-bulk-rename.desktop, probably because it is alphabetically first to find.I am aware it may be tricky to figure out what .desktop file is most adequate for the pinned dock icon or running program, but current matching makes dock unusable -- resulting in wrong icon and wrong .desktop file being run.
The text was updated successfully, but these errors were encountered: