run command histroy not shown first time after reboot

Bug #798040 reported by Redmar
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ayatana Design
Fix Released
Wishlist
John Lea
Unity
Fix Released
Wishlist
Oliver Sauder
unity-2d
Fix Released
Undecided
Unassigned
unity-lens-applications
Fix Released
Wishlist
Oliver Sauder
unity (Ubuntu)
Fix Released
Undecided
Unassigned
unity-place-applications (Ubuntu)
Fix Released
Wishlist
Oliver Sauder

Bug Description

Binary package hint: unity

When hitting alt+f2 the first time after reboot, it shows just the small bar where you can type the command, not the bigger window with most used/recently used commands. When you type just one letter in the box the window will expand to show the history.

I think this behaviour is inconsistent and requires users to perform an unnecessary extra action when they want to run a custom command.

What I would like to see is that the alt+f2 window always opens up showing the most used commands, and not to make an exception when its the first time after reboot.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: unity 3.8.14-0ubuntu1~natty1
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,gnomecompat,regex,ring,move,neg,mousepoll,snap,grid,imgpng,resize,place,animation,workarounds,session,fade,cube,expo,scale,ezoom,rotate,scaleaddon,unityshell,unitymtgrabhandles]
Date: Thu Jun 16 08:37:59 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
ProcEnviron:
 LANGUAGE=nl:en
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Redmar (redmar) wrote :
Revision history for this message
Marco Biscaro (marcobiscaro2112) wrote :

This bug is awaiting design feedback before progress can be made. Confirming that there is a question to be answered. Will be marked triaged when design gives a suitable direction forward.

Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
tags: added: needs-design
John Lea (johnlea)
Changed in ayatana-design:
assignee: nobody → John Lea (johnlea)
importance: Undecided → Wishlist
status: New → Fix Committed
Changed in unity:
status: Incomplete → Confirmed
Changed in unity (Ubuntu):
status: Incomplete → Confirmed
Changed in unity:
assignee: nobody → Unity Community Hackers (unity-community-hackers)
tags: removed: needs-design
Oliver Sauder (sao)
Changed in unity (Ubuntu):
assignee: nobody → Oliver Sauder (sao)
status: Confirmed → In Progress
Revision history for this message
Oliver Sauder (sao) wrote :

Bug seems to be in unity-place-applications

Changed in unity-place-applications:
status: New → In Progress
assignee: nobody → Oliver Sauder (sao)
Revision history for this message
Marco Biscaro (marcobiscaro2112) wrote :

Yes, I think the problem is there.

affects: unity (Ubuntu) → unity-place-applications (Ubuntu)
Changed in ayatana-design:
status: Fix Committed → Invalid
status: Invalid → Fix Committed
Changed in unity:
status: Confirmed → Invalid
assignee: Unity Community Hackers (unity-community-hackers) → nobody
Revision history for this message
Oliver Sauder (sao) wrote :

This issue is trickier than anticipated ;).

This bug does not only affect the execute command but all lenses. So after a reboot when <Super>a or <Super>f is pressed the dash is always empty.

This seems to be a timing issue. The places are connected when the home button is hovered. However with all the shortcuts such a hovering usually does not occur. Therefore the connection of the places is done when opening the dash. This is to late.

One way around this issue, would be to try to connect the places when Launcher.StartKeyShowLauncher is called. This would fix this issue for all places except the Execute Command as such does not open the launcher but directly the dash.

The only way around I can currently see, is to wait until the places are successfully connected before showing the dash.
However I'm not sure if that is really desired?

Additionally to this bug has the execute command another bug:
The history gets not loaded when the execute command gets activated. This issue should be fixed in lp:~sao/unity-place-applications/load-history-when-activating

Changed in unity:
status: Invalid → In Progress
assignee: nobody → Oliver Sauder (sao)
Changed in unity-2d:
status: New → In Progress
Alex Launi (alexlauni)
Changed in unity:
importance: Undecided → Wishlist
Changed in unity-place-applications:
importance: Undecided → Wishlist
Changed in unity-place-applications (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Omer Akram (om26er) wrote :

linked branches merged, setting to fixed.

Changed in unity-place-applications (Ubuntu):
status: In Progress → Fix Released
Changed in unity-lens-applications:
status: In Progress → Fix Released
Changed in unity:
status: In Progress → Fix Released
Changed in unity-2d:
status: In Progress → Fix Released
Changed in ayatana-design:
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.