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

elementaryOS Second Icon in Taskbar #1955

Closed
2 tasks done
Anchor5178 opened this issue Nov 30, 2021 · 6 comments · Fixed by #2139
Closed
2 tasks done

elementaryOS Second Icon in Taskbar #1955

Anchor5178 opened this issue Nov 30, 2021 · 6 comments · Fixed by #2139
Labels
misc:gui misc:installer Affects installer or launcher os:linux type:bug Something isn't working
Milestone

Comments

@Anchor5178
Copy link

Please agree to the following

Summary

Second icon opening up when launching Cryptomator

What software is involved?

  • Operating System: elementaryOS 6 Odin
  • Cryptomator: 1.6.3

Volume Type

FUSE

Steps to Reproduce

  1. install elementaryOS 6
  2. install Cryptomator AppImage
  3. open Cryptomator

Expected Behavior

When launching Appimage via Appimage directly or via Icon in Dock or Start Menu i expect the Application to open within the original icon in the dock.

Actual Behavior

When launching Cryptomator Appimage there is a second icon popping up and revealing as the actual application.

image
Left: Original Appimage which is shown in dock and startmenu, Right: Actual application that will open.

When right clicking the actual application icon there is only shown "close", it is missing the option to pin it to the dock.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@Anchor5178 Anchor5178 added the type:bug Something isn't working label Nov 30, 2021
@overheadhunter
Copy link
Member

overheadhunter commented Dec 1, 2021

Probably the StartupWMClass problem again... See also: cryptomator/cryptomator-linux#10

IIRC this was something where we had to choose between a rock and a hard place...

What does xprop WM_CLASS return for this window?

@Anchor5178
Copy link
Author

@overheadhunter WM_CLASS(STRING) = "java", "java"

@tconsta
Copy link

tconsta commented Jan 30, 2022

Confirm the same on Ubuntu.
Linux 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

WM_CLASS(STRING) = "java", "java"

@overheadhunter
Copy link
Member

overheadhunter commented Jan 30, 2022

@infeo We used to start the app via the jpackage'd binary. But iirc, you changed this to a .sh script due to the different GTK flags. This script will then launch the java binary instead. Hence the change in the WM_CLASS, I guess... Maybe we need to update this line, when using the shell script:

I guess the problem was that you can not pass -Djdk.gtk.version=2 directly to the Cryptomator binary, right?

Edit: We might want to try --add-launcher in jpackage to build a GTK2 and GTK3 launcher. 🤔

@overheadhunter overheadhunter added misc:gui misc:installer Affects installer or launcher os:linux labels Jan 30, 2022
@Anchor5178
Copy link
Author

Same issue with the flatpak install.

Changing the StartupWMClass in the .desktop file to "java" fixes this issue.

@overheadhunter
Copy link
Member

With #2139 merged, the WM_CLASS should now be org.cryptomator.launcher.Cryptomator$MainApp again.

overheadhunter added a commit that referenced this issue Apr 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
misc:gui misc:installer Affects installer or launcher os:linux type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants