Lenses get confused if scope names are too similar

Reported by Mark Tully on 2011-11-20
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Medium
Unassigned
libunity
Medium
Unassigned
libunity (Ubuntu)
Undecided
Unassigned
unity (Ubuntu)
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/launchpad/unitylensbliss/scope/main" and Books one is named "/net/launchpad/lens/books/scope/main". Using D-Feet to view dbus introspection data, it appears that the details for both net.launchpad.UnityLensBliss.Lens and net.launchpad.Lens.Books show /com/canonical/dee/model/com/canonical/Unity/Scope/main/T1321723498/Results in their introspection data. Note that 'main' appears as the final part of the scope's dbus path and the scope definition lens's introspection data.

A workaround for this is to ensure that the last part of the dbus path of a scope is unique.

Mark Tully (markjtully) wrote :
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
Didier Roche (didrocks) on 2012-02-01
Changed in unity (Ubuntu):
status: Confirmed → Triaged
Didier Roche (didrocks) on 2012-02-01
Changed in libunity (Ubuntu):
status: New → Triaged
Michal Hruby (mhr3) on 2012-02-03
Changed in libunity:
milestone: 5.2.0 → 5.4.0
Michal Hruby (mhr3) wrote :

I believe this was fixed in the precise release, can you confirm?

Changed in libunity:
status: Triaged → Incomplete
Changed in unity:
status: Triaged → Incomplete
Changed in unity (Ubuntu):
status: Triaged → Incomplete
Changed in libunity (Ubuntu):
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Unity because there has been no activity for 60 days.]

Changed in unity:
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for libunity (Ubuntu) because there has been no activity for 60 days.]

Changed in libunity (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Michal Hruby (mhr3) on 2013-09-02
Changed in libunity:
status: Incomplete → Fix Released
milestone: 5.4.0 → 6.14.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers