Unity launcher shows wrong icon (question mark) if the executable is executed via a symlink
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BAMF |
Confirmed
|
Undecided
|
Unassigned | ||
Unity |
Confirmed
|
Undecided
|
Unassigned | ||
Unity Foundations |
Invalid
|
Undecided
|
Unassigned | ||
unity-2d |
Invalid
|
Undecided
|
Unassigned | ||
bamf (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity
Install package avidemux (GTK version). Now run 'avidemux' in a terminal. You get the wrong icon in the Unity launcher (a question mark). Close Avidemux and try running 'avidemux2_gtk' in a terminal. Now you get the correct Avidemux icon in the launcher.
The only difference between the avidemux and avidemux2_gtk commands is symlinks:
% ls -l /usr/bin/avidemux*
lrwxrwxrwx 1 root root 26 2011-04-28 20:58 /usr/bin/avidemux -> /etc/alternativ
-rwxr-xr-x 1 root root 1903376 2011-01-18 00:03 /usr/bin/
% ls -l /etc/alternativ
lrwxrwxrwx 1 root root 22 2011-04-28 20:58 /etc/alternativ
So they are both the same binary. It stands to reason that both commands should produce the same icon in the Unity launcher.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: unity 3.8.12-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CompizPlugins: [core,bailer,
Date: Sun May 29 13:48:29 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in unity: | |
status: | New → Confirmed |
Changed in unity-2d: | |
status: | New → Confirmed |
Changed in unity-foundations: | |
status: | Confirmed → Invalid |
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
Changed in unity-2d: | |
status: | Confirmed → Invalid |
That's because the avidemux2_gtk is mentioned in the desktop file, which BAMF matches correctly.
BAMF should match the correct executable with the desktop file in case the executable is executed via a symlink