Re: Issues solutions updating SeaMonkey 2.26.1 to 2.33
Mark Bourne wrote: I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes on a few issues and solutions I came across, in case they help anyone else... First off, back up your profile before updating - usually a good idea anyway, just in case the new version messes something up in the profile such that it won't even work in the old version. 1. Crash on Startup - due to missing xulstore.json 2. UI Customisations Lost - does anyone know a solution? 3. Saves Passwords Lost - fix found 1. Crash on Startup - due to missing xulstore.json --- After updating, every time I started SeaMonkey with the old profile, it prompted for the master password but crashed after cancelling that prompt. I tracked this down to xulstore.json being missing from my existing profile folder. Creating an empty xulstore.json file in the root of the profile allowed SeaMonkey to start. To find your profile folder, see: http://kb.mozillazine.org/Profile_folder_-_SeaMonkey I've reported this at: https://bugzilla.mozilla.org/show_bug.cgi?id=1143503 Turns out this was already reported as bug 1092810: https://bugzilla.mozilla.org/show_bug.cgi?id=1092810 It seems to be triggered by a combination of things in the old profile. 2. UI Customisations Lost - does anyone know a solution? - After fixing the above issue, a lot of the UI had reverted to defaults. For example: - All mail folders were collapsed (usually they remember the last state). - Window division positions were reset (e.g. I previously had the folder pane wider and the message pane shorter in Mail News). - Lightning reverted to day view, rather than month view. Subsequently changing things and restarting, the customisations are remembered. This is a one-off reset after the update. This is probably related to the first issue, since xulstore.json replaces localstore.rdf for storing UI customisation. See: http://kb.mozillazine.org/Localstore.rdf So creating an empty xulstore.json probably put everything to defaults. Perhaps an interim update would have converted localstore.rdf to xulstore.json and avoided both these issues. I haven't found a solution for this. Does anyone know of an easy way to convert an old localstore.rdf to xulstore.json format? It seems the crash is at least partially down to having a master password set on the profile. Comment 16 by H. Hofer on bug 1092810: https://bugzilla.mozilla.org/show_bug.cgi?id=1092810#c16 mentions a workaround for both the crash and losing customisations, which works for me. It also seems to avoid losing the saved passwords without the messing around in about:config I previously linked to. In summary: If you haven't yet upgraded to SeaMonkey 2.31 or higher, remove the master password _before_ upgrading. Use Edit Preferences Privacy Security Master Passwords Change Password, enter the current password and leave the new password blank (DO NOT use Reset Password as that clears all your stored passwords). You can set the master password again after upgrading. If you have already upgraded, and haven't already worked around the crash in another way, back up your profile and follow the steps in that comment. In my case, since I'd previously worked around the crash by creating an empty xulstore.json and used SeaMonkey for a couple of days, I combined parts of my old 2.26.1 profile with my new 2.33 profile. Take care doing that - make backups first and if in doubt don't bother and just put up with the customisations being reset! - Backed up my new profile. - Restored most of my 2.26.1 profile from a backup created immediately before upgrading; I kept a few parts such as the mail folders from the new profile to avoid losing emails etc. from the last couple of days. - Followed H. Hofer's steps. The only customisation I've spotted so far which was lost is that the mail news folders were all collapsed rather than in their last state (a bit annoying since I have a lot of folders subfolders nested several levels deep, but no great disaster). I haven't yet spotted anything else which has been reset. Window division positions, column selections and widths, and Lightning view are all as they were before upgrading. Mark. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Issues solutions updating SeaMonkey 2.26.1 to 2.33
mozilla-lists.mbou...@spamgourmet.com wrote on 3/16/2015 3:21 PM: Paul B. Gallagher wrote: mozilla-lists.mbou...@spamgourmet.com wrote: I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes on a few issues and solutions I came across, in case they help anyone else... First off, back up your profile before updating - usually a good idea anyway, just in case the new version messes something up in the profile such that it won't even work in the old version. 1. Crash on Startup - due to missing xulstore.json 2. UI Customisations Lost - does anyone know a solution? 3. Saves Passwords Lost - fix found 1. Crash on Startup - due to missing xulstore.json I didn't have this problem (xulstore.json didn't vanish), but it may be relevant to your next issue: It didn't vanish. It just wasn't present in my old profile from SeaMonkey 2.26.1, and its absence caused a crash in SeaMonkey 2.33. From: http://kb.mozillazine.org/Localstore.rdf it looks like xulstore.json replaces localstore.rdf as of Mozilla 34 (SeaMonkey 2.31?), so not expected to exist in 2.26.1. SM 2.33 was crashing rather than converting the existing localstore.rdf or creating a default version. Perhaps updating to SeaMonkey 2.31 first would have converted localstore.rdf, and avoided the problem. 2. UI Customisations Lost - does anyone know a solution? ... Have you tried restoring xulstore.json from backup? I restored my entire profile from a backup created immediately before updating, but there was no xulstore.json in that profile. 3. Saves passwords lost - fix found ... Sorry, can't help with this. No problem - the solution I linked to worked for me. I just mentioned it in case it helps others. Thanks, Mark. Which is why doing regular full backups of your data and system drives is critical. My system does image backups daily of all my critical drives. I've been advocating this here for years and people still don't get it. They us Mozbackup as though that were the only thing to back up or the only way. Having image backups is the only smart way to go. With a good backup program even if your hard drive fails (and it will) you can restore to different hadware. I hate to be harsh but I have no sympathy for anyone without a sound backup strategy. When you lose your data don't ask me. -- Ed Mullen http://edmullen.net/ Can you buy anything specific at a general store? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Issues solutions updating SeaMonkey 2.26.1 to 2.33
Paul B. Gallagher wrote: mozilla-lists.mbou...@spamgourmet.com wrote: I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes on a few issues and solutions I came across, in case they help anyone else... First off, back up your profile before updating - usually a good idea anyway, just in case the new version messes something up in the profile such that it won't even work in the old version. 1. Crash on Startup - due to missing xulstore.json 2. UI Customisations Lost - does anyone know a solution? 3. Saves Passwords Lost - fix found 1. Crash on Startup - due to missing xulstore.json I didn't have this problem (xulstore.json didn't vanish), but it may be relevant to your next issue: It didn't vanish. It just wasn't present in my old profile from SeaMonkey 2.26.1, and its absence caused a crash in SeaMonkey 2.33. From: http://kb.mozillazine.org/Localstore.rdf it looks like xulstore.json replaces localstore.rdf as of Mozilla 34 (SeaMonkey 2.31?), so not expected to exist in 2.26.1. SM 2.33 was crashing rather than converting the existing localstore.rdf or creating a default version. Perhaps updating to SeaMonkey 2.31 first would have converted localstore.rdf, and avoided the problem. 2. UI Customisations Lost - does anyone know a solution? ... Have you tried restoring xulstore.json from backup? I restored my entire profile from a backup created immediately before updating, but there was no xulstore.json in that profile. 3. Saves passwords lost - fix found ... Sorry, can't help with this. No problem - the solution I linked to worked for me. I just mentioned it in case it helps others. Thanks, Mark. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Issues solutions updating SeaMonkey 2.26.1 to 2.33
I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes on a few issues and solutions I came across, in case they help anyone else... First off, back up your profile before updating - usually a good idea anyway, just in case the new version messes something up in the profile such that it won't even work in the old version. 1. Crash on Startup - due to missing xulstore.json 2. UI Customisations Lost - does anyone know a solution? 3. Saves Passwords Lost - fix found 1. Crash on Startup - due to missing xulstore.json --- After updating, every time I started SeaMonkey with the old profile, it prompted for the master password but crashed after cancelling that prompt. I tracked this down to xulstore.json being missing from my existing profile folder. Creating an empty xulstore.json file in the root of the profile allowed SeaMonkey to start. To find your profile folder, see: http://kb.mozillazine.org/Profile_folder_-_SeaMonkey I've reported this at: https://bugzilla.mozilla.org/show_bug.cgi?id=1143503 It may be relevant that I have two Windows user accounts set up. One a standard user account, and the other an administrator account (which I mainly use through UAC - I hardly ever log in to it directly). To update SeaMonkey, I ran it as Administrator, checked for updates and allowed it to update. Restarted SeaMonkey, again run as Administrator, to apply the update. SeaMonkey crashed the first time after applying the update, but was then OK running as Administrator. However, running as the standard user it crashed every time immediately after dismissing the prompt for master password. 2. UI Customisations Lost - does anyone know a solution? - After fixing the above issue, a lot of the UI had reverted to defaults. For example: - All mail folders were collapsed (usually they remember the last state). - Window division positions were reset (e.g. I previously had the folder pane wider and the message pane shorter in Mail News). - Lightning reverted to day view, rather than month view. Subsequently changing things and restarting, the customisations are remembered. This is a one-off reset after the update. This is probably related to the first issue, since xulstore.json replaces localstore.rdf for storing UI customisation. See: http://kb.mozillazine.org/Localstore.rdf So creating an empty xulstore.json probably put everything to defaults. Perhaps an interim update would have converted localstore.rdf to xulstore.json and avoided both these issues. I haven't found a solution for this. Does anyone know of an easy way to convert an old localstore.rdf to xulstore.json format? 3. Saves passwords lost - fix found --- One I recall someone else mentioning recently. Storage of saved passwords has also changed at some point since 2.26.1. They're supposed to be converted, but this hadn't happened. Possibly because I didn't need to use stored passwords during the first start, so cancelled the master password prompt. The solution suggested at: http://forums.mozillazine.org/viewtopic.php?p=13742105#p13742105 worked for me. As noted, this may not work if you've saved any passwords since upgrading. Hope that's of some help. Mark. --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Issues solutions updating SeaMonkey 2.26.1 to 2.33
mozilla-lists.mbou...@spamgourmet.com wrote: I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes on a few issues and solutions I came across, in case they help anyone else... First off, back up your profile before updating - usually a good idea anyway, just in case the new version messes something up in the profile such that it won't even work in the old version. 1. Crash on Startup - due to missing xulstore.json 2. UI Customisations Lost - does anyone know a solution? 3. Saves Passwords Lost - fix found 1. Crash on Startup - due to missing xulstore.json I didn't have this problem (xulstore.json didn't vanish), but it may be relevant to your next issue: 2. UI Customisations Lost - does anyone know a solution? ... Have you tried restoring xulstore.json from backup? 3. Saves passwords lost - fix found ... Sorry, can't help with this. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
