Auto update 2.50 to 2.51
I was toying with SM 2.50 last week and it automatically updated to 2.51 Saturday. Anyhow, for what it's worth. The functions that I use, so far, have worked fine. -- "This is America! You can't make a horse testify against himself!" Mister Ed ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto-Update "Something is trying to trick SeaMonkey..."
Paul B. Gallagher wrote: My recollection is 2.35, but either way, the point is you have to install one update manually to get past the certificate issue, and from then on auto updates will work again. I was able to visit over the holidays, and the new SM is now installed and working. It turns out that it could have been done without admin rights anyway; I must have originally installed it "per user" and that's why the updates had been working for over five years. -- Gerry Hickman (London UK) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto-Update "Something is trying to trick SeaMonkey..."
Edmund Wong wrote: Gerry Hickman wrote: Hi, I don't fully understand the cause of the issue (client cert, server cert, string mismatch), but I did notice some about:config values in my own correctly updated 2.38 version. I wonder if they change app.update.cert.requireBuiltIn true -> false would it allow them to get past the error and receive the new version? The basic issue is that around 2.38b1 (iirc), we had changed certs, so anything < 2.38b1 won't be able to upgrade to the latest version and will require a full download and install. So while 2.38 -> 2.39 works, 2.x -> 2.38+ (where x <38) won't update. My recollection is 2.35, but either way, the point is you have to install one update manually to get past the certificate issue, and from then on auto updates will work again. -- 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: Auto-Update "Something is trying to trick SeaMonkey..."
Gerry Hickman wrote: > Hi, > > I don't fully understand the cause of the issue (client cert, server > cert, string mismatch), but I did notice some about:config values in my > own correctly updated 2.38 version. > > I wonder if they change > app.update.cert.requireBuiltIn > true -> false > would it allow them to get past the error and receive the new version? The basic issue is that around 2.38b1 (iirc), we had changed certs, so anything < 2.38b1 won't be able to upgrade to the latest version and will require a full download and install. So while 2.38 -> 2.39 works, 2.x -> 2.38+ (where x <38) won't update. Edmund ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Auto-Update "Something is trying to trick SeaMonkey..."
Hi, On a friend's computer, they are getting this error when SM <2.38 tries to perform auto-udpate. Apparently, it's a "known issue" related to SSL certificate mismatch. See first forum post here http://forums.mozillazine.org/viewtopic.php?f=3=2964365 The solution is to use admin rights to download and install a fresh copy of the SeaMonkey distribution. However, in this case I'd like to try to get their auto-update working (long story) so they can get onto >2.38, and then it should be OK. I don't fully understand the cause of the issue (client cert, server cert, string mismatch), but I did notice some about:config values in my own correctly updated 2.38 version. I wonder if they change app.update.cert.requireBuiltIn true -> false would it allow them to get past the error and receive the new version? app.update.cert.requireBuiltIn;true app.update.certs.1.commonName;aus2-community.mozilla.org app.update.certs.1.issuerName;CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US app.update.certs.2.commonName;aus2-community.mozilla.org app.update.certs.2.issuerName;CN=Thawte SSL CA,O="Thawte, Inc.",C=US app.update.url;https://aus2-community.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml -- Gerry Hickman (London UK) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: No auto update anymore?
Eric schrieb: Seamonkey used to just download and install migrating everything over, does it not do this anymore? Why? Sorry, because i don't have an answer. But sometimes when i look at the version in help, there is a comment telling me to be in an download phase. At any time a new version is coming. -- Liebe Grüße, Gerd Satelliten FAQ, DVB-T, Katzen, Mopped, Garten, Heimwerken: http://www.satgerd.de/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: No auto update anymore?
Eric wrote on 10/11/2015 21:03: Seamonkey used to just download and install migrating everything over, does it not do this anymore? Why? Eric I never use the auto-update. I always remove the current SM then I install the new one. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: No auto update anymore?
Ray_Net wrote: Eric wrote on 10/11/2015 21:03: Seamonkey used to just download and install migrating everything over, does it not do this anymore? Why? Eric I never use the auto-update. I always remove the current SM then I install the new one. Got the pop-up prompt this morning inviting me to upgrade, dismissed it because I'm working on a mission-critical job and can't take any risks. Will return in a few days and check for updates manually, accept it if there hasn't been a surge of complaints here. Everything seems to be working normally in this respect. The OP should read my previous reply in this thread. -- 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: No auto update anymore?
Eric wrote: SeaMonkey used to just download and install migrating everything over, does it not do this anymore? What are your settings? Edit | Preferences | Advanced | Software Installation: ... SeaMonkey [x] Automatically check for updates (•) daily (o) weekly [ ] Automatically download and install the update [x] Warn me if this will disable any of my add-ons For example, if it's only checking weekly, it might not know about 2.39 yet. -- 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
No auto update anymore?
Seamonkey used to just download and install migrating everything over, does it not do this anymore? Why? Eric ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Mike C wrote: EE wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. By sidebar do you mean he left window where the folders are? Or something else? The sidebar opens in the browser window. I have to open it by pressing Option plus either Page Up or Page Down, but with Windows you can open it with F9. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Original Message *Subject: *Re: Auto Update *From: *Mike C rp...@earthlink.net *To: * *Date: *Fri Sep 26 2014 01:38:34 GMT+0200 (CEST) Ed Mullen wrote: EE wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. Click the email column to sort by that. Then click the Name column. No idea how this got screwed up in an update. Hey Ed, Thanks for the post. BUT Clicking name at top of column doesn't fix it. However... If I sort by email column AND THEN resort by name it goes correct. BUT... the next time address book is opened it's back to being incorrect. (This is with both 2.29 and 2.29.1) I am aware that if I go back to 2.26 all will be well again. Not important enough to do that. It's not so serious, just inconvenient. For this issue and Gosthery unsupport in SM 2.29, I back to SM 2.26.1 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? In my 2.26.1 and all previous versions, the address book has been sortable -- click on a column title (e.g., Name) to sort by that parameter, click it again to reverse the order. Does that not work for you? -- 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: Auto Update
stan wrote: Michael Speier wrote: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1 I think it is better to upgrade your Windows XP before downgrade your SeaMonkey! So are you saying that if I want to continue using SM that I must upgrade to Windows 7 or 8? Maybe one day when the development environment will be upgraded (probably by the Firefox people) this will be needed anyway. I guess Michael wanted to tell you that the security holes (well known!) in XP are MUCH bigger problems than your seamonkey problems. And they NEVER will be fixed! Just my 2cc, Mycroft -- There's another way to survive. Mutual trust -- and help. -- Kirk, Day of the Dove, stardate unknown ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
EE wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. By sidebar do you mean he left window where the folders are? Or something else? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
EE wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. Click the email column to sort by that. Then click the Name column. No idea how this got screwed up in an update. -- Ed Mullen http://edmullen.net/ Artificial intelligence is no match for natural stupidity ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Paul B. Gallagher wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? In my 2.26.1 and all previous versions, the address book has been sortable -- click on a column title (e.g., Name) to sort by that parameter, click it again to reverse the order. Does that not work for you? Doesn't work in 2.29 or 2.29.1 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Ed Mullen wrote: EE wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. Click the email column to sort by that. Then click the Name column. No idea how this got screwed up in an update. Hey Ed, Thanks for the post. BUT Clicking name at top of column doesn't fix it. However... If I sort by email column AND THEN resort by name it goes correct. BUT... the next time address book is opened it's back to being incorrect. (This is with both 2.29 and 2.29.1) I am aware that if I go back to 2.26 all will be well again. Not important enough to do that. It's not so serious, just inconvenient. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Mike C wrote: Ed Mullen wrote: EE wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? Use it in the sidebar. That is sorted correctly. Click the email column to sort by that. Then click the Name column. No idea how this got screwed up in an update. Hey Ed, Thanks for the post. BUT Clicking name at top of column doesn't fix it. However... If I sort by email column AND THEN resort by name it goes correct. BUT... the next time address book is opened it's back to being incorrect. (This is with both 2.29 and 2.29.1) I am aware that if I go back to 2.26 all will be well again. Not important enough to do that. It's not so serious, just inconvenient. Well, that is what I said to do. I agree, the fix does not hold from instance to instance SM. -- Ed Mullen http://edmullen.net/ I used to be indecisive. Now I'm not so sure. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
On 09/25/2014 04:26 PM, Mike C wrote: Paul B. Gallagher wrote: Mike C wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? In my 2.26.1 and all previous versions, the address book has been sortable -- click on a column title (e.g., Name) to sort by that parameter, click it again to reverse the order. Does that not work for you? Doesn't work in 2.29 or 2.29.1 Works for me. User agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 SeaMonkey/2.29.1 Build identifier: 20140923221706 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
WaltS48 wrote: On 09/23/2014 07:27 PM, stan wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false Well I cant logo into Tools Password Manager it crashes Also it crashes if I want to use this forum. To me that is BAD. -Stan What does Tools Password Manager have to do with auto updates? Nothing! Disabling auto update prevents loading of SM2.29 and I want to run SM2.26 until these bugs will be fixed. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
On 09/24/2014 09:40 AM, stan wrote: WaltS48 wrote: On 09/23/2014 07:27 PM, stan wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false Well I cant logo into Tools Password Manager it crashes Also it crashes if I want to use this forum. To me that is BAD. -Stan What does Tools Password Manager have to do with auto updates? Nothing! Disabling auto update prevents loading of SM2.29 and I want to run SM2.26 until these bugs will be fixed. Just saw on the mozillaZine forums that a SM 2.29.1 is imminent. [1072088 – (SM2.29.1) Tracking bug for build and release of SeaMonkey 2.29.1](https://bugzilla.mozilla.org/show_bug.cgi?id=1072088) -- Sponsored by Firefox 33.0b6 and Thunderbird 31.1.1 GO Bucs, Steelers, Pitt, Pens, Bills and Sabres! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1 I think it is better to upgrade your Windows XP before downgrade your SeaMonkey! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
stan wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false Well I cant logo into Tools Password Manager it crashes Also it crashes if I want to use this forum. To me that is BAD. -Stan Those must be Windows problems only. I use Mac OS and I can open the data manager without having any crashes, and this newsgroup is not posing any problem either. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
Michael Speier wrote: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1 I think it is better to upgrade your Windows XP before downgrade your SeaMonkey! So are you saying that if I want to continue using SM that I must upgrade to Windows 7 or 8? That would be pretty stupid. It would only make several Billon$ for Microsoft. -Stan ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false The only bug I see is the address book isn't alphabetical. Has anyone figured out how to correct it? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Auto Update
How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false Or you can do it the safe/easy way through the user interface: Edit | Preferences | Advanced | Software Installation ... SeaMonkey: [x] Automatically check for updates ( ) daily (•) weekly [ ] Automatically download and install the update If you uncheck the second box, you'll get nagged once a week but SM won't install anything without permission. If you uncheck both boxes, SM will never check and never nag (and obviously, never install anything). You can still check manually via Help | Check for Updates. -- 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: Auto Update
EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false Well I cant logo into Tools Password Manager it crashes Also it crashes if I want to use this forum. To me that is BAD. -Stan ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto Update
On 09/23/2014 07:27 PM, stan wrote: EE wrote: stan wrote: How can I suppress Auto Update for SM? The SM2.29 is too buggy so I must keep reinstalling SM2.26 -Stan I found only 2 bugs, and I found workarounds for both of them. The address book is properly sorted in the sidebar, so I can use it to get email addresses, and open a compose window from there. The bookmark backups will not restore, but if one exports them as HTML, one can import them. To stop automatic updates, what I did was go into about:config and change these settings: app.update.auto - false app.update.enabled - false app.update.silent - false Well I cant logo into Tools Password Manager it crashes Also it crashes if I want to use this forum. To me that is BAD. -Stan What does Tools Password Manager have to do with auto updates? -- Sponsored by Firefox 33.0b6 and Thunderbird 31.1.1 GO Bucs, Steelers, Pitt, Pens, Bills and Sabres! ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Auto-update language packs
Francesco Presel wrote: I'm currently using the Linux 64-bit experimental build, only available in English, which means I must use a language pack in order to localize seamonkey. Every time I update Seamonkey, the language pack is not automatically updated, and the old, now incompatible version remains. So, every time I update SM, I have to manually download and install again the language pack, for every single user and profile I have on this computer, and sometimes I even have to reactivate and set again the default language. It would be nice if, like every other addon (like Lightning, which always needs to be updated after every SM update), it was automatically updated (eg, when I update SM to 2.11 every language pack I have is updated to 2.11). I haven't found any other report of this; is there a better place to report this? TIA Francesco, your suggestion about getting the updated language pack at the same time as SM is update is a good one, but, as I understand it, the language packs are not made by the SeaMonkey Council, but rather by individuals who need the packs and they then release it to the Council for others, such as yourself, to use. So once the new version of SM is released, it takes some time (a couple of days, maybe) for the other packs to become available. One option might be to download the language pack to your hard drive and then copy it to a flash drive for coping to the other computers and install from the hard drive. -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Auto-update language packs
I'm currently using the Linux 64-bit experimental build, only available in English, which means I must use a language pack in order to localize seamonkey. Every time I update Seamonkey, the language pack is not automatically updated, and the old, now incompatible version remains. So, every time I update SM, I have to manually download and install again the language pack, for every single user and profile I have on this computer, and sometimes I even have to reactivate and set again the default language. It would be nice if, like every other addon (like Lightning, which always needs to be updated after every SM update), it was automatically updated (eg, when I update SM to 2.11 every language pack I have is updated to 2.11). I haven't found any other report of this; is there a better place to report this? TIA -- Francesco ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Lost Bookmarks, SM 2.2 auto-update
User wrote: Daniel wrote: Daniel wrote: Robert Kaiser wrote: Daniel schrieb: Saturday night, I did the auto-update from SM 2.0.14 to SM 2.2 on my Mandriva Linux 2009.0 Now I find I've got an empty bookmarks file. Searching for Bookmark brings a zero result. It seems the only old site addresses I've keep are those in the address bar drop down. Try to go into the bookmarks manager and manually import the old bookmarks.html - I'm not really sure why sometimes this doesn't happen by default. :( Robert Kaiser Thanks for the very prompt reply, Robert, but did you miss where I typed Searching for Bookmark brings a zero result?? This is not looking good, thenmust have been time to edit my Bookmarks file, anyway, I suppose. Either that or Back-up, Back-up, Back-up!! O.K., people, you can stop worrying!! I remembered I had more than on profile, so switched to one of the other profiles, found it still had a reasonably up to date bookmarks file, so exported that, changed profiles and imported the bookmarks file into the main profile. Phew!! Have you ever tried Mozbackup? http://mozbackup.jasnapaka.com/ Saved my butt more than once ;-) No, maybe next time!! -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Lost Bookmarks, SM 2.2 auto-update
Saturday night, I did the auto-update from SM 2.0.14 to SM 2.2 on my Mandriva Linux 2009.0 Now I find I've got an empty bookmarks file. Searching for Bookmark brings a zero result. It seems the only old site addresses I've keep are those in the address bar drop down. Anybody got any advise for me (apart from Back-up, Back-up, Back-up!!)? TIA -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Lost Bookmarks, SM 2.2 auto-update
Daniel schrieb: Saturday night, I did the auto-update from SM 2.0.14 to SM 2.2 on my Mandriva Linux 2009.0 Now I find I've got an empty bookmarks file. Searching for Bookmark brings a zero result. It seems the only old site addresses I've keep are those in the address bar drop down. Try to go into the bookmarks manager and manually import the old bookmarks.html - I'm not really sure why sometimes this doesn't happen by default. :( Robert Kaiser -- Note that any statements of mine - no matter how passionate - are never meant to be offensive but very often as food for thought or possible arguments that we as a community should think about. And most of the time, I even appreciate irony and fun! :) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Lost Bookmarks, SM 2.2 auto-update
Robert Kaiser wrote: Daniel schrieb: Saturday night, I did the auto-update from SM 2.0.14 to SM 2.2 on my Mandriva Linux 2009.0 Now I find I've got an empty bookmarks file. Searching for Bookmark brings a zero result. It seems the only old site addresses I've keep are those in the address bar drop down. Try to go into the bookmarks manager and manually import the old bookmarks.html - I'm not really sure why sometimes this doesn't happen by default. :( Robert Kaiser Thanks for the very prompt reply, Robert, but did you miss where I typed Searching for Bookmark brings a zero result?? This is not looking good, thenmust have been time to edit my Bookmarks file, anyway, I suppose. Either that or Back-up, Back-up, Back-up!! -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Lost Bookmarks, SM 2.2 auto-update
Daniel wrote: Robert Kaiser wrote: Daniel schrieb: Saturday night, I did the auto-update from SM 2.0.14 to SM 2.2 on my Mandriva Linux 2009.0 Now I find I've got an empty bookmarks file. Searching for Bookmark brings a zero result. It seems the only old site addresses I've keep are those in the address bar drop down. Try to go into the bookmarks manager and manually import the old bookmarks.html - I'm not really sure why sometimes this doesn't happen by default. :( Robert Kaiser Thanks for the very prompt reply, Robert, but did you miss where I typed Searching for Bookmark brings a zero result?? This is not looking good, thenmust have been time to edit my Bookmarks file, anyway, I suppose. Either that or Back-up, Back-up, Back-up!! O.K., people, you can stop worrying!! I remembered I had more than on profile, so switched to one of the other profiles, found it still had a reasonably up to date bookmarks file, so exported that, changed profiles and imported the bookmarks file into the main profile. Phew!! -- Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Version 2.2 auto update and versioning question.
Interviewed by CNN on 18/07/2011 02:07, Bill Davidsen told the world: From my view, in every release there are new features, improvements and bugfixes haven't come to my attention. I like a model where eventually you release something fully functional. I'm not entirely clear on the meaning of your phrasing here. But fully functional tends to be a moving target. I think for this model the spelling you want is bizarre. No, bazaar, like in Eric Raymond's book The Cathedral and the Bazaar. If you don't consider address book being broken to be pouring the chamber pot in the cistern, could you give an example of just how broken something would have to be before it gets fixed? Well, I don't consider the address book issue you mention anything -- I don't consider it serious, I don't consider it insignificant. I'm just barely aware that there is some sort of complaint regarding it. Since I'm not in the dev team and I don't make any sort of decisions regarding releases, my opinion in this particular issue is irrelevant. But, generally speaking, I would think that a chemspill issue might fit one of theses possibilities (not limited to them; these are the ones I could think of): - one where a large percentage of users would be unable to use the major features of the product; - one where there was a risk of serious dataloss (non-recoverable by reinstalling or reverting to the previous version); - one where there was a serious risk of an exploit by a malicious third-party compromising user privacy and data security. I admit I'm more offended by the fact that you don't consider the address book debacle or the reported offline imap deleting hundreds of messages serious enough to be fixed than by the fact that there is not QA, after years of working things becoming broken I assume user testing of beta versions is the only testing there is. As I said, I don't consider those issues anything; I'm barely aware of their existence and I have no role on the decision-making. I have no data and no opinion, beyond the fact that I'm using both IMAP and the address book and had no problems. As for the testing... yes, beta versions exist FOR user-testing. And I'm unaware of any other form of effective software testing. But then, I'm not a developer; there might be some sort of automated test suite that can help. I have a bet with someone here that the reaction to my post will be a personal attack on my tone, accusations of being a whiner, and no corrective response to the issues I raised. Unfortunately, your frustration is misdirected. I'm an user, same as you. I have no responsibilities in the decision-making process. Therefore, I feel no anger at your demands for explanations -- I'm not personally involved. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Sharp pocket calculator. *Added by TagZilla 0.066.2 running on Seamonkey 2.1 * 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: Version 2.2 auto update and versioning question.
On 7/18/2011 1:07 AM, Bill Davidsen wrote: I have a bet with someone here that the reaction to my post will be a personal attack on my tone, accusations of being a whiner, and no corrective response to the issues I raised. Or more importantly I did not intend my original questions to be cause to debate the validity of the Mozilla foundation or the Seamonkey team's decisions. I mearly asked for clarification of a question and got great answers from three users. So lets try not to drag this thread down into a Seamonkey bashing thread. -Hawker ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Version 2.2 auto update and versioning question.
Thanx for everyone's answers. That was very helpful. Hawker On 7/15/2011 12:47 PM, The digits of Jens Hatlak's hands composed the following: hawker wrote: 1) I see my 2.0.x still says no update. Will there be a 2.2 auto update soon? There will be one but I cannot tell when. I'm wondering if I should install it or if I should wait for 2.2.1. I usually skip a X.0.0 release so I don't get the bad bugs (did not do 2.0 until 2.0.4 I think). You can install it at any time (from the official downloads). The auto update is just a convenience thing, the result will be the same. You may want to look at the release notes, especially the Known Issues sections, of the 2.1 and 2.2 releases. While 2.1 probably has more compatible add-ons, 2.2 is the latest release and contains some fixes (see the Changes page). It also contains a regression (drag and drop of address book entries doesn't work anymore), though. And don't wait for 2.2.1. The next version will be 2.3. 2) I'm just curious about versioning. Perhaps I just don't understand fully what changed. From what I understand 2.1 has a decent number of changes. It perhaps should have been 2.5 not 2.1. But what I don't understand is I thought 2.2 was 2.1 with bug fixes. It came out very fast after 2.1. Why is 2.2 not 2.1.1 or some such? What major changes under the hood happened? MCBastos already answered that in detail, I think. ;-) And yes, if I knew this rapid release train was coming, I would probably have voted to call 2.1 2.5 and 2.2 3.0. HTH Jens ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Version 2.2 auto update and versioning question.
MCBastos wrote: Interviewed by CNN on 15/07/2011 10:41, hawker told the world: This is not a flame, I've rewritten it twice to reduce personal criticism. It's just how I see the new model;. 2) I'm just curious about versioning. Perhaps I just don't understand fully what changed. From what I understand 2.1 has a decent number of changes. It perhaps should have been 2.5 not 2.1. But what I don't understand is I thought 2.2 was 2.1 with bug fixes. It came out very fast after 2.1. Why is 2.2 not 2.1.1 or some such? What major changes under the hood happened? OK. The Mozilla organization recently changed the update philosophy, from a traditional development model to what has been nicknamed the rapid-release train. Seamonkey, while strictly speaking is not part of the Mozilla organization, is closely related to it and highly dependent on the Firefox and Thunderbird projects. Therefore, it went along, partly because it's easier to sync efforts if both are in the same model. I have compared in the past the two development models to the publishing business: the traditional model is akin to writing a reference textbook, where you spend a long time researching the new edition while your publisher releases new printings of the old edition with minor updates and corrections for typos. The rapid-release train is more like publishing a periodical reference guide, such as a restaurant guide (perhaps the sort some newspapers give away every month) -- you don't expect it to be entirely rewritten every month, but there are always SOME changes. And you don't go back to press to correct typos on the May edition either, since the June edition will be ready pretty soon. Essentially, the rapid-release train does away with the distinction between major and minor versions -- it's somewhat in the middle: every release there's some improvement, and every release there are bugfixes too. From my view, in every release there are new features, improvements and bugfixes haven't come to my attention. I like a model where eventually you release something fully functional. There's also the cathedral-and-bazaar philosophies involved. The traditional model was developed for cathedral organizations, and carries with it some of the old assumptions -- that having all the changes released in a big lump is better than giving them out one at a time (this is specially attractive for commercial software companies, since big changes help enticing the customer into paying for upgrade fees), that distribution of new versions is slow and expensive, and so on. I think for this model the spelling you want is bizarre. But Mozilla is a collective, free (in both senses) software project. The bazaar approach is probably a better model of what is really happening. And one of the maxims of the bazaar model is release early, release often. And that's what's happening now. As for the version numbers themselves... they become pretty meaningless, despite the obvious (higher is newer). There are no clear distinctions between major and minor versions. Mozilla and Chrome went with major versions numbering, Seamonkey went with minor numbering, and some organizations use a somewhat-hybrid year.month numbering (which I, personally, think is the sanest long-term scheme). Third-level version numbers (x.x.1) are still used sometimes, for what Mozilla calls a chemspill release (and Seamonkey calls an oilspill) -- a fix for a bug so serious it CANNOT wait for the next cycle. But those are special cases, not to be considered in the normal release schedule. If you don't consider address book being broken to be pouring the chamber pot in the cistern, could you give an example of just how broken something would have to be before it gets fixed? I admit I'm more offended by the fact that you don't consider the address book debacle or the reported offline imap deleting hundreds of messages serious enough to be fixed than by the fact that there is not QA, after years of working things becoming broken I assume user testing of beta versions is the only testing there is. As for your more specific question, why is it 2.2 instead of 2.1.1.? Well, yes, the Seamonkey part of it was mostly bugfixes. However, the underlying Gecko engine (which comes from Mozilla) has new features, which are listed on the Release Notes. So, Seamonkey gets those new features too. So it's a valid version increment. As long as the really important things like version number are correct... I have a bet with someone here that the reaction to my post will be a personal attack on my tone, accusations of being a whiner, and no corrective response to the issues I raised. -- Bill Davidsen david...@tmr.com We are not out of the woods yet, but we know the direction and have taken the first step. The steps are many, but finite in number, and if we persevere we will reach our destination. -me, 2010 ___ support-seamonkey mailing
Version 2.2 auto update and versioning question.
Hey all, two questions. 1) I see my 2.0.x still says no update. Will there be a 2.2 auto update soon? I'm wondering if I should install it or if I should wait for 2.2.1. I usually skip a X.0.0 release so I don't get the bad bugs (did not do 2.0 until 2.0.4 I think). 2) I'm just curious about versioning. Perhaps I just don't understand fully what changed. From what I understand 2.1 has a decent number of changes. It perhaps should have been 2.5 not 2.1. But what I don't understand is I thought 2.2 was 2.1 with bug fixes. It came out very fast after 2.1. Why is 2.2 not 2.1.1 or some such? What major changes under the hood happened? Hawker ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Version 2.2 auto update and versioning question.
Interviewed by CNN on 15/07/2011 10:41, hawker told the world: 2) I'm just curious about versioning. Perhaps I just don't understand fully what changed. From what I understand 2.1 has a decent number of changes. It perhaps should have been 2.5 not 2.1. But what I don't understand is I thought 2.2 was 2.1 with bug fixes. It came out very fast after 2.1. Why is 2.2 not 2.1.1 or some such? What major changes under the hood happened? OK. The Mozilla organization recently changed the update philosophy, from a traditional development model to what has been nicknamed the rapid-release train. Seamonkey, while strictly speaking is not part of the Mozilla organization, is closely related to it and highly dependent on the Firefox and Thunderbird projects. Therefore, it went along, partly because it's easier to sync efforts if both are in the same model. I have compared in the past the two development models to the publishing business: the traditional model is akin to writing a reference textbook, where you spend a long time researching the new edition while your publisher releases new printings of the old edition with minor updates and corrections for typos. The rapid-release train is more like publishing a periodical reference guide, such as a restaurant guide (perhaps the sort some newspapers give away every month) -- you don't expect it to be entirely rewritten every month, but there are always SOME changes. And you don't go back to press to correct typos on the May edition either, since the June edition will be ready pretty soon. Essentially, the rapid-release train does away with the distinction between major and minor versions -- it's somewhat in the middle: every release there's some improvement, and every release there are bugfixes too. There's also the cathedral-and-bazaar philosophies involved. The traditional model was developed for cathedral organizations, and carries with it some of the old assumptions -- that having all the changes released in a big lump is better than giving them out one at a time (this is specially attractive for commercial software companies, since big changes help enticing the customer into paying for upgrade fees), that distribution of new versions is slow and expensive, and so on. But Mozilla is a collective, free (in both senses) software project. The bazaar approach is probably a better model of what is really happening. And one of the maxims of the bazaar model is release early, release often. And that's what's happening now. As for the version numbers themselves... they become pretty meaningless, despite the obvious (higher is newer). There are no clear distinctions between major and minor versions. Mozilla and Chrome went with major versions numbering, Seamonkey went with minor numbering, and some organizations use a somewhat-hybrid year.month numbering (which I, personally, think is the sanest long-term scheme). Third-level version numbers (x.x.1) are still used sometimes, for what Mozilla calls a chemspill release (and Seamonkey calls an oilspill) -- a fix for a bug so serious it CANNOT wait for the next cycle. But those are special cases, not to be considered in the normal release schedule. As for your more specific question, why is it 2.2 instead of 2.1.1.? Well, yes, the Seamonkey part of it was mostly bugfixes. However, the underlying Gecko engine (which comes from Mozilla) has new features, which are listed on the Release Notes. So, Seamonkey gets those new features too. So it's a valid version increment. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from The Voices in My Head. *Added by TagZilla 0.066.2 running on Seamonkey 2.1 * 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: Version 2.2 auto update and versioning question.
On 7/15/2011 9:41 AM, hawker wrote: 1) I see my 2.0.x still says no update. Will there be a 2.2 auto update soon? I'm wondering if I should install it or if I should wait for 2.2.1. I usually skip a X.0.0 release so I don't get the bad bugs (did not do 2.0 until 2.0.4 I think). There will be a 2.0-2.2 update offer within the week, there is absolutely no harm in updating to 2.2 directly. There will be no 2.2.1 or 2.1.1. You are right in that 2.1 would have been better called 2.5 or something, but the realization came much too late in our process for us to feel comfortable changing it. -- ~Justin Wood (Callek) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Version 2.2 auto update and versioning question.
hawker wrote: 1) I see my 2.0.x still says no update. Will there be a 2.2 auto update soon? There will be one but I cannot tell when. I'm wondering if I should install it or if I should wait for 2.2.1. I usually skip a X.0.0 release so I don't get the bad bugs (did not do 2.0 until 2.0.4 I think). You can install it at any time (from the official downloads). The auto update is just a convenience thing, the result will be the same. You may want to look at the release notes, especially the Known Issues sections, of the 2.1 and 2.2 releases. While 2.1 probably has more compatible add-ons, 2.2 is the latest release and contains some fixes (see the Changes page). It also contains a regression (drag and drop of address book entries doesn't work anymore), though. And don't wait for 2.2.1. The next version will be 2.3. 2) I'm just curious about versioning. Perhaps I just don't understand fully what changed. From what I understand 2.1 has a decent number of changes. It perhaps should have been 2.5 not 2.1. But what I don't understand is I thought 2.2 was 2.1 with bug fixes. It came out very fast after 2.1. Why is 2.2 not 2.1.1 or some such? What major changes under the hood happened? MCBastos already answered that in detail, I think. ;-) And yes, if I knew this rapid release train was coming, I would probably have voted to call 2.1 2.5 and 2.2 3.0. HTH Jens -- Jens Hatlak http://jens.hatlak.de/ SeaMonkey Trunk Tracker http://smtt.blogspot.com/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
