Re: SeaMonkey Crash Repair

[Connie]

On 16/09/2013 15:13, Daniel wrote:

Connie, I notice that you posted this message using SeaMonkey Version 2.16, but
in your post you are talking about SeaMonkey version 1.9. (As there was no
SeaMonkey version 1.9, I expect you mean SeaMonkey Version 1.1.9.) Are you aware
that there was a change in formatting for some of the SeaMonkey profile files in
the transition from version 2.0 to 2.1??

On your old computer, do a File Manager Search for your received e-mails file
which is called "inbox", without the inverted commas and without the ".msf" as
that file is just an index of the messages in your inbox. If/When you find this
file, report back for more directions.

If you need to re-download SeaMonkey 1.1.19, go here

http://www.seamonkey-project.org/releases/1.1.9


I've two machines.  The one I'm posting from isn't the one I've a problem with. 
 It's my other machine that has/is the problem.  That's the one that was 
running the old version.  Yes,  I did know about the changes.  I just want to 
try to restore the other machine to the way it was - if I can - then update in 
stages.  If it doesn't work, it doesn't.  I'll use it for testing programs


Thanks :))

--
Connie
http://oursalmons.wordpress.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Crash Repair

[Connie]

On 16/09/2013 14:40, Rob wrote:


No.
The bookmarks and mails are stored in your user profile, not in the software.
You can find your user profile and restore it from your backup.
It depends on your operating system where your user profile lives.


OK, thanks

--
Connie
http://oursalmons.wordpress.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey Crash Repair

[Daniel]

Connie wrote:

At the beginning of the year I had a strange crash which caused all my
bookmarks and email accounts to disappear but nothing else was
affected.  It was likened to being a new install.

I think I know what happened because the same thing happened again at
the weekend.  This time I saw what happened so was able to reverse it.

The version of SeaMonkey I was using at the beginning of the year was
1.9.  I still have a copy of that on the affected computer.  If I
reinstall that version, would I get back my original bookmarks and mails?


Connie, I notice that you posted this message using SeaMonkey Version 
2.16, but in your post you are talking about SeaMonkey version 1.9. (As 
there was no SeaMonkey version 1.9, I expect you mean SeaMonkey Version 
1.1.9.) Are you aware that there was a change in formatting for some of 
the SeaMonkey profile files in the transition from version 2.0 to 2.1??


On your old computer, do a File Manager Search for your received e-mails 
file which is called "inbox", without the inverted commas and without 
the ".msf" as that file is just an index of the messages in your inbox. 
If/When you find this file, report back for more directions.


If you need to re-download SeaMonkey 1.1.19, go here

http://www.seamonkey-project.org/releases/1.1.9

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130418192405


or

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 
Firefox/24.0 SeaMonkey/2.21 Build identifier: 20130827183508

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

Re: SeaMonkey Crash Repair

[Rob]

Connie  wrote:
> At the beginning of the year I had a strange crash which caused all my 
> bookmarks 
> and email accounts to disappear but nothing else was affected.  It was 
> likened 
> to being a new install.
>
> I think I know what happened because the same thing happened again at the 
> weekend.  This time I saw what happened so was able to reverse it.
>
> The version of SeaMonkey I was using at the beginning of the year was 1.9.  I 
> still have a copy of that on the affected computer.  If I reinstall that 
> version, would I get back my original bookmarks and mails?

No.
The bookmarks and mails are stored in your user profile, not in the software.
You can find your user profile and restore it from your backup.
It depends on your operating system where your user profile lives.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Connie]

Rob wrote:


You can even change the icon to something different for mail and browser.
There are icons predefined, click the "change icon" button in the shorcut
properties, browse to the location where you installed Seamonkey, then
to chrome, to icons and there you can select one of them.
(e.g. messengerWindow.ico for the mail shortcut)


Hallo

Thanks.  I'll bear that in mind.  For the moment I have the browser 
one to the left of the mail one and both have been renamed so a mouse 
hover confirms what they are.  They're essentially in the same 
position in relation to one another as they used to be; just not on 
opposite sides of the screen.


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

Re: SeaMonkey crash

[Rob]

Connie  wrote:
> Paul B. Gallagher wrote:
>
>> You can still have that, if you create two shortcuts, one for each
>> function.
>>
>> Right-click the shortcut and choose "Properties." For the target,
>> you'll see something like this:
>> "C:\Program Files (x86)\SeaMonkey\seamonkey.exe"
>>
>> Change it to read
>> "C:\Program Files (x86)\SeaMonkey\seamonkey.exe" -mail
>> and it will always open the mail application.
>>
>> Change it to read
>> "C:\Program Files (x86)\SeaMonkey\seamonkey.exe" -browser
>> and it will always open the browser.
>>
>> So if you create two different shortcuts with the two different
>> instructions, each will open the desired application.
>
> Thank you.  That's very handy.

You can even change the icon to something different for mail and browser.
There are icons predefined, click the "change icon" button in the shorcut
properties, browse to the location where you installed Seamonkey, then
to chrome, to icons and there you can select one of them.
(e.g. messengerWindow.ico for the mail shortcut)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Connie]

Ed Mullen wrote:


The problem is likely that the existing profile could not be used by
the current version because it was for a very old version of SM. What
version did you have before the upgrade?


Hallo

You'll have seen which version it was by now.  The problem was an 
association one.


I'd still like to now why that version of SeaMonkey crashed.

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

Re: SeaMonkey crash

[Connie]

Paul B. Gallagher wrote:


You can still have that, if you create two shortcuts, one for each
function.

Right-click the shortcut and choose "Properties." For the target,
you'll see something like this:
"C:\Program Files (x86)\SeaMonkey\seamonkey.exe"

Change it to read
"C:\Program Files (x86)\SeaMonkey\seamonkey.exe" -mail
and it will always open the mail application.

Change it to read
"C:\Program Files (x86)\SeaMonkey\seamonkey.exe" -browser
and it will always open the browser.

So if you create two different shortcuts with the two different
instructions, each will open the desired application.


Thank you.  That's very handy.

Connie in London


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

Re: SeaMonkey crash

[Connie]

Janine Starykowicz wrote:

See if you can import the old profile:
http://kb.mozillazine.org/Profile_migration_-_SeaMonkey


Hallo

Thank for the link.  It made more sense at a second reading.

Connie in London

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

Re: SeaMonkey crash

[Connie]

NoOp wrote:


Your election to wait to install 2.15.x across 400+ computers is, of
course your choice. It may even be a good choice in your
situation/environment, but in the interim your company is at risk to the
CVE's listed. That said, I'd be pretty hesitant to tell someone an
individual on this list to stay at a 2.14 release without (IMO) good
reason.


Hallo

I would have installed 2.14, even without Rob's sound advice to do so. 
 Even though, in your opinion, there's no good reason for being one 
step behind, I believe it does make sense.


There have been a number of threads about problems in the newest 
version. Every time there's a new release,  problems (for want of a 
better word), appear.  The release doesn't quite go the way it was 
expected/intended to a greater or lesser degree.  It doesn't matter 
how much beta testing there has been, it's only when a product is 
being operated by the intended users that other 
faults/errors/bugs/quirks will be found.  The reason being that most 
beta testers know what they are doing and customers don't - the latter 
just want to use the product.  It's like Rob says: he can pick up 
bugs/problems but others using the program in a different way will 
pick up different bugs/problems.


I used to write user manuals for systems I used myself.  The first 
instruction was not how to do a particular task - it was "turn on the 
machine"!  That may sound daft but there are users who /are/ that 
daft!  That's especially so when it's a new user or one unfamiliar 
with the system.


Now I'm retired, I do respite care with a severely disabled youngster. 
 I get the "experts" telling me how things /should/ be while I can 
see how things actually are.  The two seldom match because the 
"experts" are book learned and expect everything to be "by the book", 
whereas as I've learned by observation.  Life isn't "by the book" - 
nor is SeaMonkey in the hands of non tech users.  So when things go 
wrong, a nice, clear, calm, non tech,  plain English explanation is 
what's needed.

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

Re: SeaMonkey crash

[Connie]

Rob wrote:


Ok, that is great (and what was to be expected).
It tells you not to panic because something does not show up anymore :)


The email accounts didn't reappear so I'll have to sort that out tomorrow.


Yes that is what I said.  You need to create the mail accounts.  That
is normally very simple.

Your bookmarks are normally in the file places.sqlite that you can
copy over from the old to the new profile, but they are also backed
up regularly in a subfolder bookmarkbackups where you find several
files from different dates, and you can import those in the program.

Ok good luck.   But I still recommend you to implement some backup
solution to an external USB stick or disk.


Hallo

I only start to get anxious when it comes to the work I do on my computer.

Some of the folders within the accounts are missing but I should be 
able to rebuild them easily enough.


I'll have a look at the bookmark folders and subfolders later.

I did do a backup but it didn't appear to have worked.  Now I know 
what to look for, I'll make sure that's saved where I know to find it, 
together with your instructions for reinstalling.


Many thanks again for your help - and patience! :-)

Connie in London

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

Re: SeaMonkey crash

[Rob]

NoOp  wrote:
> On 01/24/2013 12:38 AM, Rob wrote:
>> NoOp  wrote:
>>> On 01/23/2013 01:23 PM, Connie wrote:
 NoOp wrote:
 
> I'd rethink taking that "advise" were I you:
> 
 
 Not take which advice?  Uninstalling the version already installed? 
 Installing over the top or not doing so?  Or not installing 2.14.1?
>>>
>>> Installing 2.14.1 instead of the current 2.15.1.
>>>
>>> Notice that 2.15 fixes 12 /Critical/ security issues, and 6 /High/
>>> security issues.
>> 
>> Wait.  Each and every new release combines security fixes with
>> functional changes and new bugs.   It is like that, no matter if
>> you like it or not.   It is not always good to install the latest
>> release, because they (lately) often come with critical problems
>> that affect the average user much much more than a security issue.
>
> So you are advising every "average user" here to back down to 2.14.1?

I have read several times here that users experience issues after the
upgrade to 2.15 and I think that people should know that the updates
that Mozilla tells them are for security are actually just snapshots
of an ongoing development process.  When they cannot live with the new
problems of a new release, they should stay at a release that proved
to work OK.   One of them is 2.12.1 and it looks like 2.14.1 is also
working reasonably as long as you don't specify a default fontsize in
the mail composition and do not change the fontsize yourself.

>> The security issue only hits you when you visit some infected site,
>> the new bugs often hit you all the time and right in the face.
>
> I recommend that you actually take the time to *read* the fixed security
> issues.
>
> And do you think you will have a heads up for every "infected site"? Or
> that all of the security fixes/vulnerabilities only involve the browser
> component?

Again, I consider security updates very important, but unfortunately
Mozilla doesn't issue them.

>> Watch for example what happened with IMAP mail in 2.13.  We had to
>> rollback the entire Seamonkey deployment in our company because of
>> critical bugs in 2.13.   Now we use 2.14.1 but I am again very
>> wary to upgrade without extensive testing and making sure there
>> are no stupid bugs like the font bug that was introduced into the
>> HTML editor (and forced us to disable font size changes in the
>> mail composition)
>
> Odd, I don't see that mentioned in your posts here. But see no
> improvement on the IMAP issues that I experience regardless of version.
> (I click on an IMAP account & get continuous download symptoms until I
> click away).

The discussion happened in Bugzilla, not here.

> Your election to wait to install 2.15.x across 400+ computers is, of
> course your choice. It may even be a good choice in your
> situation/environment, but in the interim your company is at risk to the
> CVE's listed. That said, I'd be pretty hesitant to tell someone an
> individual on this list to stay at a 2.14 release without (IMO) good
> reason.

We are not very much at risk, because our users work as nonprivileged
users, software installs are disabled (among other things locked down
using a long lockPref file), a software restriction policy is in place
that allows users only to execute programs installed by the admin in
directories users cannot write to, and a proxy is between the users
and internet that filters many threats.  And of course there is an
on-access virus/trojan scanner.

It is a much greater risk to the company when the users suddenly can't
use their e-mail, cannot access attachments they received, cannot
compose mail because of a custom setting they made, cannot edit an
intranet page because of a silly bug introduced in the browser, etc
etc etc.
It is a fact of life that every new release introduces high-profile
bugs, and it takes months or years to subsequently remove them.

>> With Mozilla you basically get security issues fixed only in the
>> "current version", and whenever a security bug is fixed they entice
>> you to upgrade to a new version with functional changes and new
>> bugs, that are fixed only very slowly.   This means that many users
>> just stay at (slightly) older versions.
>
> I reckon that with the 400 MSO (mail & browser) license fees that your
> company saves by using SeaMonkey, perhaps your company can contribute
> something to the SeaMonkey project?
> 
> 

Actually I have contributed many detailed issue reports in Bugzilla.
Unfortunately I have seen many times that a new version introduces a
critical bug in functionality that worked OK for a decade, I report
the bug immediately after the release, but then it takes months or
years before it gets looked at and possibly fixed.
I would expect bugs that describe regressions or new problems introduced
in recent releases to have a high priority and to 

Re: SeaMonkey crash

[NoOp]

On 01/24/2013 12:38 AM, Rob wrote:
> NoOp  wrote:
>> On 01/23/2013 01:23 PM, Connie wrote:
>>> NoOp wrote:
>>> 
 I'd rethink taking that "advise" were I you:
 
>>> 
>>> Not take which advice?  Uninstalling the version already installed? 
>>> Installing over the top or not doing so?  Or not installing 2.14.1?
>>
>> Installing 2.14.1 instead of the current 2.15.1.
>>
>> Notice that 2.15 fixes 12 /Critical/ security issues, and 6 /High/
>> security issues.
> 
> Wait.  Each and every new release combines security fixes with
> functional changes and new bugs.   It is like that, no matter if
> you like it or not.   It is not always good to install the latest
> release, because they (lately) often come with critical problems
> that affect the average user much much more than a security issue.

So you are advising every "average user" here to back down to 2.14.1?

> 
> The security issue only hits you when you visit some infected site,
> the new bugs often hit you all the time and right in the face.

I recommend that you actually take the time to *read* the fixed security
issues.

And do you think you will have a heads up for every "infected site"? Or
that all of the security fixes/vulnerabilities only involve the browser
component?

> 
> Watch for example what happened with IMAP mail in 2.13.  We had to
> rollback the entire Seamonkey deployment in our company because of
> critical bugs in 2.13.   Now we use 2.14.1 but I am again very
> wary to upgrade without extensive testing and making sure there
> are no stupid bugs like the font bug that was introduced into the
> HTML editor (and forced us to disable font size changes in the
> mail composition)

Odd, I don't see that mentioned in your posts here. But see no
improvement on the IMAP issues that I experience regardless of version.
(I click on an IMAP account & get continuous download symptoms until I
click away).

Your election to wait to install 2.15.x across 400+ computers is, of
course your choice. It may even be a good choice in your
situation/environment, but in the interim your company is at risk to the
CVE's listed. That said, I'd be pretty hesitant to tell someone an
individual on this list to stay at a 2.14 release without (IMO) good
reason.

> 
> Security issues are important, but functional bugs are also (and
> even more) important.  Unfortunately, Mozilla does not separate
> them like Microsoft does.   With Microsoft Internet Explorer we
> get functionally stable releases for which security bugs are solved
> with updates with as little functional impact as possible.

I see. Well I suppose... nah, never mind.

> With Mozilla you basically get security issues fixed only in the
> "current version", and whenever a security bug is fixed they entice
> you to upgrade to a new version with functional changes and new
> bugs, that are fixed only very slowly.   This means that many users
> just stay at (slightly) older versions.

I reckon that with the 400 MSO (mail & browser) license fees that your
company saves by using SeaMonkey, perhaps your company can contribute
something to the SeaMonkey project?




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

Re: SeaMonkey crash

[Rob]

NoOp  wrote:
> On 01/23/2013 01:23 PM, Connie wrote:
>> NoOp wrote:
>> 
>>> I'd rethink taking that "advise" were I you:
>>> 
>> 
>> Not take which advice?  Uninstalling the version already installed? 
>> Installing over the top or not doing so?  Or not installing 2.14.1?
>
> Installing 2.14.1 instead of the current 2.15.1.
>
> Notice that 2.15 fixes 12 /Critical/ security issues, and 6 /High/
> security issues.

Wait.  Each and every new release combines security fixes with
functional changes and new bugs.   It is like that, no matter if
you like it or not.   It is not always good to install the latest
release, because they (lately) often come with critical problems
that affect the average user much much more than a security issue.

The security issue only hits you when you visit some infected site,
the new bugs often hit you all the time and right in the face.

Watch for example what happened with IMAP mail in 2.13.  We had to
rollback the entire Seamonkey deployment in our company because of
critical bugs in 2.13.   Now we use 2.14.1 but I am again very
wary to upgrade without extensive testing and making sure there
are no stupid bugs like the font bug that was introduced into the
HTML editor (and forced us to disable font size changes in the
mail composition)

Security issues are important, but functional bugs are also (and
even more) important.  Unfortunately, Mozilla does not separate
them like Microsoft does.   With Microsoft Internet Explorer we
get functionally stable releases for which security bugs are solved
with updates with as little functional impact as possible.
With Mozilla you basically get security issues fixed only in the
"current version", and whenever a security bug is fixed they entice
you to upgrade to a new version with functional changes and new
bugs, that are fixed only very slowly.   This means that many users
just stay at (slightly) older versions.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Rob]

Connie  wrote:
> Rob wrote:
>
>> The bookmarks file is no longer used.  That info is now in places.sqlite.
>
>> When your current profile is different from the one where you found the
>> mail, you can create the required mail account in the new profile, then
>> close the program and using the explorer copy the folder Mail from the
>> old profile to the new profile.   This is where all your mail files are.
>>
>> When you then start Seamonkey again, the mail should be back.
>>
>> To be sure, I would install version 2.14.1 and not 2.15 or higher.
>> There appears to be a problem in that version, as I have seen a couple
>> of postings about suddenly losing the profile.
>
> Hallo
>
> Good news!
>
> I downloaded and installed 2.14.1.  Then copied the Profile folder to 
> a safe place.  Next checked the profile and opened SeaMonkey again.
>
> Success!!!
>
> *All* the local folders were there and so were the contents.  That's 
> where most of my work was stored.

Ok, that is great (and what was to be expected).
It tells you not to panic because something does not show up anymore :)

> The email accounts didn't reappear so I'll have to sort that out tomorrow.

Yes that is what I said.  You need to create the mail accounts.  That
is normally very simple.

> Thank you very very much for your help.  It is really appreciated.
>
> The browser has found both my home page (never used) and that I prefer 
> it to open on a blank page.  It hasn't picked up the bookmarks though 
> but I'll rebuild them from those I've salvaged.

Your bookmarks are normally in the file places.sqlite that you can
copy over from the old to the new profile, but they are also backed
up regularly in a subfolder bookmarkbackups where you find several
files from different dates, and you can import those in the program.

> Thank you again and a big hug.
>
> A very grateful and relieved Connie in London
> .

Ok good luck.   But I still recommend you to implement some backup
solution to an external USB stick or disk.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Connie]

NoOp wrote:


Installing 2.14.1 instead of the current 2.15.1.



You were asked yesterday what version(s)... the first guess was 2.4, but
then you replied: "No, that's not the problem version.  I'm using a
different machine at the moment."

Today you mention 1.1.14 "Will the mails and folders transfer intact
from my original 1.1.14 via 2.0.14 to a newer version or will it all
turn turtle again?".

o Can you confirm that 1.1.4 is the version that you are having issues
with?
o Can you please confirm what "different version" you tried installing
over 1.1.4?


Hallo

I have two machines.  One had 1.1.14 on it which crashed.  The other 
which I'm using at the moment has 2.4.


I didn't try to install a newer version (2.0.14)  over an old one 
(1.1.14).  I took out one and installed the other.  Both of those have 
now gone.


I've re-read the page Janine sent a link to and it now makes more 
sense to me.


I've followed what Rob said and I am cautiously optimistic.  I have 
99% of the mails.  The missing ones are where I've deleted them in 
webview but I could probably retrieve some of them so long as I 
haven't emptied the trash.


Connie in London


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

Re: SeaMonkey crash

[Connie]

Rob wrote:


The bookmarks file is no longer used.  That info is now in places.sqlite.



When your current profile is different from the one where you found the
mail, you can create the required mail account in the new profile, then
close the program and using the explorer copy the folder Mail from the
old profile to the new profile.   This is where all your mail files are.

When you then start Seamonkey again, the mail should be back.

To be sure, I would install version 2.14.1 and not 2.15 or higher.
There appears to be a problem in that version, as I have seen a couple
of postings about suddenly losing the profile.


Hallo

Good news!

I downloaded and installed 2.14.1.  Then copied the Profile folder to 
a safe place.  Next checked the profile and opened SeaMonkey again.


Success!!!

*All* the local folders were there and so were the contents.  That's 
where most of my work was stored.


The email accounts didn't reappear so I'll have to sort that out tomorrow.

Thank you very very much for your help.  It is really appreciated.

The browser has found both my home page (never used) and that I prefer 
it to open on a blank page.  It hasn't picked up the bookmarks though 
but I'll rebuild them from those I've salvaged.


Thank you again and a big hug.

A very grateful and relieved Connie in London
.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Paul B. Gallagher]

Connie wrote:


WaltS wrote:


I think he means the advice not to install 2.15.1, due to the known
security vulnerabilities that are fixed by an update from 2.14.


Hallo

Right.  I've gone with 2.14 for now.

I'm not sure I like it having to decide if I ALWAYS want SeaMonkey to
open to mail or to the browser.  It was handy having an icon in Quick
Launch (browser) and one in the systray (for mail).


You can still have that, if you create two shortcuts, one for each function.

Right-click the shortcut and choose "Properties." For the target, you'll 
see something like this:

"C:\Program Files (x86)\SeaMonkey\seamonkey.exe"

Change it to read
"C:\Program Files (x86)\SeaMonkey\seamonkey.exe" -mail
and it will always open the mail application.

Change it to read
"C:\Program Files (x86)\SeaMonkey\seamonkey.exe" -browser
and it will always open the browser.

So if you create two different shortcuts with the two different 
instructions, each will open the desired application.


--
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: SeaMonkey crash

[Connie]

WaltS wrote:


I think he means the advice not to install 2.15.1, due to the known
security vulnerabilities that are fixed by an update from 2.14.


Hallo

Right.  I've gone with 2.14 for now.

I'm not sure I like it having to decide if I ALWAYS want SeaMonkey to 
open to mail or to the browser.  It was handy having an icon in Quick 
Launch (browser) and one in the systray (for mail).


Connie in London

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

Re: SeaMonkey crash

[NoOp]

On 01/23/2013 01:23 PM, Connie wrote:
> NoOp wrote:
> 
>> I'd rethink taking that "advise" were I you:
>> 
> 
> Not take which advice?  Uninstalling the version already installed? 
> Installing over the top or not doing so?  Or not installing 2.14.1?

Installing 2.14.1 instead of the current 2.15.1.

Notice that 2.15 fixes 12 /Critical/ security issues, and 6 /High/
security issues.

Impact key:

Critical: Vulnerability can be used to run attacker code and install
software, requiring no user interaction beyond normal browsing.
High: Vulnerability can be used to gather sensitive data from sites
in other windows or inject data or code into those sites, requiring no
more than normal browsing actions.

> 
>> Janine provided you with the link to instructions:
>> 
>> /Read/ through that and then come back with questions.
> 
> Yes, I have read it but I don't fuly understand it.  I could 
> understand what Rob said.

"I've tried installing a different version of SeaMonkey but it isn't
associating with the other version's profile and I can't see any way
of doing it." ...

You were asked yesterday what version(s)... the first guess was 2.4, but
then you replied: "No, that's not the problem version.  I'm using a
different machine at the moment."

Today you mention 1.1.14 "Will the mails and folders transfer intact
from my original 1.1.14 via 2.0.14 to a newer version or will it all
turn turtle again?".

o Can you confirm that 1.1.4 is the version that you are having issues
with?
o Can you please confirm what "different version" you tried installing
over 1.1.4?



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

Re: SeaMonkey crash

[WaltS]

On 01/23/2013 04:23 PM, Connie wrote:

NoOp wrote:


I'd rethink taking that "advise" were I you:



Not take which advice?  Uninstalling the version already installed?
Installing over the top or not doing so?  Or not installing 2.14.1?


Janine provided you with the link to instructions:

/Read/ through that and then come back with questions.


Yes, I have read it but I don't fuly understand it.  I could
understand what Rob said.

Connie in London
.



I think he means the advice not to install 2.15.1, due to the known 
security vulnerabilities that are fixed by an update from 2.14.


--
Fedora 17 (64-bit) KDE 4.9.5
Thunderbird Release
Keeping users informed
Go Sabres and Pens!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Connie]

NoOp wrote:


I'd rethink taking that "advise" were I you:



Not take which advice?  Uninstalling the version already installed? 
Installing over the top or not doing so?  Or not installing 2.14.1?



Janine provided you with the link to instructions:

/Read/ through that and then come back with questions.


Yes, I have read it but I don't fuly understand it.  I could 
understand what Rob said.


Connie in London
.

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

Re: SeaMonkey crash

[NoOp]

On 01/23/2013 10:07 AM, NoOp wrote:
> On 01/23/2013 06:36 AM, Connie wrote:

Sorry, attibute should have added Rob:

On 01/23/2013 06:36 AM, Connie wrote:
> Rob wrote:

> ...
>>> To be sure, I would install version 2.14.1 and not 2.15 or higher.
>>> There appears to be a problem in that version, as I have seen a couple
>>> of postings about suddenly losing the profile.
>> 
>> Hallo
>> 
>> OK, I'll uninstall the current version of SeaMonkey and install 2.14.1 
>> or will the latter install over my current version?
> 
> I'd rethink taking that "advise" were I you:
> 
> 
>> 
>> Do I create each account, then copy across the mail folder to the new 
>> profile?  Sorry, if that's a basic (dozy) question but I don't want to 
>> mess everything up and lose all the mails since they seem to all be 
>> there right now.
> 
> Janine provided you with the link to instructions:
> 
> /Read/ through that and then come back with questions.
> 
> 

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

Re: SeaMonkey crash

[NoOp]

On 01/23/2013 06:36 AM, Connie wrote:
...
>> To be sure, I would install version 2.14.1 and not 2.15 or higher.
>> There appears to be a problem in that version, as I have seen a couple
>> of postings about suddenly losing the profile.
> 
> Hallo
> 
> OK, I'll uninstall the current version of SeaMonkey and install 2.14.1 
> or will the latter install over my current version?

I'd rethink taking that "advise" were I you:


> 
> Do I create each account, then copy across the mail folder to the new 
> profile?  Sorry, if that's a basic (dozy) question but I don't want to 
> mess everything up and lose all the mails since they seem to all be 
> there right now.

Janine provided you with the link to instructions:

/Read/ through that and then come back with questions.


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

Re: SeaMonkey crash

[Rob]

Connie  wrote:
> Rob wrote:
>
>> When your current profile is different from the one where you found the
>> mail, you can create the required mail account in the new profile, then
>> close the program and using the explorer copy the folder Mail from the
>> old profile to the new profile.   This is where all your mail files are.
>>
>> When you then start Seamonkey again, the mail should be back.
>>
>> To be sure, I would install version 2.14.1 and not 2.15 or higher.
>> There appears to be a problem in that version, as I have seen a couple
>> of postings about suddenly losing the profile.
>
> Hallo
>
> OK, I'll uninstall the current version of SeaMonkey and install 2.14.1 
> or will the latter install over my current version?

I always install the old version, then install the new one.  The uninstall
is very quick (5 seconds) so this should be no problem.

> Do I create each account, then copy across the mail folder to the new 
> profile?  Sorry, if that's a basic (dozy) question but I don't want to 
> mess everything up and lose all the mails since they seem to all be 
> there right now.
>
> Connie in London

Of course you can always copy that Mail folder where all your mail is
now to a safe place (e.g. in your documents directory) before doing
anything else.

In general, it would also be a good idea to make backups of a system
where you have valuable information.  Right now you have a small
problem because some linkage between the software and your information
has been disturbed.  But next time you can have a crashed disk or
stolen laptop and you simply lose everything without recourse.

USB memory sticks with multi-gigabyte capacity and external disks with
hundreds or thousands of gigabytes are very cheap these days, and you
can make backups of the whole system or just your own files on them.
Then, when you have problems you can always restore what you had last
time you made a backup.
(e.g. each week or each day when you have a lot of changing information)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Connie]

Rob wrote:


When your current profile is different from the one where you found the
mail, you can create the required mail account in the new profile, then
close the program and using the explorer copy the folder Mail from the
old profile to the new profile.   This is where all your mail files are.

When you then start Seamonkey again, the mail should be back.

To be sure, I would install version 2.14.1 and not 2.15 or higher.
There appears to be a problem in that version, as I have seen a couple
of postings about suddenly losing the profile.


Hallo

OK, I'll uninstall the current version of SeaMonkey and install 2.14.1 
or will the latter install over my current version?


Do I create each account, then copy across the mail folder to the new 
profile?  Sorry, if that's a basic (dozy) question but I don't want to 
mess everything up and lose all the mails since they seem to all be 
there right now.


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

Re: SeaMonkey crash

[Rob]

Connie  wrote:
> Rob wrote:
>
>> Open the windows file explorer (not the internet explorer) and go
>> to C:\Documents and Settings\Connie\Application Data\Mozilla.
>> It may be that you need to click away some notices by Windows that
>> you do not need to go there.   It may also be that you need to
>> go to Extra ->  Options and checkmark the "show hidden files" option.
>>
>> In that location you should find a profiles.ini and one or more
>> subfolders with funny names.  See what you have there, what date
>> and time there is on those folders and show us the content of that
>> profiles.ini file.
>>
>> That should help locating the folder that holds all your previous
>> mail and settings.
>
> Hallo
>
> Good news, bad news
>
> I've found the file but it's dated 18 Jan.  SeaMonkey was working fine 
> on 12 Jan.  It wasn't on 13 Jan.  The bookmarks is only 1KB and it 
> should be a /lot/ bigger than that.  An out of date version is 330KB. 
>   It probably should be closer to 500KB now.  It looks as though the 
> browser side is totally gone.  Two folders of collated bookmarks were 
> recently added to but I should be able to use the old version to 
> re-create the majority which I'll do manually.

The bookmarks file is no longer used.  That info is now in places.sqlite.

> Under the Mozilla heading, all the mail up to the crash date seems to 
> be there.  Looking at the Inbox file on one of the two main accounts, 
> it's showing 73,011 KB, which sounds about right.  The Inbox.msf file 
> is reading 183KB.  All the email accounts are there and a quick check 
> is showing that recently added folders under the Local Folders heading 
> are also there.
>
> Question is how do I get those mails and folders back?  Do I trust 

When your current profile is different from the one where you found the
mail, you can create the required mail account in the new profile, then
close the program and using the explorer copy the folder Mail from the
old profile to the new profile.   This is where all your mail files are.

When you then start Seamonkey again, the mail should be back.

To be sure, I would install version 2.14.1 and not 2.15 or higher.
There appears to be a problem in that version, as I have seen a couple
of postings about suddenly losing the profile.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Connie]

Rob wrote:


Open the windows file explorer (not the internet explorer) and go
to C:\Documents and Settings\Connie\Application Data\Mozilla.
It may be that you need to click away some notices by Windows that
you do not need to go there.   It may also be that you need to
go to Extra ->  Options and checkmark the "show hidden files" option.

In that location you should find a profiles.ini and one or more
subfolders with funny names.  See what you have there, what date
and time there is on those folders and show us the content of that
profiles.ini file.

That should help locating the folder that holds all your previous
mail and settings.


Hallo

Good news, bad news

I've found the file but it's dated 18 Jan.  SeaMonkey was working fine 
on 12 Jan.  It wasn't on 13 Jan.  The bookmarks is only 1KB and it 
should be a /lot/ bigger than that.  An out of date version is 330KB. 
 It probably should be closer to 500KB now.  It looks as though the 
browser side is totally gone.  Two folders of collated bookmarks were 
recently added to but I should be able to use the old version to 
re-create the majority which I'll do manually.


Under the Mozilla heading, all the mail up to the crash date seems to 
be there.  Looking at the Inbox file on one of the two main accounts, 
it's showing 73,011 KB, which sounds about right.  The Inbox.msf file 
is reading 183KB.  All the email accounts are there and a quick check 
is showing that recently added folders under the Local Folders heading 
are also there.


Question is how do I get those mails and folders back?  Do I trust 
SeaMonkey not to crash again given that those who've had a similar 
thing happen have been using different OSs and/or versions of 
SeaMonkey?  Or do I try Thunderbird if it's possible to transfer from 
one program to the other?  Will the mails and folders transfer intact 
from my original 1.1.14 via 2.0.14 to a newer version or will it all 
turn turtle again?


I know, loads of questions but I'm wary of SeaMonkey now.

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

Re: SeaMonkey crash

[Rob]

Connie  wrote:
> Rob wrote:
>>
>> Unfortunately it looks like some people have been hit by this problem
>> the past week.  I suggest you look in other threads to see what you
>> can do.  I don't think your work has been lost, it is just not
>> accessible at the moment.
>>
>> It is difficult to make recommendations without knowing what operating
>> system you use, how proficient you are with the system, etc.
>>
>> When you know what you are doing, look in the Application Data\Mozilla
>> folder of your user profile and describe what you see there.
>
> Hallo
>
> That's sort of comforting.  I'm using the mailing list rather than the 
> newsgroup.  I'll find the newsgroup.  I hope the work is just 
> temporarily inaccessible.
>
> I use XP.  I can manage some things but not poking around in the 
> registry.  I'll see if I can find that folder and let you know.

Open the windows file explorer (not the internet explorer) and go
to C:\Documents and Settings\Connie\Application Data\Mozilla.
It may be that you need to click away some notices by Windows that
you do not need to go there.   It may also be that you need to
go to Extra -> Options and checkmark the "show hidden files" option.

In that location you should find a profiles.ini and one or more
subfolders with funny names.  See what you have there, what date
and time there is on those folders and show us the content of that
profiles.ini file.

That should help locating the folder that holds all your previous
mail and settings.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Janine Starykowicz]

See if you can import the old profile:
http://kb.mozillazine.org/Profile_migration_-_SeaMonkey


Connie wrote:

Hallo

Last Saturday, SeaMonkey was working fine, as it should.  My PC booted
up as normal on Sunday morning.  I clicked on the email option got a
message saying I had to set up an email account in order to use it.

I tried the browser.  Instead of opening to a blank page, it opened on
the SeaMonkey home page.  The sidebar was open with a message to add
bookmarks to start using it.

I've lost a lot of valuable work as a result.

What concerns me is why it happened.  If it's happened once, it could
happen again.  It's making me concerned about using SeaMonkey any more.

I've tried installing a different version of SeaMonkey but it isn't
associating with the other version's profile and I can't see any way of
doing it.

Connie in London


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

Re: SeaMonkey crash

[NoOp]

On 01/22/2013 11:09 AM, Connie wrote:
> Rob wrote:
>>
>> Unfortunately it looks like some people have been hit by this problem
>> the past week.  I suggest you look in other threads to see what you
>> can do.  I don't think your work has been lost, it is just not
>> accessible at the moment.
>>
>> It is difficult to make recommendations without knowing what operating
>> system you use, how proficient you are with the system, etc.
>>
>> When you know what you are doing, look in the Application Data\Mozilla
>> folder of your user profile and describe what you see there.
> 
> Hallo
> 
> That's sort of comforting.  I'm using the mailing list rather than the 
> newsgroup.  I'll find the newsgroup.  I hope the work is just 
> temporarily inaccessible.
> 
> I use XP.  I can manage some things but not poking around in the 
> registry.  I'll see if I can find that folder and let you know.

http://kb.mozillazine.org/Profile_folder_-_SeaMonkey
...
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Ed Mullen]

Connie wrote:

WaltS wrote:


How can you make that recommendation when you don't know what
operating system Connie is using? :)

BTW her UA is showing, Mozilla/5.0 (Windows NT 5.1; rv:7.0)
Gecko/20110923 Firefox/7.0 SeaMonkey/2.4, but she doesn't tell us with
what SeaMonkey version she has the problem.

Is this the different version, or the problem version.


Hallo

No, that's not the problem version.  I'm using a different machine at
the moment.

It was a very old version I was using on my other machine.  I was going
to try updating it but real life problems got in the way.  So it didn't
happen.

Connie in London


The problem is likely that the existing profile could not be used by the 
current version because it was for a very old version of SM.  What 
version did you have before the upgrade?


--
Ed Mullen
http://edmullen.net/
If you mixed vodka with orange juice and Milk Of Magnesia, would you get 
a Philip's Screwdriver?

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

Re: SeaMonkey crash

[Paul B. Gallagher]

Connie wrote:


Hartmut Figge wrote:


Connie is obviously using a new profile. How this did happen is not
clear. It is quite possible that the original profile still exists.


Hallo

No, I wasn't using a new profile.  There was only one on the machine.
It was designated as the default.


You may not have /chosen/ to use a new profile, but it seems clear 
that's what you have.


--
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: SeaMonkey crash

[Connie]

Hartmut Figge wrote:


Connie is obviously using a new profile. How this did happen is not
clear. It is quite possible that the original profile still exists.


Hallo

No, I wasn't using a new profile.  There was only one on the machine. 
 It was designated as the default.


Connie in London



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

Re: SeaMonkey crash

[Connie]

WaltS wrote:


How can you make that recommendation when you don't know what
operating system Connie is using? :)

BTW her UA is showing, Mozilla/5.0 (Windows NT 5.1; rv:7.0)
Gecko/20110923 Firefox/7.0 SeaMonkey/2.4, but she doesn't tell us with
what SeaMonkey version she has the problem.

Is this the different version, or the problem version.


Hallo

No, that's not the problem version.  I'm using a different machine at 
the moment.


It was a very old version I was using on my other machine.  I was 
going to try updating it but real life problems got in the way.  So it 
didn't happen.


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

Re: SeaMonkey crash

[Connie]

Rob wrote:


Unfortunately it looks like some people have been hit by this problem
the past week.  I suggest you look in other threads to see what you
can do.  I don't think your work has been lost, it is just not
accessible at the moment.

It is difficult to make recommendations without knowing what operating
system you use, how proficient you are with the system, etc.

When you know what you are doing, look in the Application Data\Mozilla
folder of your user profile and describe what you see there.


Hallo

That's sort of comforting.  I'm using the mailing list rather than the 
newsgroup.  I'll find the newsgroup.  I hope the work is just 
temporarily inaccessible.


I use XP.  I can manage some things but not poking around in the 
registry.  I'll see if I can find that folder and let you know.


Connie in London



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

Re: SeaMonkey crash

[Connie]

Beauregard T. Shagnasty wrote:


Everything Connie wrote describes a blank (just-like-a-fresh-install)
profile. No email account, SeaMonkey home page, no bookmarks...


Hallo

Yes, that's /exactly/ what it was like, except it wasn't a fresh install.


Sounds more to me that your hard drive has corrupted your profile.

Reinstall the profile from your backup.


It was only SeaMonkey that was affected, nothing else which seems odd.

I'll see what I can do.

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

Re: SeaMonkey crash

[Hartmut Figge]

Beauregard T. Shagnasty:

>Everything Connie wrote describes a blank (just-like-a-fresh-install) 
>profile. No email account, SeaMonkey home page, no bookmarks...

Connie is obviously using a new profile. How this did happen is not
clear. It is quite possible that the original profile still exists.

Well, i do know nothing about Win, so i will shut up. :)

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

Re: SeaMonkey crash

[WaltS]

On 01/22/2013 01:29 PM, Rob wrote:

Connie  wrote:

Hallo

Last Saturday, SeaMonkey was working fine, as it should.  My PC booted
up as normal on Sunday morning.  I clicked on the email option got a
message saying I had to set up an email account in order to use it.

I tried the browser.  Instead of opening to a blank page, it opened on
the SeaMonkey home page.  The sidebar was open with a message to add
bookmarks to start using it.

I've lost a lot of valuable work as a result.

What concerns me is why it happened.  If it's happened once, it could
happen again.  It's making me concerned about using SeaMonkey any more.

I've tried installing a different version of SeaMonkey but it isn't
associating with the other version's profile and I can't see any way
of doing it.

Connie in London


Unfortunately it looks like some people have been hit by this problem
the past week.  I suggest you look in other threads to see what you
can do.  I don't think your work has been lost, it is just not
accessible at the moment.

It is difficult to make recommendations without knowing what operating
system you use, how proficient you are with the system, etc.

When you know what you are doing, look in the Application Data\Mozilla
folder of your user profile and describe what you see there.




How can you make that recommendation when you don't know what operating 
system Connie is using? :)


BTW her UA is showing, Mozilla/5.0 (Windows NT 5.1; rv:7.0) 
Gecko/20110923 Firefox/7.0 SeaMonkey/2.4, but she doesn't tell us with 
what SeaMonkey version she has the problem.


Is this the different version, or the problem version.

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

Re: SeaMonkey crash

[Beauregard T. Shagnasty]

Rob wrote:

> Beauregard T. Shagnasty  wrote:
>> Connie wrote:
>>
>>> Last Saturday, SeaMonkey was working fine, as it should.  My PC booted
>>> up as normal on Sunday morning.  I clicked on the email option got a
>>> message saying I had to set up an email account in order to use it.
>>> 
>>> I tried the browser.  Instead of opening to a blank page, it opened on
>>> the SeaMonkey home page.  The sidebar was open with a message to add
>>> bookmarks to start using it.
>>
>> Sounds more to me that your hard drive has corrupted your profile.
> 
> Hogwash.

Your hog is dirty?

Everything Connie wrote describes a blank (just-like-a-fresh-install) 
profile. No email account, SeaMonkey home page, no bookmarks...

-- 
   -bts
   -This space for rent, but the price is high
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Philip TAYLOR]

nom...@example.com wrote:

> Beauregard T. Shagnasty  wrote:

>> Sounds more to me that your hard drive has corrupted your profile.
> 
> Hogwash.

Is that a mis-spelled reference to the academy at which Harry Potter
studied or was it intended to be similar in meaning to "I respectfully
beg to disagree" ?

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

Re: SeaMonkey crash

[Rob]

Beauregard T. Shagnasty  wrote:
> Connie wrote:
>
>> Last Saturday, SeaMonkey was working fine, as it should.  My PC booted
>> up as normal on Sunday morning.  I clicked on the email option got a
>> message saying I had to set up an email account in order to use it.
>> 
>> I tried the browser.  Instead of opening to a blank page, it opened on
>> the SeaMonkey home page.  The sidebar was open with a message to add
>> bookmarks to start using it.
>
> Sounds more to me that your hard drive has corrupted your profile.

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

Re: SeaMonkey crash

[Rob]

Connie  wrote:
> Hallo
>
> Last Saturday, SeaMonkey was working fine, as it should.  My PC booted 
> up as normal on Sunday morning.  I clicked on the email option got a 
> message saying I had to set up an email account in order to use it.
>
> I tried the browser.  Instead of opening to a blank page, it opened on 
> the SeaMonkey home page.  The sidebar was open with a message to add 
> bookmarks to start using it.
>
> I've lost a lot of valuable work as a result.
>
> What concerns me is why it happened.  If it's happened once, it could 
> happen again.  It's making me concerned about using SeaMonkey any more.
>
> I've tried installing a different version of SeaMonkey but it isn't 
> associating with the other version's profile and I can't see any way 
> of doing it.
>
> Connie in London

Unfortunately it looks like some people have been hit by this problem
the past week.  I suggest you look in other threads to see what you
can do.  I don't think your work has been lost, it is just not
accessible at the moment.

It is difficult to make recommendations without knowing what operating
system you use, how proficient you are with the system, etc.

When you know what you are doing, look in the Application Data\Mozilla
folder of your user profile and describe what you see there.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SeaMonkey crash

[Beauregard T. Shagnasty]

Connie wrote:

> Last Saturday, SeaMonkey was working fine, as it should.  My PC booted
> up as normal on Sunday morning.  I clicked on the email option got a
> message saying I had to set up an email account in order to use it.
> 
> I tried the browser.  Instead of opening to a blank page, it opened on
> the SeaMonkey home page.  The sidebar was open with a message to add
> bookmarks to start using it.

Sounds more to me that your hard drive has corrupted your profile.

Reinstall the profile from your backup.

-- 
   -bts
   -This space for rent, but the price is high
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey crash - still

[Walter]

Robert Kaiser wrote:

Walter schrieb:

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


SeaMonkey updates cannot fix Flash crashing, very probably. The positive
side is that in 2.1 versions, SeaMonkey doen't crash when Flash crashes,
so you'll only get a sad face plugins symbol on the page because the
Flash plugin crashed, but the browser will still run.
You can try 2.1 Beta 2 if you dare to see that and confine the crash to
the plugin itself.

Robert Kaiser





Robert,

Thanks for the additional information. I think I will wait for the final 
version of 2.1 and live with the crashes. The only  problem is the 
nuisance of having to restart SM again and the second time I can go back 
to the exact same page and it works OK. Aren't computers wonderful? 
(when they work right?)


You guys do a remarkable job keeping SM up, running and current. Thanks 
for your efforts.


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

Re: Seamonkey crash - still

[Robert Kaiser]

Walter schrieb:

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


SeaMonkey updates cannot fix Flash crashing, very probably. The positive 
side is that in 2.1 versions, SeaMonkey doen't crash when Flash crashes, 
so you'll only get a sad face plugins symbol on the page because the 
Flash plugin crashed, but the browser will still run.
You can try 2.1 Beta 2 if you dare to see that and confine the crash to 
the plugin itself.


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

[Walter]

NoOp wrote:

On 02/26/2011 09:24 AM, Walter wrote:
...

My apologies for not including additional information on the bug report.
This is first time to submit a bug report and obviously another instance
of "knowing just enough to be dangerous".

I will continue running SM when it will run without crashes and restart
when it does crash in hopes somebody will look at all the information I
have posted in this forum and make sense of it.


Walter, I'll add information to the report for you.
https://bugzilla.mozilla.org/show_bug.cgi?id=636797





NOOP,

I truly appreciate that.

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

Re: Seamonkey crash - still

[NoOp]

On 02/26/2011 09:24 AM, Walter wrote:
...
> My apologies for not including additional information on the bug report. 
> This is first time to submit a bug report and obviously another instance 
> of "knowing just enough to be dangerous".
> 
> I will continue running SM when it will run without crashes and restart 
> when it does crash in hopes somebody will look at all the information I 
> have posted in this forum and make sense of it.

Walter, I'll add information to the report for you.
https://bugzilla.mozilla.org/show_bug.cgi?id=636797


___
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 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.




My apologies for not including additional information on the bug report. 
This is first time to submit a bug report and obviously another instance 
of "knowing just enough to be dangerous".


I will continue running SM when it will run without crashes and restart 
when it does crash in hopes somebody will look at all the information I 
have posted in this forum and make sense of it.


Again, thanks for your assistance.

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

Re: Seamonkey crash - still

[Rick Merrill]

NoOp wrote:
...

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'


Fascinating!  Glad to know about this.

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

Re: Seamonkey crash - still

[Daniel]

Walter wrote:



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.


...but, Walter, you are telling us that it is brokeat least very 
regularly!!.


Daniel
___
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: 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: 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: 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: 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

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: Seamonkey crash - still

[Chris Ilias]

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.


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

Re: Seamonkey crash - still

[Michael Gordon]

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?

Robert Kaiser




Robert,

Try these with SM 2.0.x

Report ID
Date Submitted




bp-cbf86791-3597-4a83-a8f1-951472110223 2/23/2011   7:36 PM
bp-e97424d5-df0c-4570-a173-384552110223 2/23/2011   7:17 PM
bp-0188fbfe-cb83-4a08-ace1-8f2b92110223 2/23/2011   7:16 PM
bp-4b522991-5eb5-4b01-94cf-08ddc2110223 2/23/2011   7:15 PM
bp-adc9714f-717c-4e44-a46f-5977a2110213 2/13/2011   7:45 PM
bp-345c6a7a-25e5-4c3c-b5ed-078462110213 2/13/2011   7:44 PM
bp-56fec057-d6a6-4aef-a6af-d624a2110213 2/13/2011   5:20 PM
bp-4d7b6ee6-642d-48a3-ad5a-cee8e2110213 2/13/2011   5:02 PM
bp-df7eb2e6-062c-4acd-a064-f13302110213 2/13/2011   4:45 PM
bp-3b14183d-a744-4c18-9b3d-2c8ba2110213 2/13/2011   4:45 PM
bp-0658b031-0595-49ee-89f0-dfae52110211 2/11/2011   11:07 PM
bp-8de3c0b4-ff33-42f7-b86a-97e232110211 2/11/2011   11:06 PM
bp-81f6bfcb-5785-494d-8d78-f93692110211 2/11/2011   7:31 PM
bp-4b0dc088-3ac5-47d6-a9d6-30b732110211 2/11/2011   7:30 PM
bp-f7b89f46-b5f6-4958-a4d5-e795f2110211 2/11/2011   7:30 PM
bp-92165148-1525-46ed-bdc1-c09142110209 2/9/20118:18 PM
bp-687112cd-4503-491e-beb2-547d52110209 2/9/20118:17 PM
bp-016e9be5-fb32-4ad1-85a7-1f3d22110209 2/9/20118:11 PM
bp-a8677efb-4094-4625-84a8-8111a2110209 2/9/20117:24 PM
bp-9bc039ca-447a-4f65-8631-b746b2110209 2/9/20117:23 PM
bp-1a01300e-a80b-4b73-856f-a189c2110206 2/6/20119:40 PM
bp-2968c463-25c3-4fa2-8cc8-f7e4d2110206 2/6/20119:39 PM
bp-8b0687de-faad-41d6-86eb-8a5002110206 2/6/20119:22 PM
bp-d73835b1-fde2-4122-9d20-8c9512110206 2/6/20118:56 PM
bp-3d1e29af-c118-41ca-90ef-8e8d92110206 2/6/20118:55 PM
bp-f3e9a95c-14c9-4423-8737-769c12110206 2/6/20118:51 PM
bp-95a44c5c-efa9-4445-8132-50adb2110205 2/5/20119:27 PM
bp-92be15b4-4648-45ca-a33d-55f762110205 2/5/20119:17 PM
bp-796a1c84-95ec-4724-a9b6-266b52110205 2/5/20119:16 PM
bp-179dc935-a585-449d-864e-d78de2110205 2/5/20119:04 PM
bp-b068e71b-6d8c-4d1d-a743-4a8752110203 2/3/20118:06 PM
bp-2bac57cd-f281-45b9-acfe-b749e2110202 2/2/20117:41 PM
bp-f31ab4a2-17d6-4c09-9207-cb0172110131 1/31/2011   7:20 PM
bp-99c65343-a097-4322-99e7-f0b6d2110131 1/31/2011   7:20 PM
bp-e9da002b-3a1a-4eac-8ceb-260d72110131 1/31/2011   7:19 PM
bp-708b8b02-0560-46dc-b42f-57fcb2110128 1/28/2011   10:17 PM
bp-1d14eb47-1b7f-49ec-b13b-bc9a72110128 1/28/2011   10:16 PM
bp-07aba9bf-b3db-4742-87cd-f8fd72110128 1/28/2011   10:16 PM
bp-cc65e6f3-bc51-4683-a6bb-a9c372110127 1/27/2011   8:25 PM
bp-f0393dfa-7190-42ae-ba3f-75fec2110127 1/27/2011   8:24 PM
bp-e0548f20-9287-48a7-a85b-ae4112110127 1/27/2011   8:07 PM
bp-fe022995-bc2b-435d-b238-f339a2110127 1/27/2011   8:07 PM
bp-da52c73f-f0ec-4e33-a86f-ba0892110127 1/27/2011   8:06 PM
bp-053559ab-c16c-4eca-a624-457f52110127 1/27/2011   8:05 PM
bp-ee032974-ce08-4233-a5db-d97c42110126 1/26/2011   7:51 PM
bp-07a3e7a2-f491-493a-875e-dbed72110126 1/26/2011   5:18 PM
bp-870d7da8-38cf-461b-94b3-179f62110126 1/26/2011   1:49 PM
bp-f73b3c0e-195c-4879-8701-952e42110125 1/25/2011   9:32 PM
bp-fa8ad2b4-8e89-44fe-a129-c6c7e2110125 1/25/2011   9:30 PM
bp-3f753a52-df55-4f22-bfe1-2b9a92110125 1/25/2011   9:18 PM
bp-02203ac9-501f-4593-a4a6-8de282110125 1/25/2011   9:09 PM
bp-79cf2e4b-d42a-497b-a105-424332110125 1/25/2011   5:04 PM
bp-86be-4690-4cdf-8d0c-1a66c2110125 1/25/2011   12:35 PM
bp-f362f5cf-a0fb-4054-98e1-d0ded2110124 1/24/2011   12:13 PM
bp-37ad42fb-77c4-4452-a020-878462110123 1/23/2011   11:10 PM
bp-6cc39ebf-24d4-4d31-9a87-96f0c2110121 1/21/2011   11:54 AM
bp-4876d1ed-ca51-476e-bb0f-2ba2a2110117 1/17/2011   8:14 PM
d203e4ca-fb69-47c6-8b46-e1847e4442271/16/2011   10:19 PM
45568881-db09-49d2-a265-28ea517db80d1/15/2011   9:03 PM
baffaf10-c11a-4a24-b3a2-058a5e59d8541/15/2011   9:02 PM
c15bdc01-b5ca-49c6-8890-7536f36cdaeb1/15/2011   9:02 PM
5835a2fa-1b95-48c4-9481-b986f36d54d11/15/2011   9:01 PM
eb22432c-b19d-4399-ad86-6f2537be4ef21/15/2011   9:01 PM
bp-ae5d408f-0aec-4d63-bd1f-08c972110112 1/12/2011   11:03 PM
bp-fdce1413-5caa-41ed-b7f5-e16612110112 1/12/2011   11:02 PM
bp-5b8acdd8-130c-4ef4-8db6-df77c2110112 1/12/2011   10:54 PM
bp-e397e292-7e7c-4028-85ac-a018b2110111 1/11/2011   11:12 AM
bp-377ffa65-a5dd-49f9-84cb-0e8b92110105 1/5/20117:27 PM
bp-5e8540b8-525c-46c1-a518-bdf6c2110105 1/5/20115:02 PM
bp-9935e52b-003f-412d-84c5-956282110105 1/5/20114:55 PM
bp-24682811-a5e8-45f6-bed6-17fbf2110105 1/5/20114:55 PM
bp-cefd8f71-5e63-430b-b667-7fe262110105 1/5/20114:54 PM
bp-358c0baf-7770-4f5a-a7a4-0f3f5

Re: Seamonkey crash - still

[Robert Kaiser]

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?


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

[Paul Bergsagel]

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


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

Re: Seamonkey Crash

[NoOp]

On 12/31/2010 11:11 AM, William Morrison wrote:
> Paul B. Gallagher wrote:
>> P.S. Adobe thinks I have version 10,1,102,64. It's only Mozilla's 
>> plugincheck that complains -- and that's because SM is reporting 
>> version 10.1 r102.
>>
>> 
>>
> I believe you're correct Paul as I have checked the above link with 
> Firefox 3.6.13  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; 
> rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13  and IE-8  Version 
> 8.0.6001.18702 along with Seamonkey 2.0.11  Mozilla/5.0 (Windows; U; 
> Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 and 
> the only one that shows that I need to update Flashplayer is Seamonkey.
> 

I have (linux):
$ apt-cache policy adobe-flashplugin
adobe-flashplugin:
  Installed: 10.1.102.65-2lucid1
  Candidate: 10.1.102.65-2lucid1
  Version table:
 *** 10.1.102.65-2lucid1 0
500 http://archive.canonical.com/ lucid/partner Packages
100 /var/lib/dpkg/status
Which is the most recent version for 32bit linux:
Download Adobe Flash Player
Adobe Flash Player version 10.1.102.65
Linux

But SeaMonkey (and Firefox) show:
SeaMonkey 2.0.11:
Shockwave Flash
File name: /usr/lib/adobe-flashplugin/libflashplayer.so
Shockwave Flash 10.1 r102
Firefox 3.6.13:
Shockwave Flash
File: /usr/lib/adobe-flashplugin/libflashplayer.so
Version:
Shockwave Flash 10.1 r102

so the plugin checker thinks my flash needs updating for both.

Looks like it's taking the strings from Shockwave Flash 10.1 r102 in the
file:
$ strings /usr/lib/adobe-flashplugin/libflashplayer.so | grep 10.1
FlashPlayer_10_1_102_65_FlashPlayer
Shockwave Flash 10.1 r102
10.1
Flash Player 10.1

LNX 10,1,102,65
and perhaps instead use "FlashPlayer_10_1_102_65_FlashPlayer"

Don't know if it's a Mozilla issue, or the way that Flash reports it's
version.

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

Re: Seamonkey Crash

[Chris Ilias]

On 10-12-31 12:57 PM, Walter wrote:

Crashed again after the reload of Flash. Again a copy of the error
report follows. The url is part of the report.


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


You latest crashes are the same type of crash as before. Try updating 
your installation of adblock plus.


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

Re: Seamonkey Crash

[William Morrison]

William Morrison wrote:

Paul B. Gallagher wrote:
P.S. Adobe thinks I have version 10,1,102,64. It's only Mozilla's 
plugincheck that complains -- and that's because SM is reporting 
version 10.1 r102.




I believe you're correct Paul as I have checked the above link with 
Firefox 3.6.13  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; 
rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13  and IE-8  Version 
8.0.6001.18702 along with Seamonkey 2.0.11  Mozilla/5.0 (Windows; U; 
Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 
and the only one that shows that I need to update Flashplayer is 
Seamonkey.


Correction not the above link but instead this link  
http://www.mozilla.com/en-US/plugincheck/#list-plugins  and I even just 
ran it using Google Chrome V8.0.552.224 and it too shows all up to date.

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

Re: Seamonkey Crash

[William Morrison]

Paul B. Gallagher wrote:
P.S. Adobe thinks I have version 10,1,102,64. It's only Mozilla's 
plugincheck that complains -- and that's because SM is reporting 
version 10.1 r102.




I believe you're correct Paul as I have checked the above link with 
Firefox 3.6.13  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; 
rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13  and IE-8  Version 
8.0.6001.18702 along with Seamonkey 2.0.11  Mozilla/5.0 (Windows; U; 
Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11 and 
the only one that shows that I need to update Flashplayer is Seamonkey.


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

Re: Seamonkey Crash

[Walter]

Chris Ilias wrote:

On 10-12-30 3:05 PM, Walter wrote:

Chris Ilias wrote:


Do you have a link to the crash report on
? If not, go to the address
"about:crashes" (without the quotes) and click on your latest crash
report. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.


Crashed again after the reload of Flash. Again a copy of the error
report follows. The url is part of the report.



We need the crash ID or report URL (found in about:crashes).




Here is latest crash details and about:crashes

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

BuildID: 20101123124820
CrashTime: 1293815455
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 76304
StartupTime: 1293815308
Theme: classic/1.0
Throttleable: 1
URL: 
http://apps.facebook.com/frontierville/giftaccept.php?next=giftaccept.php&senderId=1%3A1398567385&gh=548c0bc3b029eb11386009d01ead5c52&gift=fruitcake×tamp=1293762745&ref=free_thank_you&key=d9d40a8dd6c037f73823eae0afdea1f0%24%24cfO4S%2CVV53bZYhg8M-o-XQc!0YTONwNOK1hb)e)*8ewQ73GeYteuzcCyC(P!jRU&src=request&aff=gift&crt=fruitcake&signature=6ce67bf7269e24828c25523ce4aa1b8b

Vendor: Mozilla
Version: 2.0.11


and about-all

Submitted Crash Reports






Report ID
Date Submitted




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


Both of the above occurred minutes ago. This is no big deal but very 
annoying.


I am reading the posts about version # conflicts and wonder if there is 
a workaround on this.




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

Re: Seamonkey Crash

[JAS]

Paul B. Gallagher wrote:
> P.S. Adobe thinks I have version 10,1,102,64. It's only Mozilla's
> plugincheck that complains -- and that's because SM is reporting
> version 10.1 r102.
>
> 
>
I always have to go in an manually uninstall the old version. Usually at
C:\WINDOWS\system32\Macromed\Flash

-- 
   You either teach people to treat you with dignity and respect, or you don't. 
This means you are partly responsible for the mistreatment that you get at the 
hands of someone else. 

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

Re: Seamonkey Crash

[Paul B. Gallagher]

P.S. Adobe thinks I have version 10,1,102,64. It's only Mozilla's 
plugincheck that complains -- and that's because SM is reporting version 
10.1 r102.




--
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: Seamonkey Crash

[Paul B. Gallagher]

Chris Ilias wrote:


On 10-12-30 6:39 PM, Paul B. Gallagher wrote:


My system has Shockwave Flash 10.1 r102, which is reported as
"outdated," but the new version is 10.1.102.64, so I'm not too
terribly alarmed. At a certain level of subtlety, the site should
just say, "close enough for rock 'n' roll," don'tcha think?


The security vulnerabilities fixed in those Flash updates are huge.
That's one of the reasons why Mozilla created to plugin check page.


OK, your word "huge" was enough to alarm me, so I went to the Adobe site 
and installed both plugins. When I returned to the plugincheck page, it 
still didn't recognize Shockwave Flash 10.1 r102 as the current version, 
but it approved Shockwave for Director 11.5.9.615.


I concluded that either there's a bug in the way plugincheck matches 
version numbers reported by SeaMonkey to version numbers reported by 
Adobe, or Adobe's installer is failing to update my system, or SeaMonkey 
is not reporting version numbers correctly. So I went to Add/Remove 
programs, located the Adobe Flash Player 10 Plugin, and clicked for 
support information. Sure enough, the system reported my version as 
10.1.102.64, just as it should. The third theory (bad SM version 
reporting) seems to be confirmed. With version 10.1.102.64, SM is 
reporting version "10.1 r102," so of course plugincheck thinks it's a 
mismatch.


I would also add that I think it's inappropriate and misleading to patch 
a "huge" security hole (unless that was just hyperbole on your part) and 
use a version number that differs only in the fourth place. If it's that 
big a deal, the version numbering should be more obviously different.


--
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: Seamonkey Crash

[JD]

Chris Ilias wrote:

On 10-12-30 6:39 PM, Paul B. Gallagher wrote:

My system has Shockwave Flash 10.1 r102, which is reported as
"outdated," but the new version is 10.1.102.64, so I'm not too terribly
alarmed. At a certain level of subtlety, the site should just say,
"close enough for rock 'n' roll," don'tcha think?


The security vulnerabilities fixed in those Flash updates are huge.
That's one of the reasons why Mozilla created to plugin check page.



Chris..

I didn't know the page even existed.

http://www.mozilla.com/en-US/plugincheck/#list-plugins

One stop plug-in shopping.

Thanks!

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

Re: Seamonkey Crash

[Chris Ilias]

On 10-12-30 6:39 PM, Paul B. Gallagher wrote:

My system has Shockwave Flash 10.1 r102, which is reported as
"outdated," but the new version is 10.1.102.64, so I'm not too terribly
alarmed. At a certain level of subtlety, the site should just say,
"close enough for rock 'n' roll," don'tcha think?


The security vulnerabilities fixed in those Flash updates are huge. 
That's one of the reasons why Mozilla created to plugin check page.


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

Re: Seamonkey Crash

[Chris Ilias]

On 10-12-30 3:05 PM, Walter wrote:

Chris Ilias wrote:


Do you have a link to the crash report on
? If not, go to the address
"about:crashes" (without the quotes) and click on your latest crash
report. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.


Crashed again after the reload of Flash. Again a copy of the error
report follows. The url is part of the report.



We need the crash ID or report URL (found in about:crashes).

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

Re: Seamonkey Crash

[Paul B. Gallagher]

William Morrison wrote:


I have a question about this "plugincheck", I've ran it twice and
installed all of what it tells me needs updating but if I run it again
it still tells me that I need to update Shockwave Flash plugin. I've
installed it twice now with a coldboot after the second install and it
still shows an update available. What gives XP Home Sp3 Mozilla/5.0
(Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123
SeaMonkey/2.0.11


My system has Shockwave Flash 10.1 r102, which is reported as 
"outdated," but the new version is 10.1.102.64, so I'm not too terribly 
alarmed. At a certain level of subtlety, the site should just say, 
"close enough for rock 'n' roll," don'tcha think?


Similarly, I have Adobe Shockwave for Director Netscape plug-in, version 
11.5, but the latest version is 11.5.9.615 -- big f***in' deal.


Or maybe the plugincheck page isn't sophisticated enough to recognize 
notational equivalents?


--
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: Seamonkey Crash

[Walter]

Chris Ilias wrote:

On 10-12-28 12:37 PM, Walter wrote:

Chris Ilias wrote:

On 10-12-27 6:38 PM, Walter wrote:

Using CM 2.0.11 on HP P6204y, 6gb memory, 750 gb hard drive, Win 7 home
premium

I frequently get "Seamonkey crashed" quit Seamonkey or restart and
details.

Here are the details:

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



Any suggestions? This happens mostly on Facebook applications, though
not always. I can find no pattern.


Do you have a link to the crash report on
? If not, go to the address
"about:crashes" (without the quotes) and click on your latest crash
report. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.



I can access both links but they make absolutely no sense to me.
However, I get the following additional information on about:crashes
Maybe it will help in diagnosing the problem.


We need the URLs. They will make sense to us. :-)
(More specifically, we're looking for the crash signature)



Crashed again after the reload of Flash. Again a copy of the error 
report follows. The url is part of the report.


Walter.


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

BuildID: 20101123124820
CrashTime: 1293739151
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 95272
StartupTime: 1293737908
Theme: classic/1.0
Throttleable: 1
URL: 
http://www.popularmechanics.com/home/improvement/electrical-plumbing/18-strangest-bathrooms-in-the-world

Vendor: Mozilla
Version: 2.0.11

This report also contains technical information about
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Crash

[William Morrison]

Walter wrote:

Chris Ilias wrote:

On 10-12-29 12:19 PM, Walter wrote:

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


Are you using the latest version of Flash? Go to
 to find out.



I was not but now have installed it. Thanks for the help. I will see 
if that helps.


w.
I have a question about this "plugincheck", I've ran it twice and 
installed all of what it tells me needs updating but if I run it again 
it still tells me that I need to update Shockwave Flash plugin. I've 
installed it twice now with a coldboot after the second install and it 
still shows an update available. What gives XP Home Sp3 Mozilla/5.0 
(Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 
SeaMonkey/2.0.11


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

Re: Seamonkey Crash

[Walter]

Chris Ilias wrote:

On 10-12-29 12:19 PM, Walter wrote:

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


Are you using the latest version of Flash? Go to
 to find out.



I was not but now have installed it. Thanks for the help. I will see if 
that helps.


w.

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

Re: Seamonkey Crash

[Chris Ilias]

On 10-12-29 12:19 PM, Walter wrote:

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


Are you using the latest version of Flash? Go to 
 to find out.


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

Re: Seamonkey Crash

[Walter]

Chris Ilias wrote:

On 10-12-28 12:37 PM, Walter wrote:

Chris Ilias wrote:

On 10-12-27 6:38 PM, Walter wrote:

Using CM 2.0.11 on HP P6204y, 6gb memory, 750 gb hard drive, Win 7 home
premium

I frequently get "Seamonkey crashed" quit Seamonkey or restart and
details.

Here are the details:

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



Any suggestions? This happens mostly on Facebook applications, though
not always. I can find no pattern.


Do you have a link to the crash report on
? If not, go to the address
"about:crashes" (without the quotes) and click on your latest crash
report. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.



I can access both links but they make absolutely no sense to me.
However, I get the following additional information on about:crashes
Maybe it will help in diagnosing the problem.


We need the URLs. They will make sense to us. :-)
(More specifically, we're looking for the crash signature)




This from about:crashes which I have already sent but putting all 
information I have in one e-mail...



Remove Reports
Submitted Crash Reports






Report ID
Date Submitted




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.




This from crash data link


Mozilla Crash Reports
Product Navigation

* Product:
* Current 
Versions4.0b9pre4.0b83.6.134.0b8pre4.0b73.6.4pre3.6.33.6.14pre3.6.13pre3.6.12pre3.6.123.6.113.63.5.17pre3.5.16pre3.5.163.5.15pre3.5.153.5.14pre3.5.143.5.13 
Report: OverviewCrashes per UserNightly BuildsTop CrashersTop Crashers 
by URLTop Crashers by DomainTop Crashers by Topsite


Advanced Search
Firefox Crash Data

* 7 days
* 14 days
* 28 days

Crashes per Active Daily User
Dec 21
Dec 22
Dec 23
Dec 24
Dec 25
Dec 26
Dec 27
Dec 28
0
2
4
6
4.0b9pre
4.0b8
3.6.13
Firefox Top Crashers

* Top Crashers
* Top Changers

Firefox 4.0b9pre View all

nsRefPtr::assign_assuming_AddRef(mozilla::storage::BindingParamsArray*) 
| nsRefPtr::assign_with_AddRef(nsAccEventQueue*) | 
mozilla::layers::CairoImageD3D9::SetDevice(IDirect3DDevice9*)

1,779

nsRefPtr::assign_assuming_AddRef(mozilla::storage::BindingParamsArray*) 
| nsRefPtr::assign_with_AddRef(IDataObject*) | 
mozilla::layers::CairoImageD3D9::SetDevice(IDirect3DDevice9*)

1,179

nsRefPtr::assign_assuming_AddRef(nsFileControlFrame::CaptureMouseListener*) 
| nsRefPtr::assign_with_AddRef(nsInputStreamPump*) | 
mozilla::layers::CairoImageD3D9::SetDevice(IDirect3DDevice9*)

1,083

nsRefPtr::assign_assuming_AddRef(nsDOMAttributeMap*) 
| nsRefPtr::assign_with_AddRef(nsDOMFileList*) | 
mozilla::layers::CairoImageD3D9::SetDevice(IDirect3DDevice9*)

1,034

nsRefPtr::assign_assuming_AddRef(nsCookie*) | 
nsRefPtr::assign_with_AddRef(IDirect3DDevice9*) | 
mozilla::layers::CairoImageD3D9::SetDevice(IDirect3DDevice9*)

1,029

nsRefPtr::assign_assuming_AddRef(mozilla::imagelib::SVGRootRenderingObserver*) 
| 
nsRefPtr::assign_with_AddRef(mozilla::dom::indexedDB::IDBRequest*) 
| mozilla::layers::Cai...

971

nsRefPtr::assign_assuming_AddRef(nsPrincipal*) | 
nsRefPtr::assign_with_AddRef(IDirect3D9*) | 
nsRefPtr::oper

Re: Seamonkey Crash

[Chris Ilias]

On 10-12-28 12:37 PM, Walter wrote:

Chris Ilias wrote:

On 10-12-27 6:38 PM, Walter wrote:

Using CM 2.0.11 on HP P6204y, 6gb memory, 750 gb hard drive, Win 7 home
premium

I frequently get "Seamonkey crashed" quit Seamonkey or restart and
details.

Here are the details:

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


Any suggestions? This happens mostly on Facebook applications, though
not always. I can find no pattern.


Do you have a link to the crash report on
? If not, go to the address
"about:crashes" (without the quotes) and click on your latest crash
report. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.



I can access both links but they make absolutely no sense to me.
However, I get the following additional information on about:crashes
Maybe it will help in diagnosing the problem.


We need the URLs. They will make sense to us. :-)
(More specifically, we're looking for the crash signature)

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

Re: Seamonkey Crash

[Walter]

Chris Ilias wrote:

On 10-12-27 6:38 PM, Walter wrote:

Using CM 2.0.11 on HP P6204y, 6gb memory, 750 gb hard drive, Win 7 home
premium

I frequently get "Seamonkey crashed" quit Seamonkey or restart and
details.

Here are the details:

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


BuildID: 20101123124820
CrashTime: 1293492718
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 100274
StartupTime: 1293468218
Theme: classic/1.0
Throttleable: 1


Any suggestions? This happens mostly on Facebook applications, though
not always. I can find no pattern.


Do you have a link to the crash report on
? If not, go to the address
"about:crashes" (without the quotes) and click on your latest crash
report. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.



I can access both links but they make absolutely no sense to me. 
However, I get the following additional information on about:crashes 
Maybe it will help in diagnosing the problem.


Thanks, Walter.


Crashing Thread
Frame   Module  Signature [Expand]  Source
0 	NPSWF32.dll 	F1292875159_ 
F_1924533480__:29209
1 	NPSWF32.dll 	F957328252 
F58547254:494

2   user32.dll  InternalCallWinProc 
3   user32.dll  UserCallWinProcCheckWow 
4   user32.dll  DispatchMessageWorker   
5   user32.dll  DispatchMessageW
6 	seamonkey.exe 	nsAppShell::ProcessNextNativeEvent 
widget/src/windows/nsAppShell.cpp:165
7 	seamonkey.exe 	nsBaseAppShell::DoProcessNextNativeEvent 
widget/src/xpwidgets/nsBaseAppShell.cpp:151
8 	seamonkey.exe 	nsBaseAppShell::OnProcessNextEvent 
widget/src/xpwidgets/nsBaseAppShell.cpp:284
9 	xpcom_core.dll 	nsThread::ProcessNextEvent 
xpcom/threads/nsThread.cpp:508
10 	xpcom_core.dll 	NS_ProcessNextEvent_P 
objdir/mozilla/xpcom/build/nsThreadUtils.cpp:247
11 	seamonkey.exe 	nsBaseAppShell::Run 
widget/src/xpwidgets/nsBaseAppShell.cpp:170
12 	seamonkey.exe 	nsAppStartup::Run 
toolkit/components/startup/src/nsAppStartup.cpp:193

13  seamonkey.exe   XRE_maintoolkit/xre/nsAppRunner.cpp:3321
14  seamonkey.exe   NS_internal_mainsuite/app/nsSuiteApp.cpp:103
15  seamonkey.exe   wmain   toolkit/xre/nsWindowsWMain.cpp:110
16 	seamonkey.exe 	__tmainCRTStartup 
objdir/mozilla/memory/jemalloc/src/crtexe.c:591

17  kernel32.dllBaseThreadInitThunk 
18  ntdll.dll   __RtlUserThreadStart
19  ntdll.dll   _RtlUserThreadStart 

Show/hide other threads
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Crash

[Chris Ilias]

On 10-12-27 6:38 PM, Walter wrote:

Using CM 2.0.11 on HP P6204y, 6gb memory, 750 gb hard drive, Win 7 home
premium

I frequently get "Seamonkey crashed" quit Seamonkey or restart and details.

Here are the details:

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

BuildID: 20101123124820
CrashTime: 1293492718
InstallTime: 1292344168
ProductName: SeaMonkey
SecondsSinceLastCrash: 100274
StartupTime: 1293468218
Theme: classic/1.0
Throttleable: 1


Any suggestions? This happens mostly on Facebook applications, though
not always. I can find no pattern.


Do you have a link to the crash report on 
? If not, go to the address 
"about:crashes" (without the quotes) and click on your latest crash 
report. We can then look at the data specific to your crash and have a 
better idea of what is causing the problem.


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