Comment 17 for bug 558581

Inconsistent behavior:

Interestingly, after I tried the above workaround, I reverted back to indicator-applet + indicator-applet-session just to check the consistency of the workaround, and I found that indicator-applet no longer overrode <super>+m on my system.

After switching back and forth among a number of different combinations of indicator-applet configurations on the panel (and logging out and back in each time) it seems that indicator-applet night only override the user's own keyboard shortcut for <super>+m if /usr/lib/indicator-applet/indicator-applet runs before /usr/bin/gtk-window-decorator at session startup. As the run order is not always consistent, sometimes indicator-applet overrides <super>+m and sometimes not.

This goes a long way to explain how this bug could exist at the same time as its "duplicate" (actually inverse) Bug #577226. They are both reflections of a deeper problem: there currently seems to be sense of precedence among programs when it comes to setting global key bindings.

Right now I am using <super>+m to toggle maximization with no problems, even though indicator-applet is running. Don't know if that will still be true tomorrow...