Lenses get confused if scope names are too similar
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Expired
|
Medium
|
Unassigned | ||
libunity |
Fix Released
|
Medium
|
Unassigned | ||
libunity (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
unity (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
If scopes in different lenses have names that are too similar to each other, results from one lens can show up incorrectly under another one. This can be most easily noticed in the home lens, but can occur under individual lenses as well.
For example, installing the Bliss lens (lp:unity-lens-bliss) and the Books lens (lp:unity-lens-books) can lead to results from the Bliss lens (applications) showing up under both Bliss's applications category and the Books category when a global search is done. A screenshot is attached to demonstrate this The screenshot contains results for the default applications lens, the Bliss lens and the Books lens, with Firefox showing up under all three. It should not show up under Books.
This happens due to the fact that the local scope in the Bliss lens dbus path is named: ''/net/
A workaround for this is to ensure that the last part of the dbus path of a scope is unique.
Changed in unity: | |
status: | New → Confirmed |
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
Changed in unity: | |
importance: | Undecided → High |
Changed in unity (Ubuntu): | |
importance: | Undecided → High |
Changed in libunity: | |
milestone: | none → 5.0.2 |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in unity: | |
importance: | High → Medium |
status: | Confirmed → Triaged |
Changed in unity (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in libunity (Ubuntu): | |
status: | New → Triaged |
Changed in libunity: | |
milestone: | 5.2.0 → 5.4.0 |
Changed in libunity: | |
status: | Incomplete → Fix Released |
milestone: | 5.4.0 → 6.14.0 |
Changed in libunity (Ubuntu): | |
importance: | Undecided → Medium |
I believe this was fixed in the precise release, can you confirm?