problem in updating Seamonkey
Gentlemen: I currently have Seamonkey version 2.46. However I keep getting a message that something is blocking me to update Seamonkey. Do you have any idea how I can correct this problem.\ I have been using Seamonkey for a long time and am very satisfied with the program. Hope you can help me solve this problem. Very truly yours, George Achilles --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ 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
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
Re: Updating SeaMonkey
Ed Mullen wrote: http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_SeaMonkey Thank you. I'm going to have to read that a few times. -- Connie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Ray Davison wrote: There is the application and there is data. Profile, mail, news,,are data. You want a new app. You don't want or need new data. Copy the profile to a neutral location - preferably off the boot partition so when you go to a new Win you don't have to create a new SM. Now whenever you get a new app, just point it to that profile. As long as you moving to newer apps - not trying to go back - you will not have to do anything else. Thank you. It makes sense to keep the profile separate. It'll save a lot of hassle. -- Connie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
MCBastos wrote: Well, the easiest way to do a migration is using the automatic migration tool. But it's no longer included in more recent versions. So, the trick is doing it in two (or three) steps: 1. Install SM 2.0.14 from this page: http://www.seamonkey-project.org/releases/2.0.14 Note that SM 2.x by default WON'T install over your SM 1.x. Which means that you will end up with two different versions of SM on the disk. This is BY DESIGN. DO NOT force installation over the old version. Note that it's possible that some of your shortcuts are still pointing to the old version. This will be dealt with later. [...] 3. Now, upgrade Seamonkey to the latest version, obtainable from http://www.seamonkey-project.org/ That's basically it. Thank you for the detailed explanation. -- Connie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Daniel wrote: Connie, the other three guys seem to have missed/ignored your last paragraph about SM 2.4.1. If you have run SM 2.4.1, it may have imported your (old) SM 1.1.14 profile, and, when you run 2.4.1, it will attempt to update to SM 2.12, so you will end up with SM 1.1.14 with part of your profile and SM 2.12 with part of your profile. Some of the two profiles might overlapno great problem. My suggestion (for what it's worth!!) would be to delete the SM 2.4.1 program (but keep its profile), then do what the others suggest to convert to SM 2.12, then come back here and we can advise how to get your SM 2.4.1 profile information into your new SM 2.12 profile, if needed. Thank you. I think this is what must have happened. It's the mail accounts and local folders which have been affected. Not all of them are there. I have one machine where they are there but not on the other machine. I think I may have to delete it from the second machine and start again using a copy of the profile from my first one. That would work? -- Connie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Connie wrote: Daniel wrote: Connie, the other three guys seem to have missed/ignored your last paragraph about SM 2.4.1. If you have run SM 2.4.1, it may have imported your (old) SM 1.1.14 profile, and, when you run 2.4.1, it will attempt to update to SM 2.12, so you will end up with SM 1.1.14 with part of your profile and SM 2.12 with part of your profile. Some of the two profiles might overlapno great problem. My suggestion (for what it's worth!!) would be to delete the SM 2.4.1 program (but keep its profile), then do what the others suggest to convert to SM 2.12, then come back here and we can advise how to get your SM 2.4.1 profile information into your new SM 2.12 profile, if needed. Thank you. I think this is what must have happened. It's the mail accounts and local folders which have been affected. Not all of them are there. I have one machine where they are there but not on the other machine. I think I may have to delete it from the second machine and start again using a copy of the profile from my first one. That would work? Most likely *NOT*, if you are talking using the SM 1.1.14 profile directly with SM 2.12, as some of the file formats were changed sometime about SM 2.0 or 2.1. So you will have to do it in two steps, as the others have advised, eg 1.1.14 - 2.0 or 2.1 and then update that 2.1 - 2.12. In any case, if you keep the SM 2.4.1 profile, it can be added to the new, converted, profile later! -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Daniel wrote: Most likely *NOT*, if you are talking using the SM 1.1.14 profile directly with SM 2.12, as some of the file formats were changed sometime about SM 2.0 or 2.1. So you will have to do it in two steps, as the others have advised, eg 1.1.14 - 2.0 or 2.1 and then update that 2.1 - 2.12. In any case, if you keep the SM 2.4.1 profile, it can be added to the new, converted, profile later! Thank you for your advice. It's appreciated. -- Connie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Connie Sparrow wrote: I hope I have the right list for this. If not, I'm sure someone will redirect me to the right one. I use SeaMonkey 1.1.14, yes, I know it's an antique but I like it. It's easy, straightforward and uncomplicated. Unfortunately, there are an increasing number of sites that won't allow me to use it or only allow restricted use :( This means I'm either going to have to update or use one of the ghastly alternatives to SeaMonkey. Equally unfortunately, it appears nothing from my venerable version will automatically install on the newest version. Is there a simple, quick, easy way to move all my settings, etc to the new version or do I have to start again from scratch, adding email accounts, favourites, etc? I have 2.4.1 on my other machine and I don't like it. It's fiddly, complicated and not at all friendly or willing to do things the I want. Connie, the other three guys seem to have missed/ignored your last paragraph about SM 2.4.1. If you have run SM 2.4.1, it may have imported your (old) SM 1.1.14 profile, and, when you run 2.4.1, it will attempt to update to SM 2.12, so you will end up with SM 1.1.14 with part of your profile and SM 2.12 with part of your profile. Some of the two profiles might overlapno great problem. My suggestion (for what it's worth!!) would be to delete the SM 2.4.1 program (but keep its profile), then do what the others suggest to convert to SM 2.12, then come back here and we can advise how to get your SM 2.4.1 profile information into your new SM 2.12 profile, if needed. -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Updating SeaMonkey
I hope I have the right list for this. If not, I'm sure someone will redirect me to the right one. I use SeaMonkey 1.1.14, yes, I know it's an antique but I like it. It's easy, straightforward and uncomplicated. Unfortunately, there are an increasing number of sites that won't allow me to use it or only allow restricted use :( This means I'm either going to have to update or use one of the ghastly alternatives to SeaMonkey. Equally unfortunately, it appears nothing from my venerable version will automatically install on the newest version. Is there a simple, quick, easy way to move all my settings, etc to the new version or do I have to start again from scratch, adding email accounts, favourites, etc? I have 2.4.1 on my other machine and I don't like it. It's fiddly, complicated and not at all friendly or willing to do things the I want. -- Connie ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Connie Sparrow wrote: I hope I have the right list for this. If not, I'm sure someone will redirect me to the right one. I use SeaMonkey 1.1.14, yes, I know it's an antique but I like it. It's easy, straightforward and uncomplicated. Unfortunately, there are an increasing number of sites that won't allow me to use it or only allow restricted use :( This means I'm either going to have to update or use one of the ghastly alternatives to SeaMonkey. Equally unfortunately, it appears nothing from my venerable version will automatically install on the newest version. Is there a simple, quick, easy way to move all my settings, etc to the new version or do I have to start again from scratch, adding email accounts, favourites, etc? I have 2.4.1 on my other machine and I don't like it. It's fiddly, complicated and not at all friendly or willing to do things the I want. http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_SeaMonkey -- Ed Mullen http://edmullen.net/ Music expresses that which cannot be said and on which it is impossible to be silent. - Victor Hugo ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Connie Sparrow wrote: Is there a simple, quick, easy way to move all my settings, etc to the new version or do I have to start again from scratch, adding email accounts, favourites, etc? There is the application and there is data. Profile, mail, news,,are data. You want a new app. You don't want or need new data. Copy the profile to a neutral location - preferably off the boot partition so when you go to a new Win you don't have to create a new SM. Now whenever you get a new app, just point it to that profile. As long as you moving to newer apps - not trying to go back - you will not have to do anything else. Ray ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Updating SeaMonkey
Interviewed by CNN on 01/09/2012 11:20, Connie Sparrow told the world: I hope I have the right list for this. If not, I'm sure someone will redirect me to the right one. I use SeaMonkey 1.1.14, yes, I know it's an antique but I like it. It's easy, straightforward and uncomplicated. Unfortunately, there are an increasing number of sites that won't allow me to use it or only allow restricted use :( This means I'm either going to have to update or use one of the ghastly alternatives to SeaMonkey. Equally unfortunately, it appears nothing from my venerable version will automatically install on the newest version. Is there a simple, quick, easy way to move all my settings, etc to the new version or do I have to start again from scratch, adding email accounts, favourites, etc? I have 2.4.1 on my other machine and I don't like it. It's fiddly, complicated and not at all friendly or willing to do things the I want. Well, the easiest way to do a migration is using the automatic migration tool. But it's no longer included in more recent versions. So, the trick is doing it in two (or three) steps: 1. Install SM 2.0.14 from this page: http://www.seamonkey-project.org/releases/2.0.14 Note that SM 2.x by default WON'T install over your SM 1.x. Which means that you will end up with two different versions of SM on the disk. This is BY DESIGN. DO NOT force installation over the old version. Note that it's possible that some of your shortcuts are still pointing to the old version. This will be dealt with later. On first run, it will offer to copy your data and settings. from the old 1.x profile to a new 2.x profile. Note that it COPIES the profile, it does not CHANGE the original profile. So, if something goes wrong with the process (happens sometimes), your original profile is still unmodified. So, at the end of the process, you will have two Seamonkeys and two profiles. You should now uninstall SM 1.x to avoid problems. Yes, it will remove some of the Seamonkey shortcuts. That's no problem. 2. (OPTIONAL INTERMEDIATE STEP) Later versions of SM 2.x are unable to preserve your download history from SM 2.0.x. Most users don't care about this and skip this step. If you want to preserve download history, you should now upgrade your installation to SM 2.1, obtained here: http://www.seamonkey-project.org/releases/2.1 3. Now, upgrade Seamonkey to the latest version, obtainable from http://www.seamonkey-project.org/ That's basically it. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my TRS-80 * Added by TagZilla 0.7a1 running on Seamonkey 2.12 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
David E. Ross wrote: On 1/11/11 4:38 AM, John wrote: Ray_Net wrote: David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. That is not what is happening. When the newsserver lists open expanded I always collapse them. The bug is that when I close the mail/news reader with the listings collapsed, they are expanded again *sometimes* when I next start mail/news. If they came back the way I left them when I last closed the app, I wouldn't be complaining about it. John If you mean that individual newsgroup threads are expanded within a newsgroup, that is a different issue. That is bug #232562. There is a workaround for this. Either through [Tools Options Advanced Config Editor] or by editing the user.js file in your profile, set the preference variable mailnews.scroll_to_new_message to false. See https://bugzilla.mozilla.org/show_bug.cgi?id=232562. If you mean that a news-mail account is expanded, that is bug 507908, which I cited earlier in this thread. Yes, it is the mail-news accounts, specifically the newsservers, which are being expanded. I leave the mail account expanded all the time but not the news accounts. Is it sufficient to have this reported as a bug for Thunderbird, or should it also be reported somewhere for SeaMonkey? John ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
On 1/12/11 12:06 PM, John wrote: David E. Ross wrote: On 1/11/11 4:38 AM, John wrote: Ray_Net wrote: David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. That is not what is happening. When the newsserver lists open expanded I always collapse them. The bug is that when I close the mail/news reader with the listings collapsed, they are expanded again *sometimes* when I next start mail/news. If they came back the way I left them when I last closed the app, I wouldn't be complaining about it. John If you mean that individual newsgroup threads are expanded within a newsgroup, that is a different issue. That is bug #232562. There is a workaround for this. Either through [Tools Options Advanced Config Editor] or by editing the user.js file in your profile, set the preference variable mailnews.scroll_to_new_message to false. See https://bugzilla.mozilla.org/show_bug.cgi?id=232562. If you mean that a news-mail account is expanded, that is bug 507908, which I cited earlier in this thread. Yes, it is the mail-news accounts, specifically the newsservers, which are being expanded. I leave the mail account expanded all the time but not the news accounts. Is it sufficient to have this reported as a bug for Thunderbird, or should it also be reported somewhere for SeaMonkey? John Since both bugs 232562 and 507908 are specifically Thunderbird bugs, separate SeaMonkey bugs might be appropriate. Check the following bug reports before submitting a new one: https://bugzilla.mozilla.org/show_bug.cgi?id=64426 https://bugzilla.mozilla.org/show_bug.cgi?id=208525 The user interface (UI) for SeaMonkey differs in some respects from the UI for Thunderbird. I'm not really familiar with the SeaMonkey UI for mail-news. I use Thunderbird for a newsreader because I don't want to shut down and restart my newsreader when I change browser profiles. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
On 1/10/2011 4:49 PM PT, David E. Ross typed: https://bugzilla.mozilla.org/show_bug.cgi?id=507908 Thanks. I added my two cents and a vote. :) -- ... Our latest evil plan and create an army of giant ants to take over the galaxy... --Dark Helmet from Spaceballs: The Animated Series (S1 E3). /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
On 1/10/2011 9:46 AM PT, John typed: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I also find this annoying too. :( -- Are you slower than an ant? --Sai Yuk from The Legend of Fong Sai Yuk movie (English subtitles) /\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o| | \ _ /If crediting, then use Ant nickname and AQFL URL/link. ( ) If e-mailing, then axe ANT from its address if needed. Ant is currently not listening to any songs on this computer. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
On 1/11/2011 3:52 AM Ray_Net wrote: David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. I also prefer to have it the way it was when I closed SM. I have one news group that I prefer expanded and others I don't. Perhaps a configuration option on each news group a user has rather than cut and dried expanded or not expanded? -- Ed http://mysite.verizon.net/vze1zhwu/ Powered by SeaMonkey: http://www.seamonkey-project.org/ Never eat more than you can lift.-Miss Piggy (1974-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
Ray_Net wrote: David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. That is not what is happening. When the newsserver lists open expanded I always collapse them. The bug is that when I close the mail/news reader with the listings collapsed, they are expanded again *sometimes* when I next start mail/news. If they came back the way I left them when I last closed the app, I wouldn't be complaining about it. John ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
John wrote: Ray_Net wrote: David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. That is not what is happening. When the newsserver lists open expanded I always collapse them. The bug is that when I close the mail/news reader with the listings collapsed, they are expanded again *sometimes* when I next start mail/news. If they came back the way I left them when I last closed the app, I wouldn't be complaining about it. John Mine has done exactly that for sometime now, through several versions , not just since the last update. It might happen once a week or so and I shut down nightly. Only one of my news servers does not open when the others do. At times the ones that are open have not checked for new messages until I close them and reopen. JAS -- You either teach people to treat you with dignity and respect, or you don't. This means you are partly responsible for the mistreatment that you get at the hands of someone else. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
On 1/11/11 4:38 AM, John wrote: Ray_Net wrote: David E. Ross wrote: On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. Seehttps://bugzilla.mozilla.org/show_bug.cgi?id=507908. How can i vote negatively ? Because i love this bug ... you will find expanded/closed as it was before the closing of SM, So you retrieve the latest situation at start up. That is not what is happening. When the newsserver lists open expanded I always collapse them. The bug is that when I close the mail/news reader with the listings collapsed, they are expanded again *sometimes* when I next start mail/news. If they came back the way I left them when I last closed the app, I wouldn't be complaining about it. John If you mean that individual newsgroup threads are expanded within a newsgroup, that is a different issue. That is bug #232562. There is a workaround for this. Either through [Tools Options Advanced Config Editor] or by editing the user.js file in your profile, set the preference variable mailnews.scroll_to_new_message to false. See https://bugzilla.mozilla.org/show_bug.cgi?id=232562. If you mean that a news-mail account is expanded, that is bug 507908, which I cited earlier in this thread. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! John ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Annoying behavior since updating SeaMonkey to 2.0.11 from 1.1.19
On 1/10/11 2:37 PM, Ray_Net wrote: John wrote: When I open the mail/news reader, about one time in four it will open with all newsservers expanded to show all subscribed newsgroups. I prefer them not to be expanded, and this never happened with v1.1.19. Why is this behavior not consistent each time, and how do I stop it? Thanks! I think that if you close all expanded stuffs just before leaving completely SM before going to shutdown your pc and before going to sleep. The next morning started the pc and started SM ... you will find it in the same situation of yesterday ... all is closed. This is Bug 507908, which some developers think might be a feature. I think it is indeed a bug -- a regression from Tbird 2 -- and should be fixed. See https://bugzilla.mozilla.org/show_bug.cgi?id=507908. -- David E. Ross http://www.rossde.com/ On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
