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

StartupWMclass org.jabref.JabRefMain vs org-jabref-JabRefMain #6396

Closed
HifeFish opened this issue May 2, 2020 · 1 comment · Fixed by #6398
Closed

StartupWMclass org.jabref.JabRefMain vs org-jabref-JabRefMain #6396

HifeFish opened this issue May 2, 2020 · 1 comment · Fixed by #6398
Milestone

Comments

@HifeFish
Copy link
Contributor

HifeFish commented May 2, 2020

I installed JabRef 5.0 from the .deb package on Ubuntu 16.04.

JabRef is not correctly associated with the .desktop file, so it doesn't show the icon in the launcher (it shows the default ?-icon instead).

The StartupWMclass in the .desktop file is org-jabref-JabRefMain whereas the application seems to use org.jabref.JabRefMain.

Changing the line in the .desktop file to StartupWMClass=org.jabref.JabRefMain resolves the issue.

@Siedlerchr
Copy link
Member

@HifeFish Thanks for reporting that issue. It would be nice if you could change that line here as well, this is the desktop file that gets copied over
https://github.com/JabRef/jabref/blob/master/buildres/linux/JabRef.desktop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants