Modern theme incompatile

[fred6633]

Hello,
I've just installed 2.1 RC 1 (= final release I assume) and when it checks the add-ons, it says that the modern theme is incompatible with 2.1 and deactivates it.

I haven't installed any modern theme (or any else themes for that matter).

Is this a known bug?

[raj_bhaskar]

Modern is one of the built-in themes. If it's declaring as incompatible then I'd say that's a bug, although I haven't tested the RC.

[WaltS48]

Maybe on MAC OS. Works here on openSUSE 11.3

[fred6633]

I'm on my macbook at home now. The Addon manager reports that both the default and modern theme are incompatible with SeaMonkey 2.1. However the default theme is not disabled.

If I start in failsafe mode also the default theme is disabled in the Addon manager. Since I only have those themes and they are both disabled, I wonder where my icons etc come from...

Fred

[fred6633]

I tested with 2.1.1 pre, and none of the themes were reported incompatible and could both be enabled.

So it seems to be a known bug in 2.1 fixed in 2.1.1.

Fred

[rsx11m]

It's a problem when migrating a 2.0.x profile to 2.1 with RC1, I've just today (and without seeing your existing report here) run into this issue when migrating my production profiles.

This is bug 657957, Migrating a SeaMonkey 2.0 profile to 2.1 reports modern and default themes as incompatible.

[rsx11m]

I tested with 2.1.1 pre, and none of the themes were reported incompatible and could both be enabled.

That's because the issue apparently only occurs when you update from 2.0.x to either 2.1pre or 2.1.1pre, but not from 2.1pre to 2.1.1pre (see my comment #8 in the bug report).

[rsx11m]

A fix has just landed, http://hg.mozilla.org/releases/comm-2.0/rev/ac9c579e9694.
If you try a 2.0.x > 2.1.1pre migration again with tomorrow's nightly it should work.

[fred6633]

A fix has just landed, http://hg.mozilla.org/releases/comm-2.0/rev/ac9c579e9694.
If you try a 2.0.x > 2.1.1pre migration again with tomorrow's nightly it should work.

Thanks but all my 2.0.x profiles are already migrated to 2.1. When I tested with 2.1.1, I had renamed the SeaMonkey folder in /User/Fred/Library/Application Support.

I want to stay with stable releases. From what I understand, when 2.1.1 is released the themes will no longer be reported as incompatible.

[fred6633]

I deleted the xpi files in the extension folder in the application folder. Thereafter copied them back from the Mac dmg file and both the themes were reported compatible next restart.
Correction: It didn't work with another profile. I had some hacked xpi files. It must have been these I copied and got it to work.

[rsx11m]

Have a look at comment #9, item #2. Removing or renaming the extensions.sqlite file in your profile will force it to rebuild, taking the correct versions from the installation folder.

Today's nightly update bumped the theme versions successfully from 1.0 to 2.1.1pre (or 2.2a1pre if you are on trunk), so that part worked.

[fred6633]

I just installed 2.1 rc 2. Now the themes have changed from 2.1 to 2.1pre.

[rsx11m]

Will be fixed in RC3 or final, it shouldn't affect the compatibility as the themes now match the application's version number, thus are always "compatible" in this regard (it's a different story with the optional extensions installing in the profile, but the themes still come bundled with the application and stay there).

[4td8s]

SM 2.1 final release came out on June 10. no RC3 was needed, rsx11m.

[therube]

(After RC2, a 2.1-candidates was built. Then it was simply moved over, as is, to be the 2.1 Release.)