Open Bug 1865454 Opened 7 months ago Updated 6 months ago

Themes not updated when installing 2.53.18b1

Categories

(SeaMonkey :: General, defect)

defect

Tracking

(Not tracked)

People

(Reporter: petermad, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 SeaMonkey/2.53.17.1

Steps to reproduce:

Installe SeaMonkey 2.53.18b1

Actual results:

When opening the Addons Manager the SeaMonkey Default Theme and the SeaMonkey Modern Theme versions are not updated and is marked as incompatible, and If I try to switch between themes, then it is not possible.

It only happens with my work profile, not with virgin profiles that only has one extra them installed.

Expected results:

The SeaMonkey Default Theme and the SeaMonkey Modern Theme versions should show up as version 2.53.18 and I should be able to switch between themes as usual.

If I restore SeaMonkey 2.53.17.1 and restore my profile, everything works again.

I expect the problem lies in my extensions.json so I attach both my extensions.json file from v. 2.53.17.1 from before updating and extensions.json from after installing v. 2.53.18b1

You seem to have old stuff in "C:\Program Files (x86)\SeaMonkey\". If yes please deinstall SeaMonkey and make sure there is no entry for a second x86 version left. If there is then deinstall it too. Then reboot and remove the "C:\Program Files (x86)\SeaMonkey\" and "C:\Program Files\SeaMonkey\" directories if still there. Then reinstall the x64 version. There are several incompatible extensions listed in your json but can't tell you if they are real or old entries. Some old themes, venkman, an obsolete chatzilla language pack and adb-helper. There are also 2 other modern themes. If they use the same add-on id as Modern they might clash with the internal one.

There was no old stuff in "C:\Program Files (x86)\SeaMonkey".

But I found the reason: there was an extensions.ini file in my default profile with references to files in one of my test profiles. I have no idea how thaet extensions.ini file got there, but it was dated july 2020, and I have updated SeaMonkey more than 30 times since that without problems.

But after removing that extensions.txt file everything works as usual.

hmm extensions.ini is no longer used and should not be created. Need to check if something still uses it.

I might have copied extensions.ini to the profile folder myself, but that must have been several years ago, so it is interesting that its presence haven't given any trouble until I installed v. 2.53.18.b1

Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: SeaMonkey 2.53 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: