Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #422
Closed
Open
Created Mar 30, 2016 by RingBot@RingBotOwner

GNOME Client: Hardcoded icon path in launcher file

Issue generated from Tuleap's migration script. Originally submitted by: Vincent Bermel (willov)

Currently in the launcher file gnome-ring.desktop.in the icon path is hardcoded to the following absolute path:

Icon=@RING\_INSTALL\_PREFIX@/share/icons/hicolor/scalable/apps/ring.svg

This prevents icon theming without editing the launcher file.

According to the freedesktop.org standard application launcher icon locations are:
/usr/share/icons/hicolor/[size]/apps/
\~/.local/share/icons/hicolor/[size]/apps/
/usr/share/pixmaps/

Since you already install your icon to a standard location according to the standard specification and w.r.t. the icon lookup mechanisms of GNU/Linux DEs you can change the icon path line to simply the icon name:

Icon=ring

You needn't specify the full path or the file extension for icons in a standard location.

The icon will still up correctly and additionally can be themed via globally applied themes.

Assignee
Assign to
Time tracking