Re: Error Truncating The Inbox

[Danny Kile]

Richard Lee Holbert wrote:

I am running SeaMonkey 1.1.18 and when I turn my computer back on
after returning from work and check my e-mail, I get a message about
90% of the time stating:

"There was an error truncating the Inbox after filtering a message to
folder XYZ ( Insert name on one of my folders for XYZ ) . You may need to
shutdown SeaMonkey and delete inbox.msf ".

This hangs up my e-mail until I click on the OK Box in the message and
when download over 2000 e-mails when SeaMonkey starts back up, it
get's OLD Fast.

I have searched for this inbox.msf and cannot locate this folder.

After I first start SeaMonkey I still get the error about once every 50
or so messages.


In Seamonkey click on Edit > Mail & Newsgroup Account Settings > Server 
Settings for the Account in question. Then at the bottom of the window 
is a Local Directory, listing the path to your e-mail folder on the hard 
drive. You will find inbox.msf here.


Danny
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Philip Chee]

On Fri, 25 Feb 2011 10:59:04 -0800, NoOp wrote:

> I only checked the last 3; all are showing the same signature & crash
> cause and location:
> 
> 
> Signature: F1292875159
> Crash Reason  EXCEPTION_ACCESS_VIOLATION_READ
> Crash Address 0x9b8
> 
> 
> Signature: F1292875159
> Crash Reason  EXCEPTION_ACCESS_VIOLATION_READ
> Crash Address 0x9b8
> 
> 
> Signature: F1292875159
> Crash Reason  EXCEPTION_ACCESS_VIOLATION_READ
> Crash Address 0x9b8
> 
> Others:
> 
> 
> [Note that those are for 2.0.12 - and most show the same crash location]
> 
> Seems to be sufficent infor for a bug report. Go to the first one above
> & click on 'Bugzilla - Report this Crash'.

Hint. Look at the crash signature and the crashing thread frames 0-5. In
all three it looks like you are crashing in the flash player.

So file it under Plugins::Adobe Flash. And put the crash signature in
the Bug summary.
But first check that an existing bug hasn't already been filed.

Phil

-- 
Philip Chee , 
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Error Truncating The Inbox

[Paul]

Richard Lee Holbert wrote:
I am running SeaMonkey 1.1.18 and when I turn my computer back on 
after returning from work and check my e-mail, I get a message about 
90% of the time stating:


"There was an error truncating the Inbox after filtering a message to
 folder XYZ ( Insert name on one of my folders for XYZ ) . You may
need to shutdown SeaMonkey and delete inbox.msf ".

This hangs up my e-mail until I click on the OK Box in the message
and when download over 2000 e-mails when SeaMonkey starts back up, it
 get's OLD Fast.

I have searched for this inbox.msf and cannot locate this folder.

After I first start SeaMonkey I still get the error about once every
50 or so messages.


Mine is here in v1119:  Yours may be somewhere similar.
"C:\Documents and Settings\somenamehere\Application Data\Mozilla\Default
User\ynpmfpg6.slt\Mail\pop.att.yahoo.com\inbox.msf"
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

[Disregard] Re: [linux] Theme issues

[NoOp]

On 02/25/2011 05:09 PM, NoOp wrote:
> On my laptop using SM 2.0.x or 2.1.x I have a strange theme issue
> whereby every other newsgroup/subject line is greyed. This doesn't seem
> to be a problem with the subject line as I've changed my desktop theme
> to hightlight in red, but the Name column does not pick this up. A
> screenshot is here:
> 
> http://img339.imageshack.us/f/screenshotreseamonkeycr.png/
> 
> Notice that the newsgroup 'Name' is not highlighted the same. I've tried
> with a clean test profile and the problem still exists. Anyone else have
> similar?
> 
> Added info: Unbutu 10.10 linux, Ambiance theme
> Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11)
> Gecko/20110205 Firefox/4.0b11 SeaMonkey/2.1b2
> 
> I cannot reproduce on my desktop running the same, nor can I reproduce
> on WinXP with 2.1b2 in a virtual manager environment. I very much
> suspect that it's a desktop theme issue rather than a SM theme.

Definately a desktop theme issue. Switching to the Unity desktop theme
results in:
http://img826.imageshack.us/f/screenshotreseamonkeycr.png/

Sorry for the noise.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

[linux] Theme issues

[NoOp]

On my laptop using SM 2.0.x or 2.1.x I have a strange theme issue
whereby every other newsgroup/subject line is greyed. This doesn't seem
to be a problem with the subject line as I've changed my desktop theme
to hightlight in red, but the Name column does not pick this up. A
screenshot is here:

http://img339.imageshack.us/f/screenshotreseamonkeycr.png/

Notice that the newsgroup 'Name' is not highlighted the same. I've tried
with a clean test profile and the problem still exists. Anyone else have
similar?

Added info: Unbutu 10.10 linux, Ambiance theme
Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b11)
Gecko/20110205 Firefox/4.0b11 SeaMonkey/2.1b2

I cannot reproduce on my desktop running the same, nor can I reproduce
on WinXP with 2.1b2 in a virtual manager environment. I very much
suspect that it's a desktop theme issue rather than a SM theme.



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Error Truncating The Inbox

[Richard Lee Holbert]

I am running SeaMonkey 1.1.18 and when I turn my computer back on
after returning from work and check my e-mail, I get a message about
90% of the time stating:

"There was an error truncating the Inbox after filtering a message to
folder XYZ ( Insert name on one of my folders for XYZ ) . You may need to
shutdown SeaMonkey and delete inbox.msf ".

This hangs up my e-mail until I click on the OK Box in the message and
when download over 2000 e-mails when SeaMonkey starts back up, it
get's OLD Fast.

I have searched for this inbox.msf and cannot locate this folder.

After I first start SeaMonkey I still get the error about once every 50 
or so messages.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[NoOp]

On 02/25/2011 02:22 PM, Walter wrote:
> 
> 
> NoOp wrote:
>> On 02/25/2011 11:36 AM, Walter wrote:
>>>
>>>
>>> NoOp wrote:
>> ...
 Seems to be sufficent infor for a bug report. Go to the first one above
 &   click on 'Bugzilla - Report this Crash'.
>>>
>>>
>>> Bug # 636797 reported.
>>
>> You should include the crash report information/links in that&  and also
>> include the weather url that you were viewing when it kept crashing.
>> However, see Roberts info that F signatures are Flash related. So you
>> might check to see if you have the latest flash version&  perhaps try
>> clearing your cache (memory&  disk) to see if that has any effect.
>>
>> What flash version do you have installed? You can check in
>> 'about:plugins' and also:
>> http://flash.com
> 
> 
> Flash is current, weather URL is part of information included in crash 
> report.
> 
> At this point, I will just live with it and hope that next SM update 
> will have found and fixed it.
> 
> A big thanks for all the help and suggestions. I know just enough about 
> computers to be dangerous.
> 
> w

My point is that this is the entirety of your bug report:

Walter  2011-02-25 11:32:35 PST

User-Agent:   Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.16)
Gecko/20101123 SeaMonkey/2.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.16)
Gecko/20101123 SeaMonkey/2.0.11

Crashes with crash message and automatically reported to Mozilla. Results
posted to mozilla.support.seamonkey

Reproducible: Sometimes

Steps to Reproduce:
1. Cannot reproduce the problem.
2.
3.


You *need* to provide, as a minimum, the about:crashes info that you've
provided in this thread. No one will be able to determine what your
report is about with the information you provided.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Coming back to: my very useful form-filler/password storer won't work with SM 2x

[Ken]

cyberzen wrote:

form history control



Hi, cybercitizen.  I'm mainly interested in an integrated 
password-remembering tool, one that instantly makes the relevant 
Password and User Name ready to enter when one goes to a particular site 
(e.g., my banking site, my emails program after a reboot).  Nothing 
beats RoboCop if it's working, I suspect.  I WOULD love to have it 
working again!


Thanks - Ken (in Oz)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Walter]

NoOp wrote:

On 02/25/2011 11:36 AM, Walter wrote:



NoOp wrote:

...

Seems to be sufficent infor for a bug report. Go to the first one above
&   click on 'Bugzilla - Report this Crash'.



Bug # 636797 reported.


You should include the crash report information/links in that&  and also
include the weather url that you were viewing when it kept crashing.
However, see Roberts info that F signatures are Flash related. So you
might check to see if you have the latest flash version&  perhaps try
clearing your cache (memory&  disk) to see if that has any effect.

What flash version do you have installed? You can check in
'about:plugins' and also:
http://flash.com



Flash is current, weather URL is part of information included in crash 
report.


At this point, I will just live with it and hope that next SM update 
will have found and fixed it.


A big thanks for all the help and suggestions. I know just enough about 
computers to be dangerous.


w
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[NoOp]

On 02/25/2011 11:36 AM, Walter wrote:
> 
> 
> NoOp wrote:
...
>> Seems to be sufficent infor for a bug report. Go to the first one above
>> &  click on 'Bugzilla - Report this Crash'.
> 
> 
> Bug # 636797 reported.

You should include the crash report information/links in that & and also
include the weather url that you were viewing when it kept crashing.
However, see Roberts info that F signatures are Flash related. So you
might check to see if you have the latest flash version & perhaps try
clearing your cache (memory & disk) to see if that has any effect.

What flash version do you have installed? You can check in
'about:plugins' and also:
http://flash.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Chris Ilias]

On 11-02-25 12:18 PM, Walter wrote:

bp-e9c346b1-d2d2-4761-90f3-20ebb2110225 2/25/2011 10:47 AM
bp-d37e52eb-03d5-4c82-84ee-a9cdc2110224 2/24/2011 4:40 PM
bp-7dedc188-d492-43cf-b412-b8ba22110220 2/20/2011 6:07 PM


The cause seems to be an issue with the Flash plugin and DirectX.
Make sure that you are using the latest version of Flash. Go to 
 to find out.


--
Chris Ilias 
Newsgroup moderator
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[NoOp]

On 02/25/2011 11:02 AM, Robert Kaiser wrote:
> NoOp schrieb:
>> 
>> Signature: F1292875159
>> 
>> Signature: F1292875159
>> 
>> Signature: F1292875159
> 
> F* signatures are Flash crashing.
> 
> Robert Kaiser
> 
> 

Ah. Thanks for that.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Walter]

NoOp wrote:

On 02/25/2011 09:18 AM, Walter wrote:
...



  bp-e9c346b1-d2d2-4761-90f3-20ebb2110225   2/25/2011   10:47 AM
bp-d37e52eb-03d5-4c82-84ee-a9cdc2110224 2/24/2011   4:40 PM
bp-7dedc188-d492-43cf-b412-b8ba22110220 2/20/2011   6:07 PM


I only checked the last 3; all are showing the same signature&  crash
cause and location:


Signature: F1292875159
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x9b8


Signature: F1292875159
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x9b8


Signature: F1292875159
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x9b8

Others:


[Note that those are for 2.0.12 - and most show the same crash location]

Seems to be sufficent infor for a bug report. Go to the first one above
&  click on 'Bugzilla - Report this Crash'.



Bug # 636797 reported.

w
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Coming back to: my very useful form-filler/password storer won't work with SM 2x

[cyberzen]

Ken a écrit :

Guys, I did mention this back in December, but nothing much was
resolved.  And since then, I have a new computer.

I just saw the thread here called something like 'Message: Your browser
is not supported at this time'. Hmm. That was precisely what I was told
by the RoboForm people when I complained that my form-filler/password
rememberer - originally recommended to me by someone on this SM forum, I
think - doesn't integrate with SM 2x. 'Use Firefox instead', was their
suggestion. But I prefer the SM suite, thanks very much.

I still have RoboForm installed on my new computer, because it stores
scores of passwords for me. But I have to manually open it and copy
across the relevant password and/or user name on each occasion those are
needed (several times a day, often). RoboForm WON'T integrate with my SM
2x. And I can't add new passwords, etc., to its list.

But is there a way to fool it into thinking that my SM is really
Firefox? Or do people here have any other practical suggestions?

Thanks very much - Ken (in Oz)


have you tried
form history control

--
cyberzen
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Robert Kaiser]

NoOp schrieb:


Signature: F1292875159

Signature: F1292875159

Signature: F1292875159


F* signatures are Flash crashing.

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 needs answers to. 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: Seamonkey crash - still

[NoOp]

On 02/25/2011 09:18 AM, Walter wrote:
...
> 
> 
>  bp-e9c346b1-d2d2-4761-90f3-20ebb2110225  2/25/2011   10:47 AM
> bp-d37e52eb-03d5-4c82-84ee-a9cdc2110224   2/24/2011   4:40 PM
> bp-7dedc188-d492-43cf-b412-b8ba22110220   2/20/2011   6:07 PM

I only checked the last 3; all are showing the same signature & crash
cause and location:


Signature: F1292875159
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x9b8


Signature: F1292875159
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x9b8


Signature: F1292875159
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x9b8

Others:


[Note that those are for 2.0.12 - and most show the same crash location]

Seems to be sufficent infor for a bug report. Go to the first one above
& click on 'Bugzilla - Report this Crash'.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Message: Your browser is not supported at this time.

[JeffM]

hapihakr wrote:
>Use the user agent string option to masquerade as Firefox.
>
...or just don't visit sites built by chimps.

Thanks for posting to an 11-month old thread.

In addition:
The proper line length length for text in Usenet posts
is also much shorter than your post would indicate.
http://google.com/search?q=RFC+Usenet+%22.no-more-than-78-characters%22
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Walter]

Glen wrote:

Walter wrote:



Chris Ilias wrote:

On 11-02-24 10:42 PM, Michael Gordon wrote:

Robert Kaiser wrote:

Walter schrieb:

Still crashing occasionally. Below are details that are displayed.


Have you sent crash reports through our system? If so, can you
please go
to about:crashes and tell us the the crash IDs on those?


Try these with SM 2.0.x


The about:crashes page is going to list different crash IDs for each
person. So the crash IDs on your about:crashes page are not the ones in
Walter's.



Here are my crash reports from about:crashes
w




Remove Reports
Submitted Crash Reports






Report ID
Date Submitted




bp-e9c346b1-d2d2-4761-90f3-20ebb2110225 2/25/2011 10:47 AM
bp-d37e52eb-03d5-4c82-84ee-a9cdc2110224 2/24/2011 4:40 PM
bp-7dedc188-d492-43cf-b412-b8ba22110220 2/20/2011 6:07 PM
bp-f580f00e-0e4c-4554-8313-f112a2110217 2/17/2011 2:37 PM
bp-8379840a-9265-4d7d-8929-6701b2110215 2/15/2011 6:09 PM
bp-3dd7ab4c-2e21-4df9-ba10-9daba2110213 2/13/2011 3:57 PM
bp-45b59743-7b84-4522-bf9a-ad0ff2110213 2/13/2011 1:46 PM
bp-859a558c-8538-4dad-a60b-8dd852110212 2/12/2011 11:22 AM
bp-e8b481db-e5e3-41fe-8ea1-1a0222110211 2/11/2011 10:23 AM
bp-75f12d6f-4536-42a9-b8ed-4d0ff2110210 2/10/2011 2:45 PM
bp-76d7348c-d169-43f0-aed4-4ef442110209 2/9/2011 10:32 AM
bp-4a5d0b33-27b2-4901-b542-83cdd2110207 2/7/2011 4:46 PM
bp-3e05bc61-f2a4-42e3-985b-006b42110206 2/6/2011 1:08 PM
bp-0c8bd6d2-dfc8-4502-8e2d-cbbef2110205 2/5/2011 10:28 AM
bp-4810658d-38a9-4ea4-8992-325a62110203 2/3/2011 11:08 AM
bp-ebdd162a-d0ab-412c-8bd0-614412110201 2/1/2011 12:51 PM
bp-7c2e47ef-1aff-4871-8dd3-a91bc2110201 2/1/2011 11:45 AM
bp-02d84ae2-25cb-4b90-94f6-2a2952110131 1/31/2011 12:01 PM
bp-b49b0020-d8ad-45a8-8d4d-34e4a2110130 1/30/2011 2:57 PM
bp-730103dd-af72-46f0-a7c9-602e42110126 1/26/2011 10:36 AM
bp-a57a21ea-f27c-463d-9fca-cd1fc2110125 1/25/2011 11:32 AM
bp-9d8ba440-08e6-440b-b72f-268352110122 1/22/2011 11:12 AM
bp-a44511ae-c916-4016-b7db-2803c2110119 1/19/2011 1:23 PM
bp-4856865a-79d8-46b9-b888-c21892110119 1/19/2011 10:17 AM
bp-4dcf964c-7cea-48c5-a1b6-e17cc2110118 1/18/2011 3:08 PM
bp-9bf2f74f-e2a6-4daa-8881-4e1e42110111 1/11/2011 11:12 AM
bp-8ca831b4-3c60-4a98-a74a-d66732110110 1/10/2011 10:59 AM
bp-955000e7-f3f5-44bd-89d5-855da2101231 12/31/2010 11:11 AM
bp-a02878d9-322f-4b68-85aa-8f9132101230 12/30/2010 1:59 PM
bp-6ccdce26-640d-4e1b-8a85-4ef762101229 12/29/2010 11:31 AM
bp-055e734b-0b86-4c63-bc4e-2138a2101228 12/28/2010 11:41 AM
bp-7b019cfa-556b-45e9-ace9-6f59b2101227 12/27/2010 5:32 PM
bp-7eeed46c-692f-4071-856c-e867d2101226 12/26/2010 1:40 PM
bp-d57bb9d7-752a-4ed1-ab10-e0f772101225 12/25/2010 8:57 PM
bp-d2ce9c93-259c-4f29-9c8c-7b4332101224 12/24/2010 1:16 PM
bp-b299d413-816d-4ced-9f25-bccce2101220 12/20/2010 12:25 PM
bp-5546d42f-9526-4ee9-b359-2382e2101220 12/20/2010 11:47 AM
bp-41340ad5-fd9d-46f0-a18c-06a572101218 12/18/2010 2:09 PM
bp-eab755d9-f78c-425f-ab9f-f44952101216 12/16/2010 11:31 AM
bp-1916c33b-fb14-491b-82dd-18fc52101215 12/15/2010 5:47 PM
bp-6fd2eb75-ffc9-462b-ab40-e98612101212 12/12/2010 5:07 PM
bp-3c6613fc-7297-4db3-a2bb-d67b52101212 12/12/2010 4:47 PM
bp-e5f46306-0878-4fa0-ac10-2e7db2101207 12/7/2010 2:32 PM
bp-2a75c1a3-5ded-4133-bd79-adbb32101205 12/5/2010 4:41 PM
bp-6fe1b4e7-be0b-4b33-b86a-4f8d22101201 12/1/2010 10:13 AM
bp-987e6731-585f-4d0f-b131-26a262101130 11/30/2010 3:37 PM
bp-fb9e1e17-ca9d-4b3d-845b-66eb82101130 11/30/2010 3:04 PM
bp-19e786fa-ece5-4960-8849-ad5df2101129 11/29/2010 10:54 AM
bp-1868cb51-7b97-4075-9309-cb4662101129 11/29/2010 10:52 AM
bp-54b969b1-142c-49bb-9d3a-009852101129 11/29/2010 10:22 AM
bp-d6c29b3a-11c4-4cce-9917-d41492101128 11/28/2010 8:47 PM
bp-652d61bf-16ec-40bc-9323-1fbe92101025 10/25/2010 2:31 PM
bp-4cc23be8-8983-48e5-a5a0-2b2922100627 6/27/2010 1:44 PM
bp-cf71e4a4-b0b1-461e-ae03-e5c432100616 6/16/2010 1:42 PM




No crash reports have been submitted.

This application has not been configured to display crash reports. The
preference breakpad.reportURL must be set.



So it still crashes while trying to go into safe mode?



Have not tried safe mode yet. As long as I am running, "if it ain't 
broke, keep on truckin'"


w.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Glen]

Walter wrote:



Chris Ilias wrote:

On 11-02-24 10:42 PM, Michael Gordon wrote:

Robert Kaiser wrote:

Walter schrieb:

Still crashing occasionally. Below are details that are displayed.


Have you sent crash reports through our system? If so, can you
please go
to about:crashes and tell us the the crash IDs on those?


Try these with SM 2.0.x


The about:crashes page is going to list different crash IDs for each
person. So the crash IDs on your about:crashes page are not the ones in
Walter's.



Here are my crash reports from about:crashes
w




Remove Reports
Submitted Crash Reports






Report ID
Date Submitted




bp-e9c346b1-d2d2-4761-90f3-20ebb2110225 2/25/2011 10:47 AM
bp-d37e52eb-03d5-4c82-84ee-a9cdc2110224 2/24/2011 4:40 PM
bp-7dedc188-d492-43cf-b412-b8ba22110220 2/20/2011 6:07 PM
bp-f580f00e-0e4c-4554-8313-f112a2110217 2/17/2011 2:37 PM
bp-8379840a-9265-4d7d-8929-6701b2110215 2/15/2011 6:09 PM
bp-3dd7ab4c-2e21-4df9-ba10-9daba2110213 2/13/2011 3:57 PM
bp-45b59743-7b84-4522-bf9a-ad0ff2110213 2/13/2011 1:46 PM
bp-859a558c-8538-4dad-a60b-8dd852110212 2/12/2011 11:22 AM
bp-e8b481db-e5e3-41fe-8ea1-1a0222110211 2/11/2011 10:23 AM
bp-75f12d6f-4536-42a9-b8ed-4d0ff2110210 2/10/2011 2:45 PM
bp-76d7348c-d169-43f0-aed4-4ef442110209 2/9/2011 10:32 AM
bp-4a5d0b33-27b2-4901-b542-83cdd2110207 2/7/2011 4:46 PM
bp-3e05bc61-f2a4-42e3-985b-006b42110206 2/6/2011 1:08 PM
bp-0c8bd6d2-dfc8-4502-8e2d-cbbef2110205 2/5/2011 10:28 AM
bp-4810658d-38a9-4ea4-8992-325a62110203 2/3/2011 11:08 AM
bp-ebdd162a-d0ab-412c-8bd0-614412110201 2/1/2011 12:51 PM
bp-7c2e47ef-1aff-4871-8dd3-a91bc2110201 2/1/2011 11:45 AM
bp-02d84ae2-25cb-4b90-94f6-2a2952110131 1/31/2011 12:01 PM
bp-b49b0020-d8ad-45a8-8d4d-34e4a2110130 1/30/2011 2:57 PM
bp-730103dd-af72-46f0-a7c9-602e42110126 1/26/2011 10:36 AM
bp-a57a21ea-f27c-463d-9fca-cd1fc2110125 1/25/2011 11:32 AM
bp-9d8ba440-08e6-440b-b72f-268352110122 1/22/2011 11:12 AM
bp-a44511ae-c916-4016-b7db-2803c2110119 1/19/2011 1:23 PM
bp-4856865a-79d8-46b9-b888-c21892110119 1/19/2011 10:17 AM
bp-4dcf964c-7cea-48c5-a1b6-e17cc2110118 1/18/2011 3:08 PM
bp-9bf2f74f-e2a6-4daa-8881-4e1e42110111 1/11/2011 11:12 AM
bp-8ca831b4-3c60-4a98-a74a-d66732110110 1/10/2011 10:59 AM
bp-955000e7-f3f5-44bd-89d5-855da2101231 12/31/2010 11:11 AM
bp-a02878d9-322f-4b68-85aa-8f9132101230 12/30/2010 1:59 PM
bp-6ccdce26-640d-4e1b-8a85-4ef762101229 12/29/2010 11:31 AM
bp-055e734b-0b86-4c63-bc4e-2138a2101228 12/28/2010 11:41 AM
bp-7b019cfa-556b-45e9-ace9-6f59b2101227 12/27/2010 5:32 PM
bp-7eeed46c-692f-4071-856c-e867d2101226 12/26/2010 1:40 PM
bp-d57bb9d7-752a-4ed1-ab10-e0f772101225 12/25/2010 8:57 PM
bp-d2ce9c93-259c-4f29-9c8c-7b4332101224 12/24/2010 1:16 PM
bp-b299d413-816d-4ced-9f25-bccce2101220 12/20/2010 12:25 PM
bp-5546d42f-9526-4ee9-b359-2382e2101220 12/20/2010 11:47 AM
bp-41340ad5-fd9d-46f0-a18c-06a572101218 12/18/2010 2:09 PM
bp-eab755d9-f78c-425f-ab9f-f44952101216 12/16/2010 11:31 AM
bp-1916c33b-fb14-491b-82dd-18fc52101215 12/15/2010 5:47 PM
bp-6fd2eb75-ffc9-462b-ab40-e98612101212 12/12/2010 5:07 PM
bp-3c6613fc-7297-4db3-a2bb-d67b52101212 12/12/2010 4:47 PM
bp-e5f46306-0878-4fa0-ac10-2e7db2101207 12/7/2010 2:32 PM
bp-2a75c1a3-5ded-4133-bd79-adbb32101205 12/5/2010 4:41 PM
bp-6fe1b4e7-be0b-4b33-b86a-4f8d22101201 12/1/2010 10:13 AM
bp-987e6731-585f-4d0f-b131-26a262101130 11/30/2010 3:37 PM
bp-fb9e1e17-ca9d-4b3d-845b-66eb82101130 11/30/2010 3:04 PM
bp-19e786fa-ece5-4960-8849-ad5df2101129 11/29/2010 10:54 AM
bp-1868cb51-7b97-4075-9309-cb4662101129 11/29/2010 10:52 AM
bp-54b969b1-142c-49bb-9d3a-009852101129 11/29/2010 10:22 AM
bp-d6c29b3a-11c4-4cce-9917-d41492101128 11/28/2010 8:47 PM
bp-652d61bf-16ec-40bc-9323-1fbe92101025 10/25/2010 2:31 PM
bp-4cc23be8-8983-48e5-a5a0-2b2922100627 6/27/2010 1:44 PM
bp-cf71e4a4-b0b1-461e-ae03-e5c432100616 6/16/2010 1:42 PM




No crash reports have been submitted.

This application has not been configured to display crash reports. The
preference breakpad.reportURL must be set.



So it still crashes while trying to go into safe mode?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Coming back to: my very useful form-filler/password storer won't work with SM 2x

[Ken]

Guys, I did mention this back in December, but nothing much was 
resolved.  And since then, I have a new computer.


I just saw the thread here called something like 'Message: Your browser 
is not supported at this time'.  Hmm.  That was precisely what I was 
told by the RoboForm people when I complained that my 
form-filler/password rememberer - originally recommended to me by 
someone on this SM forum, I think - doesn't integrate with SM 2x.  'Use 
Firefox instead', was their suggestion.  But I prefer the SM suite, 
thanks very much.


I still have RoboForm installed on my new computer, because it stores 
scores of passwords for me.  But I have to manually open it and copy 
across the relevant password and/or user name on each occasion those are 
needed (several times a day, often).  RoboForm WON'T integrate with my 
SM 2x.  And I can't add new passwords, etc., to its list.


But is there a way to fool it into thinking that my SM is really 
Firefox?  Or do people here have any other practical suggestions?


Thanks very much - Ken (in Oz)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Walter]

Chris Ilias wrote:

On 11-02-24 10:42 PM, Michael Gordon wrote:

Robert Kaiser wrote:

Walter schrieb:

Still crashing occasionally. Below are details that are displayed.


Have you sent crash reports through our system? If so, can you please go
to about:crashes and tell us the the crash IDs on those?


Try these with SM 2.0.x


The about:crashes page is going to list different crash IDs for each
person. So the crash IDs on your about:crashes page are not the ones in
Walter's.



Here are my crash reports from about:crashes
w




Remove Reports
Submitted Crash Reports






Report ID
Date Submitted




bp-e9c346b1-d2d2-4761-90f3-20ebb2110225 2/25/2011   10:47 AM
bp-d37e52eb-03d5-4c82-84ee-a9cdc2110224 2/24/2011   4:40 PM
bp-7dedc188-d492-43cf-b412-b8ba22110220 2/20/2011   6:07 PM
bp-f580f00e-0e4c-4554-8313-f112a2110217 2/17/2011   2:37 PM
bp-8379840a-9265-4d7d-8929-6701b2110215 2/15/2011   6:09 PM
bp-3dd7ab4c-2e21-4df9-ba10-9daba2110213 2/13/2011   3:57 PM
bp-45b59743-7b84-4522-bf9a-ad0ff2110213 2/13/2011   1:46 PM
bp-859a558c-8538-4dad-a60b-8dd852110212 2/12/2011   11:22 AM
bp-e8b481db-e5e3-41fe-8ea1-1a0222110211 2/11/2011   10:23 AM
bp-75f12d6f-4536-42a9-b8ed-4d0ff2110210 2/10/2011   2:45 PM
bp-76d7348c-d169-43f0-aed4-4ef442110209 2/9/201110:32 AM
bp-4a5d0b33-27b2-4901-b542-83cdd2110207 2/7/20114:46 PM
bp-3e05bc61-f2a4-42e3-985b-006b42110206 2/6/20111:08 PM
bp-0c8bd6d2-dfc8-4502-8e2d-cbbef2110205 2/5/201110:28 AM
bp-4810658d-38a9-4ea4-8992-325a62110203 2/3/201111:08 AM
bp-ebdd162a-d0ab-412c-8bd0-614412110201 2/1/201112:51 PM
bp-7c2e47ef-1aff-4871-8dd3-a91bc2110201 2/1/201111:45 AM
bp-02d84ae2-25cb-4b90-94f6-2a2952110131 1/31/2011   12:01 PM
bp-b49b0020-d8ad-45a8-8d4d-34e4a2110130 1/30/2011   2:57 PM
bp-730103dd-af72-46f0-a7c9-602e42110126 1/26/2011   10:36 AM
bp-a57a21ea-f27c-463d-9fca-cd1fc2110125 1/25/2011   11:32 AM
bp-9d8ba440-08e6-440b-b72f-268352110122 1/22/2011   11:12 AM
bp-a44511ae-c916-4016-b7db-2803c2110119 1/19/2011   1:23 PM
bp-4856865a-79d8-46b9-b888-c21892110119 1/19/2011   10:17 AM
bp-4dcf964c-7cea-48c5-a1b6-e17cc2110118 1/18/2011   3:08 PM
bp-9bf2f74f-e2a6-4daa-8881-4e1e42110111 1/11/2011   11:12 AM
bp-8ca831b4-3c60-4a98-a74a-d66732110110 1/10/2011   10:59 AM
bp-955000e7-f3f5-44bd-89d5-855da2101231 12/31/2010  11:11 AM
bp-a02878d9-322f-4b68-85aa-8f9132101230 12/30/2010  1:59 PM
bp-6ccdce26-640d-4e1b-8a85-4ef762101229 12/29/2010  11:31 AM
bp-055e734b-0b86-4c63-bc4e-2138a2101228 12/28/2010  11:41 AM
bp-7b019cfa-556b-45e9-ace9-6f59b2101227 12/27/2010  5:32 PM
bp-7eeed46c-692f-4071-856c-e867d2101226 12/26/2010  1:40 PM
bp-d57bb9d7-752a-4ed1-ab10-e0f772101225 12/25/2010  8:57 PM
bp-d2ce9c93-259c-4f29-9c8c-7b4332101224 12/24/2010  1:16 PM
bp-b299d413-816d-4ced-9f25-bccce2101220 12/20/2010  12:25 PM
bp-5546d42f-9526-4ee9-b359-2382e2101220 12/20/2010  11:47 AM
bp-41340ad5-fd9d-46f0-a18c-06a572101218 12/18/2010  2:09 PM
bp-eab755d9-f78c-425f-ab9f-f44952101216 12/16/2010  11:31 AM
bp-1916c33b-fb14-491b-82dd-18fc52101215 12/15/2010  5:47 PM
bp-6fd2eb75-ffc9-462b-ab40-e98612101212 12/12/2010  5:07 PM
bp-3c6613fc-7297-4db3-a2bb-d67b52101212 12/12/2010  4:47 PM
bp-e5f46306-0878-4fa0-ac10-2e7db2101207 12/7/2010   2:32 PM
bp-2a75c1a3-5ded-4133-bd79-adbb32101205 12/5/2010   4:41 PM
bp-6fe1b4e7-be0b-4b33-b86a-4f8d22101201 12/1/2010   10:13 AM
bp-987e6731-585f-4d0f-b131-26a262101130 11/30/2010  3:37 PM
bp-fb9e1e17-ca9d-4b3d-845b-66eb82101130 11/30/2010  3:04 PM
bp-19e786fa-ece5-4960-8849-ad5df2101129 11/29/2010  10:54 AM
bp-1868cb51-7b97-4075-9309-cb4662101129 11/29/2010  10:52 AM
bp-54b969b1-142c-49bb-9d3a-009852101129 11/29/2010  10:22 AM
bp-d6c29b3a-11c4-4cce-9917-d41492101128 11/28/2010  8:47 PM
bp-652d61bf-16ec-40bc-9323-1fbe92101025 10/25/2010  2:31 PM
bp-4cc23be8-8983-48e5-a5a0-2b2922100627 6/27/2010   1:44 PM
bp-cf71e4a4-b0b1-461e-ae03-e5c432100616 6/16/2010   1:42 PM




No crash reports have been submitted.

This application has not been configured to display crash reports. The 
preference breakpad.reportURL must be set.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Glen]

Walter wrote:



Paul Bergsagel wrote:

Before you can be effectively you need to supply more information. What
Operating System are you running?

Walter wrote:


Still crashing occasionally. Below are details that are displayed.
w.



Add-ons:
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:1.3.3,{8A6C82A1-F6C9-481a-AAE7-C96444C9A754}:5.1.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:1.0,mod...@themes.mozilla.org:1.0



BuildID: 20101123124820
CrashTime: 1298587194
Email: w.john.son.1...@gmail.com
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 340326
StartupTime: 1298587156
Theme: classic/1.0
Throttleable: 1
URL:
http://local.msn.com/weather.aspx?q=De%20Kalb-TX&zip=75559&eid=153989639
Vendor: Mozilla
Version: 2.0.11

This report also contains technical information about




Running Windows 7 Premium on a HP p6204y desktop, 6gb memory, 750gb hard
drive.

Another crash today just after boot, accessing first link:

Add-ons:
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:1.3.3,{8A6C82A1-F6C9-481a-AAE7-C96444C9A754}:5.1.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:1.0,mod...@themes.mozilla.org:1.0

BuildID: 20101123124820
CrashTime: 1298652431
Email: w.john.son.1...@gmail.com
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 65237
StartupTime: 1298652414
Theme: classic/1.0
Throttleable: 1
URL:
http://local.msn.com/weather.aspx?q=De%20Kalb-TX&zip=75559&eid=153989639
Vendor: Mozilla
Version: 2.0.11

This report also contains technical information about


I cannot see any pattern to crashes. Sometimes several days between
them, sometimes a few minutes. This has been going on since installation
of SM 2.0.11. This is second report of this but I got no resolution in
any of the comments of the first report. HELP?

Walter.

Any suggestions welcome.



Walter,
Did you try starting up SM in safe mode and see if it still crashes?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Walter]

Paul Bergsagel wrote:

Before you can be effectively you need to supply more information. What
Operating System are you running?

Walter wrote:


Still crashing occasionally. Below are details that are displayed.
w.



Add-ons:
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:1.3.3,{8A6C82A1-F6C9-481a-AAE7-C96444C9A754}:5.1.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:1.0,mod...@themes.mozilla.org:1.0


BuildID: 20101123124820
CrashTime: 1298587194
Email: w.john.son.1...@gmail.com
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 340326
StartupTime: 1298587156
Theme: classic/1.0
Throttleable: 1
URL:
http://local.msn.com/weather.aspx?q=De%20Kalb-TX&zip=75559&eid=153989639
Vendor: Mozilla
Version: 2.0.11

This report also contains technical information about




Running Windows 7 Premium on a HP p6204y desktop, 6gb memory, 750gb hard 
drive.


Another crash today just after boot, accessing first link:

Add-ons: 
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:1.3.3,{8A6C82A1-F6C9-481a-AAE7-C96444C9A754}:5.1.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:1.0,mod...@themes.mozilla.org:1.0

BuildID: 20101123124820
CrashTime: 1298652431
Email: w.john.son.1...@gmail.com
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 65237
StartupTime: 1298652414
Theme: classic/1.0
Throttleable: 1
URL: 
http://local.msn.com/weather.aspx?q=De%20Kalb-TX&zip=75559&eid=153989639

Vendor: Mozilla
Version: 2.0.11

This report also contains technical information about


I cannot see any pattern to crashes. Sometimes several days between 
them, sometimes a few minutes. This has been going on since installation 
of SM 2.0.11. This is second report of this but I got no resolution in 
any of the comments of the first report. HELP?


Walter.

Any suggestions welcome.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Message: Your browser is not supported at this time.

[Paul B. Gallagher]

Beauregard T. Shagnasty wrote:


Paul B. Gallagher wrote:


But what will they do with all that money they save by building
only one version of their site? And how will their webmaster
survive on only a third of his former pay?


I'm guessing your post is tongue-in-cheek humor. That's okay.
However, it is not necessary to build multiple versions, not even for
multiple languages. If one writes code adhering to W3C standards,
browser *sniffing* is not required at all. This is not difficult.


Yes, that was humor, and yes, that's exactly my point.

--
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: Extension on Dual Boot system

[Terry R.]

On 2/25/2011 5:08 AM On a whim, Daniel pounded out on the keyboard


I dual boot my HP6730b Laptop with both Win7 and Mandriva Linux 2009.0
and have SM 2.0.11 on both.

Last Sunday evening, I deliberately booted into my Win7 system and
started up SeaMonkey to give it a chance to download any System and AV
updates.

Then I went looking, my SM was plain vanilla installation, so I went to
addons.mozilla.org (or whatever the site is) and installed about a half
dozen extensions like AdBlockPlus, BeeFree, Display mail route, Ghostery
and KaiRo.at Mandelbrot (whatever this does???).

The installations all went without a problem, so on Monday, when I
booted into my Linux SeaMonkey, I was expecting to have to install the
same extensions, but no, they were showing up there in my Linux SM already.

At first I thought "What the heck", but then I thought the Win7 SM
extensions would have been installed in the plug-ins folder {or
whatever} of my SM profile (which is, naturally, on a Win7 drive) and my
Linux SM uses the same profile, and, it would seem, the same plug-ins
folder {or whatever} of my SM profile (which is, naturally, on a Win7
drive because Linux can "see" Windows drives but Windows cannot "see"
Linux mount points.).

But isn't the code words used (whatever) for Windows going to be
different to the code words used for Linux (whatever)??

Anyone??

Daniel


Hi Daniel,

I don't use SM, but I have TB installed on multiple OS's.  I would 
create another partition and move your profile there to share data 
between.  I have all OS's each on a partition, data on another, and 
programs on another.  I separated all the mail/news data out of the 
profile into a separate folder, and that is what was shared with Linux. 
 The rest (add-ons etc) needs to be installed into each OS, unless you 
have many Windows OS's as I do. With those I can point to the same 
profile on each one.


I don't hardly use Linux at all any more (as no clients or friends ever 
used it and I only installed it for support purposes), but the above 
worked fine for sharing between them.



Terry R.
--
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Extension on Dual Boot system

[cyberzen]

Daniel a écrit :

I dual boot my HP6730b Laptop with both Win7 and Mandriva Linux 2009.0
and have SM 2.0.11 on both.

Last Sunday evening, I deliberately booted into my Win7 system and
started up SeaMonkey to give it a chance to download any System and AV
updates.

Then I went looking, my SM was plain vanilla installation, so I went to
addons.mozilla.org (or whatever the site is) and installed about a half
dozen extensions like AdBlockPlus, BeeFree, Display mail route, Ghostery
and KaiRo.at Mandelbrot (whatever this does???).

The installations all went without a problem, so on Monday, when I
booted into my Linux SeaMonkey, I was expecting to have to install the
same extensions, but no, they were showing up there in my Linux SM already.

At first I thought "What the heck", but then I thought the Win7 SM
extensions would have been installed in the plug-ins folder {or
whatever} of my SM profile (which is, naturally, on a Win7 drive) and my
Linux SM uses the same profile, and, it would seem, the same plug-ins
folder {or whatever} of my SM profile (which is, naturally, on a Win7
drive because Linux can "see" Windows drives but Windows cannot "see"
Linux mount points.).

But isn't the code words used (whatever) for Windows going to be
different to the code words used for Linux (whatever)??

Anyone??

Daniel


do you have the profile of Seamonkey in the same location for both 
linux/windows ?

the extensions are in the profile

--
cyberzen
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Extension on Dual Boot system

[Daniel]

I dual boot my HP6730b Laptop with both Win7 and Mandriva Linux 2009.0 
and have SM 2.0.11 on both.


Last Sunday evening, I deliberately booted into my Win7 system and 
started up SeaMonkey to give it a chance to download any System and AV 
updates.


Then I went looking, my SM was plain vanilla installation, so I went to 
addons.mozilla.org (or whatever the site is) and installed about a half 
dozen extensions like AdBlockPlus, BeeFree, Display mail route, Ghostery 
and KaiRo.at Mandelbrot (whatever this does???).


The installations all went without a problem, so on Monday, when I 
booted into my Linux SeaMonkey, I was expecting to have to install the 
same extensions, but no, they were showing up there in my Linux SM already.


At first I thought "What the heck", but then I thought the Win7 SM 
extensions would have been installed in the plug-ins folder {or 
whatever} of my SM profile (which is, naturally, on a Win7 drive) and my 
Linux SM uses the same profile, and, it would seem, the same plug-ins 
folder {or whatever} of my SM profile (which is, naturally, on a Win7 
drive because Linux can "see" Windows drives but Windows cannot "see" 
Linux mount points.).


But isn't the code words used (whatever) for Windows going to be 
different to the code words used for Linux (whatever)??


Anyone??

Daniel
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Message: Your browser is not supported at this time.

[Beauregard T. Shagnasty]

Paul B. Gallagher wrote:

> Beauregard T. Shagnasty wrote:
>> hapihakr wrote:
>>> Use the user agent string option to masquerade as Firefox. The
>>> following command will execute on Linux. Windows may be slightly
>>> different (both executable program and user agent string). 
>>> 
>>> google-chrome --user-agent="Mozilla/5.0 (X11; U; Linux x86_64;
>>> en-US; rv:1.9.2.13) Gecko/20101206 Linux Mint/9 (Isadora)
>>> Firefox/3.6.13"
>> 
>> Instead of changing to the Firefox UA string (which will reduce
>> SeaMonkey's market share), just add the following to the original:
>>
>>NOT Firefox/3.6.13
>>
>> The sniffers just look in the string for the word "Firefox". Better
>> yet, notify the web site to stop sniffing completely. If an author
>> builds a proper web site, it will/should work in any browser.
> 
> But what will they do with all that money they save by building only
> one version of their site? And how will their webmaster survive on
> only a third of his former pay?

I'm guessing your post is tongue-in-cheek humor. That's okay. However,
it is not necessary to build multiple versions, not even for multiple
languages. If one writes code adhering to W3C standards, browser
*sniffing* is not required at all. This is not difficult.

(Re the languages, the content is contained in a database and the
particular content is read and displayed by server-side scripts and
based on user choice of the language.)

-- 
   -bts
   -Four wheels carry the body; two wheels move the soul
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Message: Your browser is not supported at this time.

[Paul B. Gallagher]

Beauregard T. Shagnasty wrote:


hapihakr wrote:


Use the user agent string option to masquerade as Firefox. The
following command will execute on Linux. Windows may be slightly
different (both executable program and user agent string).

google-chrome --user-agent="Mozilla/5.0 (X11; U; Linux x86_64;
en-US; rv:1.9.2.13) Gecko/20101206 Linux Mint/9 (Isadora)
Firefox/3.6.13"


Instead of changing to the Firefox UA string (which will reduce
SeaMonkey's market share), just add the following to the original:

NOT Firefox/3.6.13

The sniffers just look in the string for the word "Firefox". Better
yet, notify the web site to stop sniffing completely. If an author
builds a proper web site, it will/should work in any browser.


But what will they do with all that money they save by building only one 
version of their site? And how will their webmaster survive on only a 
third of his former pay?


--
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: Message: Your browser is not supported at this time.

[Beauregard T. Shagnasty]

hapihakr wrote:

> Use the user agent string option to masquerade as Firefox. The
> following command will execute on Linux. Windows may be slightly
> different (both executable program and user agent string). 
> 
> google-chrome --user-agent="Mozilla/5.0 (X11; U; Linux x86_64; en-US;
> rv:1.9.2.13) Gecko/20101206 Linux Mint/9 (Isadora) Firefox/3.6.13"

Instead of changing to the Firefox UA string (which will reduce
SeaMonkey's market share), just add the following to the original:

   NOT Firefox/3.6.13

The sniffers just look in the string for the word "Firefox". Better yet,
notify the web site to stop sniffing completely. If an author builds a
proper web site, it will/should work in any browser.

-- 
   -bts
   -Four wheels carry the body; two wheels move the soul
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey