633849 - Tab groups loose order after Firefox restart

Status: RESOLVED DUPLICATE of bug 628188

(Firefox Graveyard :: Panorama, defect)

Description

[Lars Gunther]

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b12pre) Gecko/20110213 Firefox/4.0b12pre
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b12pre) Gecko/20110213 Firefox/4.0b12pre

For a while now I keep losing my tab groups when I restart Minefield. Having rearranged my tabs into the order I like, this is quite annoying and totally destroys the usefulness of the feature.

Specifically, the order is reversed into something similar to what it was a a while ago, as if it had been restored from a backup. However, I don not lose any newly added tabs

Reproducible: Always

Steps to Reproduce:
1. Make a number of groups and put a bunch of tabs in each group
2. Restart Firefox
3. Open Panorama = the order is lost
Actual Results:  
See image 1 (will attach soon)

Expected Results:  
Se image 2 (will attach soon)

Bug 633810 might be related, but I'm on Linux.

Comment 1

[Lars Gunther]

Attachment: Actual result: Reverted order

Comment 2

[Lars Gunther]

Attachment: Expected result: How I had arranged my tabs before restart

Comment 3

[Tim Taubert [:ttaubert] (inactive)]

Is this possibly a duplicate of bug 628188? Do you have any jetpack-based add-ons?

Comment 4

[Lars Gunther]

That bug is supposedly fixed and I'm seeing this in the latest nightly.

Is there an easy way to copy my extensions as a text list?

BTW, it just happened again. The trigger was the first time I right clicked on a tab (after restart) and used the "move to group" command.

Comment 5

[Lars Gunther]

Also, this time the tabs did not revert into an order I've had before. Rather, a seemingly random number of tabs from other groups jumped to the tab fǵroup that was open.

That is always the case, BTW. The opened tab group will suddenly have lots of tabs that belong in other groups, but they are never totally depleted.

Comment 6

[Tim Taubert [:ttaubert] (inactive)]

This sounds very much like bug 628188. That bug is fixed but only in the core jetpack library. Every jetpack add-on needs to be updated by itself to get that fix. Could you disable all add-ons and try to reproduce this?

Comment 7

[Lars Gunther]

OK, it seems you are right. Disabling addons fixed the issue. Since that bug was closed, I did not think I could be affected...