Global menu (appmenu) environment setting should be disabled/avoided when using gnome-shell instead of Unity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Baltix |
Fix Released
|
Undecided
|
Unassigned | ||
gnome-shell (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm on Oneiric 11.10 freshly updated, using gnome-shell. Please note that this report is not really about a bug, it's more about some fine tuning for Ubuntu gnome-shell users.
As everyone knows, Ubuntu Unity relies on global menu (on the upper bar). Technically, this involves, among other things, that when an X session is started to load Unity (and Gnome back-end, etc.), an environment variable is set by the /etc/X11/
UBUNTU_
To avoid using the global menu, someone has to set this environment variable like this:
UBUNTU_MENUPROXY=0
Now, when using gnome-shell, instead of Unity, on an Ubuntu 11.10 installation and launching a gtk(3) app., you can observe that there is a slight, but noticeable, delay before the menu appears within the application. Nothing too dramatic, but just enough to make the gnome-shell experience not as great at it could be.
My suggestion/wish would be to make the above mentioned scripts determine what shell is loading (Unity, gnome-shell or...) before setting the environment variable to use, or not, the global menu. Another way to achieve this I guess would be to include in the gnome-shell package, a script that would disable this setting, when gnome-shell is loading. (I'm not so good at Xsession scripting myself, so I let other more knowledgeable people figure this out).
Thanks.
summary: |
- Global menu (appmenu) environment setting should be disabled/avoid when - using gnome-shell instead of Unity + Global menu (appmenu) environment setting should be disabled/avoided + when using gnome-shell instead of Unity |
description: | updated |
description: | updated |
Changed in baltix: | |
status: | New → Fix Released |
Changed in gnome-shell (Ubuntu): | |
status: | Fix Committed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.