Has anyone ever found themselves thinking anything beyond the apps and perhaps the files lenses are useful? Only half /s here, I love Unity as much as the next guy (maybe even more), but perhaps my workflow is just stuck in the past as I never even touch the Dash unless I need an app not currently locked to my Launcher. The first thing I do after installing a recent release is a big apt-get –purge for all other scopes, just to better see those apps which are all I (ever) need.
I’d love to have this too, and to have it come down from the top of the screen only once I push the mouse cursor all the way to the top edge. 90% of my menu clicks these days are clicks I meant to hit browser tabs with.
3. Vim, Gedit
4. Gmail (on the web)
6. Screen, yes
As the original reporter, I’m confirming that 5.20.0-0ubuntu2 from -proposed does contain the fix for this bug, i.e. the issue I reported above is no longer reproducible. I’m only hesitant about tagging this ’verification-done’ because PerformingSRUVerification is pretty adamant about having a solid test case and I’m not sure my sloppy initial report qualifies.
jani@saegusa:~$ LC_ALL=C apt-cache policy unity
*** 5.20.0-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
Christopher, your test packages do indeed fix this, excellent! As I mentioned in the report, this was 100% reproducible with the packages from -proposed, and now with the packages from your PPA I could no longer reproduce it at all, during the multiple test logins I did.
Definitely not a showstopper for me Christopher, just a minor annoyance, so it’s a go-ahead from me. Thanks for asking!
Yep, that’s exactly the issue as it occurs here too. Thanks for looking into this Christopher! If you do get this narrowed down and need testing for potentially fixed builds, I’ll be happy to try them out.
I tested 5.20 from Shuduo’s PPA and for me it reproduces the issue just the same as -proposed. To be sure, I then went back down to release versions in all the other packages (so that the only change wrt. released is again just Unity being 5.20, just now from the PPA), and the issue remained. Downgrade Unity to 5.18 and it again goes away.
But this looks like a speed issue, so Unity may not be directly at fault: any apps started once the desktop is fully loaded open as truly maximized, so a workaround is setting autostarted apps to start after a delay. Perhaps Unity going from 5.18 to 5.20 here causes just enough delay for those apps to start before whatever the component is that should fuse the menus with appindicator. The autostarting facility should wait for that component, or the component should be also able to fuse menus for existing windows once it gets up and running.
Incidentally, any appindicator-related packages’ versions also don’t seem to matter for this once Unity is 5.20. I think I’ll try upgrading just those to their -proposed versions next (so that Unity remains at 5.18) just to cover all angles.
With Unity 5.20.0-0ubuntu1 from -proposed, maximized windows opened during login by autostarting apps have their top bar visible underneath the desktop top bar (indicator-appmenu) as if unmaximized, but with the window ’maximize’ button indicating a maximized window – i.e. first click on it results in the window getting smaller. The second click on it then actually maximizes the window so that the top bar merges into the desktop top bar (indicator-appmenu).
This problem appears consistently on every login, after I’ve enabled -proposed and installed Unity 5.20 from there. It never appears when I have 5.18 from -updates. Annoyingly, I am unable to reproduce it in a VM (for a nice demonstration video), but I am able to reproduce it with a newly created user account on the host (i.e. without the configuration from my main user account).
I could’ve taken a screenshot of how it looks right after login. I’ll do that in a minute.
Edit: autostarting apps.