Comment 28 for bug 1035755

I'm on Raring, and I had this bug many months ago, but I turned off the global menu extension and was able to keep using Firefox.

Recently Firefox began having the same bug again, and I couldn't figure out why. I even removed firefox-globalmenu, but it kept happening. Then I noticed that there is no longer an extension listed for it in Firefox, and then I noticed that firefox-globalmenu suddenly became a transitional package--i.e. it's built into the Firefox package, and there's no way to disable it anymore.

So that leaves me with two choices:

a. Restart Firefox many times per day.
b. Turn off global menu for all applications.

Neither of these are good choices.

Thankfully, the libdbusmenu-qt2 package for Saucy works in Raring and seems to solve this bug.

Now I'm left with two questions:

1. When is the Raring package going to be upgraded? It's essential that it is upgraded: this is a major regression that popped up without warning in the middle of Raring's lifecycle.

2. Why was the globalmenu package merged into the main Firefox package? Why is there no way to disable the global menu for Firefox? This resulted in Firefox's context menus suddenly failing to work at all, with no apparent explanation. On top of that, I had explicitly disabled the global menu for Firefox, but this merge caused it to return without my consent and without any way to disable it!