On 6/13/20 7:43 PM, Frank-Rainer Grahl wrote:
WaltS48 wrote:
On 6/13/20 4:41 PM, Ray_Net wrote:
WaltS48 wrote on 13-06-20 21:22:
On 6/13/20 2:40 PM, Don Spam's Reckless Son wrote:
WaltS48 wrote:
On 6/13/20 12:30 PM, Ray_Net wrote:
Don Spam's Reckless Son wrote on 13-06-20 17:43:
Ray_Net wrote:
Don Spam's Reckless Son wrote on 13-06-20 17:14:
Ray_Net wrote:
Hello;
This page:
https://mydrive.tomtom.com/fr_be/#+viewport=50.84627,4.3547,16,0,-0+ver=2
is ok, the map is visible with my SM on my old pc but not
visible on my new pc.
Same version of SM on both pc.
It works ok on my new pc with Google-Chrome.
Any idea ?
Works for me, the map is of Brussels. Did you post that
comment from your old machine or the new one? (suggestion,
reply from the other one and we can check user-agents).
On my old pc:
User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0)
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
On my new pc:
User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0)
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
Your add-ons are the same? If you have a script-blocker which
has been "trained" on the old machine, is the training on the
new one as well?
Restarting with add-ons disabled would maybe a good test there.
[ PARTIALLY SOLVED ]
I have also another problem on my new pc: the Google-Maps site
did not accept my search text.
I know that this problem is solved by stopping SM then restart it.
So i do it - and all goes well with Google-Maps.
Then I read your post and I was playing around, on my old pc,
without solution.
Finally I re-test the page:
https://mydrive.tomtom.com/fr_be/#+viewport=50.84627,4.3547,16,0,-0+ver=2
on my new pc and MIRACLE - all goes well.
So I have sometimes a problem affecting Google-Maps and
MyDrive-Tomtom.
This problem is avoided by re-booting SM.
Now ... How to find it ? That's another problem.
Update to at least SM 2.49.5?
<https://archive.mozilla.org/pub/seamonkey/releases/2.49.5/>
Although 2.53.2 is the current version at
<http://www.seamonkey-project.org/>
In case you don't know, if you update from 2.49.x to 2.53.x, you
can't fall back unless you saved your profile before the update and
reload it - the first time you execute 2.53.x it updates (converts)
your profile and makes it incompatable to the old level.
- in addition, 2.49.5 (and above) are also available as 64-bit
versions. If you want a 64-bit version then you download it,
uninstall your 32-bit version and install the new version. You
only need to do that when you migrate from 32-bit to 64-bit. The
profiles are compatable between 2.49.1 and 2.49.5.
Thanks for the reminder. :)
I'm just wondering why Ray_Net is still on an old SM 2.49.1.
I think that I use the 64bits SM seeing:
User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0)
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
Correct ?
What I will do is:
- Stopping SM - re-boot to be sure that SM is not running.
- Copy my profile somewhere.
- Uninstall my SM 2.49.1
- Install the SM 2.53.3 (I am waiting for this version)
Is it a good idea ?
No, just install 2.53.2 over 2.49.1 after backing up your profile in
case you want to go back to 2.49.whatever.
2.49.1 is x86 and if he wants x64 he should uninstall before.
FRG
Thanks, I wasn't aware of that!
--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
https://give.thunderbird.net/en-US/
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
