touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #04384
[Bug 693231] Re: catch more cases for 'Keep in Launcher' by recognizing StatupWMClass from .desktop file
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/693231
Title:
catch more cases for 'Keep in Launcher' by recognizing StatupWMClass
from .desktop file
Status in BAMF Application Matching Framework:
Fix Released
Status in Unity:
Fix Released
Status in “bamf” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Fix Released
Bug description:
For a while I didn't understand why Firefox daily packages didn't
work. Buf finally I found some time to look into this.
Finding is that for things like firefox daily etc. we have a window
class name called "Minefield", but the desktop file is still called
"firefox-4.0.desktop". In turn bamf, doesn't map those.
Adding support to recognize StartupWMClass= field (if available in
.desktop files) would allow bamf to support more .desktop file
variants, including firefox daily builds.
I have a branch that has this feature here: lp:~asac/bamf/match-apps-
by-startup-wm-class
A preview package for maverick that includes an update to the .postinst to generate the new index format is available in ppa:asac/ppa
+ DSC: https://launchpad.net/~asac/+archive/ppa/+files/bamf_0.2.58-0ubuntu2.asac1.dsc
+ debdiff: http://launchpadlibrarian.net/60349193/bamf_0.2.58-0ubuntu2_0.2.58-0ubuntu2.asac1.diff.gz
... with those changes i can keep firefox daily builds in my
launcher,yay ;).
To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/693231/+subscriptions