Recently added launchers in unity won't recognize whether the application is running or not
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| BAMF |
Confirmed
|
Undecided
|
Unassigned | ||
| bamf (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: unity
After adding a new launcher in the Unity launcher, if the application is started, the launcher isn't able to recognize if the application is currently running or not and won't show it as running being required to logout to have a proper functioning. This bug could be considered serious for applications like LibreOffice since minimizing it could make that current window impossible to grab again (in the case of LibreOffice having quickstart enabled seems to break this bug though).
jose@JARR-Laptop:~$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
jose@JARR-Laptop:~$ apt-cache policy unity
unity:
Installed: 3.8.12-0ubuntu1
Candidate: 3.8.12-0ubuntu1
Version table:
*** 3.8.12-0ubuntu1 0
500 http://
100 /var/lib/
3.
500 http://
| José Antonio (josian2200) wrote | #1 |
| José Antonio (josian2200) wrote | #2 |
| summary: |
- Recently added lauchers in unity won't recognize wether the application - is running or not + Recently added launchers in unity won't recognize whether the + application is running or not |
| Bilal Akhtar (bilalakhtar) wrote | #3 |
| affects: | unity → bamf |
| affects: | unity (Ubuntu) → bamf (Ubuntu) |
| Changed in bamf: | |
| status: | New → Confirmed |
| Changed in bamf (Ubuntu): | |
| status: | New → Confirmed |
| Jens (jens-bormueller) wrote | #4 |
That's because BAMF doesn't regenerate its index, hence disallowing proper matches.