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

.AppImage is missing FreeCad Icon (no icon displayed when running) #228

Closed
AndKe opened this issue May 13, 2024 · 15 comments
Closed

.AppImage is missing FreeCad Icon (no icon displayed when running) #228

AndKe opened this issue May 13, 2024 · 15 comments

Comments

@AndKe
Copy link

AndKe commented May 13, 2024

Please look to the open source project PrusaSlicer to see how to add the icon to AppImage, if in doubt.

@maxwxyz
Copy link
Collaborator

maxwxyz commented May 28, 2024

@AndKe is still present in the current weekly?

@AndKe
Copy link
Author

AndKe commented May 28, 2024

@maxwxyz
I just tested FreeCAD_weekly-builds-37543-conda-Linux-x86_64-py311.AppImage
The issue remains.

@maxwxyz
Copy link
Collaborator

maxwxyz commented May 28, 2024

@adrianinsaval FYI

@adrianinsaval
Copy link
Member

What icon are we talking about?

@maxwxyz
Copy link
Collaborator

maxwxyz commented May 28, 2024

I guess the weekly AppImage icon for the application

@AndKe
Copy link
Author

AndKe commented May 28, 2024

I am talking about the appicon in the "task area" when the application is running.
When FreeCad AppImage is running from an AppImage, then it is represented by a default "gear" icon.
When other AppImages run, they display their own icons.

@maxwxyz
Copy link
Collaborator

maxwxyz commented May 28, 2024

A screenshot would help but I guess you mean that how it is on my Windows:
grafik

@AndKe
Copy link
Author

AndKe commented May 28, 2024

image

A part of the vertical "taskbar/Shortcut" bar on Ubuntu (apps with a orange dot are running)
you see "tmm" , then the running apps: a PDF reader, then PrusaSlicer , then FreeCad (the gear icon) - it's default for iconless-apps.

@adrianinsaval
Copy link
Member

adrianinsaval commented May 29, 2024

what's your system and are you running wayland or x11? If this is wayland, sorry this is a limitation of wayland and there's nothing we can do when shipping as an appimage. You can create a org.freecad.FreeCAD.desktop file with the correct icon info at ~/.local/share/applications and copy the icon to ~/.local/share/icons to workaround this.

@AndKe
Copy link
Author

AndKe commented May 29, 2024

I am using x11 (mostly due to xdotools)
I do already have a .desktop icon, (which works for the shortcut to the app(which has an icon) - but does not help once the app is started)
but unlike (for example) PrusaSlicer AppImage, FreeCAD 's appimage is missing the necessary information to make it display it's own icon when running.

@AndKe
Copy link
Author

AndKe commented May 29, 2024

Also: your post above me helped me because I discovered that when moving the icon to ~/.local/share/icons
, and using just a filename in the deskop file, Icon=FreeCAD.png (rather than full path to other location) works fine.
BTW: The behavior is the same for x11 and Wayland, both works now.
The main difference is still: Other .AppImage files dispålay their icon instantly (on both desktop managers) , but FreeCAD AppImage does not.
Please make it work :)

@adrianinsaval
Copy link
Member

huh, that's weird I never experienced this in x11

@adrianinsaval
Copy link
Member

I cannot reproduce this problem, I can only assume it is an issue on your system. Please let me know if this can be reproduced on a clean system on x11, otherwise I'll close this issue

@jose1968us
Copy link

If you check the .desktop file that is in the /tmp/.mount_freecad file generated when running freecad you will see that the reference to the icon is missing the file extension (.svg)

@adrianinsaval
Copy link
Member

If you check the .desktop file that is in the /tmp/.mount_freecad file generated when running freecad you will see that the reference to the icon is missing the file extension (.svg)

this should not be a problem, consider reporting this bug to your DE instead

@adrianinsaval adrianinsaval closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2024
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

4 participants