Activate "More suggestions" result to activate "recently used"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity Tweak Tool |
Fix Released
|
Low
|
J Phani Mahesh | ||
unity-tweak-tool (Ubuntu) |
Fix Released
|
Low
|
J Phani Mahesh | ||
Raring |
Fix Released
|
Low
|
Andrew Starr-Bochicchio |
Bug Description
SRU Justification:
[Impact]
* The "show more suggestions" and the "show the recently used applications" checkboxes in the search panel are reverses.
[Test Case]
1) With 0.0.4 from raring, go to the search panel and click on "show more suggestions." In Unity's applications lens, you will see that you actually enabled/disabled "recently used."
2) Install 0.0.4ubuntu0.1 from raring-proposed and verify that this does not occur.
[Regression Potential]
* The fix is trivial. It simply swaps to keys. There is very little chance of regression.
[Other Info]
As this is a native package, the patches are applied directly. The fix is taken from this upstream commit:
https:/
------
Using unty-tweak-tool 0.4 in raring
If you go to "search" and click on"show more suggestion" it activates in fact the "show" the recently used" in the dash lens application
And if you activates the "show the recently used", it activate the "more suggestions in the dash
(ubuntu 13.04, french language)
Changed in unity-tweak-tool: | |
assignee: | nobody → J Phani Mahesh (phanimahesh) |
importance: | Undecided → Low |
status: | New → Fix Committed |
Changed in unity-tweak-tool (Ubuntu): | |
assignee: | nobody → J Phani Mahesh (phanimahesh) |
Changed in unity-tweak-tool: | |
status: | Fix Committed → Fix Released |
Changed in unity-tweak-tool (Ubuntu Raring): | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Andrew Starr-Bochicchio (andrewsomething) |
description: | updated |
I'm seeing the same thing. I also talked to a buddy who had just installed 13.04 and the Unity Tweak Tool. He confirmed the bug with me, at which point I knew it wasn't just me seeing this issue. I then went to submit the bug but it already existed, so I wanted to comment my findings.