Re: SeaMonkey Icon/Logo Idea

2015-03-16 Thread Geoff Welsh

David E. Ross wrote:

On 3/16/2015 4:51 PM, G. Ross wrote:

Ronnie wrote:

Hi all,

I'm the maintainer of LXLE Linux, some of you know we recently made the
move to SeaMonkey as our default web browser/suite.

I thought of this a while back but have not mentioned it yet. I think a
good change / update to SeaMonkey to perhaps give it a fresh identity
might be to ditch the blue actual seamonkey icon for perhaps a navigator
wheel similar to the Netscapes with a monkey in a pirate hat behind it
steering it.

Just a thought.

~Ronnie


I always change my icon to a ship's wheel anyway.



I leave the default icon alone for the SeaMonkey executable and for
Internet shortcuts (.URL files).  However, I replace the icon for .htm,
.html, .shtm, and .shtml files with my own enhanced Mozilla icon (the
red dragon's head on a background that shades from pale orange at the
top to dark orange at the bottom).  This helps to distinguish HTML files
from Internet shortcuts.



ah, yesThat old red Mozilla dragon was cool!

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


Re: Issues & solutions updating SeaMonkey 2.26.1 to 2.33

2015-03-16 Thread Ed Mullen

mozilla-lists.mbou...@spamgourmet.com wrote on 3/16/2015 3:21 PM:

Paul B. Gallagher wrote:

mozilla-lists.mbou...@spamgourmet.com wrote:


I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes
on a few issues and solutions I came across, in case they help anyone
else...

First off, back up your profile before updating - usually a good idea
anyway, just in case the new version messes something up in the profile
such that it won't even work in the old version.


1. Crash on Startup - due to missing xulstore.json
2. UI Customisations Lost - does anyone know a solution?
3. Saves Passwords Lost - fix found


1. Crash on Startup - due to missing xulstore.json




I didn't have this problem (xulstore.json didn't vanish), but it may be
relevant to your next issue:


It didn't vanish. It just wasn't present in my old profile from
SeaMonkey 2.26.1, and its absence caused a crash in SeaMonkey 2.33. From:
   http://kb.mozillazine.org/Localstore.rdf
it looks like xulstore.json replaces localstore.rdf as of "Mozilla 34"
(SeaMonkey 2.31?), so not expected to exist in 2.26.1. SM 2.33 was
crashing rather than converting the existing localstore.rdf or creating
a default version. Perhaps updating to SeaMonkey 2.31 first would have
converted localstore.rdf, and avoided the problem.


2. UI Customisations Lost - does anyone know a solution?

...


Have you tried restoring xulstore.json from backup?


I restored my entire profile from a backup created immediately before
updating, but there was no xulstore.json in that profile.


3. Saves passwords lost - fix found

...


Sorry, can't help with this.


No problem - the solution I linked to worked for me. I just mentioned it
in case it helps others.

Thanks,
Mark.



Which is why doing regular full backups of your data and system drives 
is critical.


My system does image backups daily of all my critical drives.

I've been advocating this here for years and people still don't get it. 
 They us Mozbackup as though that were the only thing to back up or the 
only way.


Having image backups is the only smart way to go.

With a good backup program even if your hard drive fails (and it will) 
you can restore to different hadware.


I hate to be harsh but I have no sympathy for anyone without a sound 
backup strategy.  When you lose your data don't ask me.



--
Ed Mullen
http://edmullen.net/
Can you buy anything specific at a general store?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SeaMonkey Icon/Logo Idea

2015-03-16 Thread David E. Ross
On 3/16/2015 4:51 PM, G. Ross wrote:
> Ronnie wrote:
>> Hi all,
>>
>> I'm the maintainer of LXLE Linux, some of you know we recently made the
>> move to SeaMonkey as our default web browser/suite.
>>
>> I thought of this a while back but have not mentioned it yet. I think a
>> good change / update to SeaMonkey to perhaps give it a fresh identity
>> might be to ditch the blue actual seamonkey icon for perhaps a navigator
>> wheel similar to the Netscapes with a monkey in a pirate hat behind it
>> steering it.
>>
>> Just a thought.
>>
>> ~Ronnie
>>
> I always change my icon to a ship's wheel anyway.
> 

I leave the default icon alone for the SeaMonkey executable and for
Internet shortcuts (.URL files).  However, I replace the icon for .htm,
.html, .shtm, and .shtml files with my own enhanced Mozilla icon (the
red dragon's head on a background that shades from pale orange at the
top to dark orange at the bottom).  This helps to distinguish HTML files
from Internet shortcuts.

-- 
David E. Ross

I am sticking with SeaMonkey 2.26.1 until saved passwords can
be used when autocomplete=off.  See
.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: SeaMonkey Icon/Logo Idea

2015-03-16 Thread G. Ross

Ronnie wrote:

Hi all,

I'm the maintainer of LXLE Linux, some of you know we recently made the
move to SeaMonkey as our default web browser/suite.

I thought of this a while back but have not mentioned it yet. I think a
good change / update to SeaMonkey to perhaps give it a fresh identity
might be to ditch the blue actual seamonkey icon for perhaps a navigator
wheel similar to the Netscapes with a monkey in a pirate hat behind it
steering it.

Just a thought.

~Ronnie


I always change my icon to a ship's wheel anyway.

--
 GW Ross 

 People who live in stone houses
 shouldn't throw glasses.   






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


Re: Question about Seamonkey's life plans

2015-03-16 Thread Peter Nieman

On 16/03/15 01:08, Edmund Wong wrote:

jeff.nee...@gmail.com wrote:

Hi.  I hope no one takes offense at my question.

Is Seamonkey going to be around for a while?  So many software developers
drop support for their products after a period of time.  I'm investing a
lot of time and interest in Seamonkey.

Is it thought that SM will continue to be developed?  One can only
remember
Mozilla stopping development on Thunderbird and wonder about the
future of
SM.


Both SeaMonkey and Thunderbird are still in development, although now
as community projects (made up of volunteers).

AFAIK, it's still being worked on, but, I might add, it does require
more contributors (esp. in terms of coding).


Have a look at this:
http://www.softmaker.com/english/ofwtb_en.htm

Good news, I think.

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


SeaMonkey Icon/Logo Idea

2015-03-16 Thread Ronnie
Hi all,

I'm the maintainer of LXLE Linux, some of you know we recently made the
move to SeaMonkey as our default web browser/suite.

I thought of this a while back but have not mentioned it yet. I think a
good change / update to SeaMonkey to perhaps give it a fresh identity
might be to ditch the blue actual seamonkey icon for perhaps a navigator
wheel similar to the Netscapes with a monkey in a pirate hat behind it
steering it.

Just a thought.

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


Re: Issues & solutions updating SeaMonkey 2.26.1 to 2.33

2015-03-16 Thread mozilla-lists . mbourne

Paul B. Gallagher wrote:

mozilla-lists.mbou...@spamgourmet.com wrote:


I've just updated SeaMonkey 2.26.1 to 2.33 on Windows Vista. Some notes
on a few issues and solutions I came across, in case they help anyone
else...

First off, back up your profile before updating - usually a good idea
anyway, just in case the new version messes something up in the profile
such that it won't even work in the old version.


1. Crash on Startup - due to missing xulstore.json
2. UI Customisations Lost - does anyone know a solution?
3. Saves Passwords Lost - fix found


1. Crash on Startup - due to missing xulstore.json




I didn't have this problem (xulstore.json didn't vanish), but it may be
relevant to your next issue:


It didn't vanish. It just wasn't present in my old profile from 
SeaMonkey 2.26.1, and its absence caused a crash in SeaMonkey 2.33. From:

  http://kb.mozillazine.org/Localstore.rdf
it looks like xulstore.json replaces localstore.rdf as of "Mozilla 34" 
(SeaMonkey 2.31?), so not expected to exist in 2.26.1. SM 2.33 was 
crashing rather than converting the existing localstore.rdf or creating 
a default version. Perhaps updating to SeaMonkey 2.31 first would have 
converted localstore.rdf, and avoided the problem.



2. UI Customisations Lost - does anyone know a solution?

...


Have you tried restoring xulstore.json from backup?


I restored my entire profile from a backup created immediately before 
updating, but there was no xulstore.json in that profile.



3. Saves passwords lost - fix found

...


Sorry, can't help with this.


No problem - the solution I linked to worked for me. I just mentioned it 
in case it helps others.


Thanks,
Mark.

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


Re: Vertical Thread Lines Missing in 2.33

2015-03-16 Thread NFN Smith

Gordon Weast wrote:

Losing the lines is an annoyance, not a fatal error.  Yes, it is
possible to get the same information, just not in the simple manner that
the lines gave us.



That's exactly what I'm seeing.  If this particular issue is generalized 
to Seamonkey 2.33, rather than my particular installation, then I'm 
ready to consider it one of those things that occasionally turn up in 
releases, and hope that it goes away in the next release.  In the 
meantime, I can certainly live with this one -- annoyance, perhaps, but 
nothing that I'm going to take any serious effort with hacking at my 
configs to try to change.


If it's still in 2.34, and nobody has already filed a bug report with 
bugzilla, I might do that myself, but I'm not going worry about it until 
then.


Given apparent structural issues that caused a late release of 2.33, and 
indications that 2.34 could be late, as well, I'm quite willing to give 
the developers a lot of slack on this one, and consider this to be a 
low-priority fix.


Smith

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


Re: Seamonkey update Crash

2015-03-16 Thread Eric

Daniel wrote:

On 16/03/15 04:42, Eric wrote:

Daniel wrote:

On 15/03/15 07:25, Eric wrote:

Daniel wrote:

On 14/03/15 11:26, Eric wrote:

Has anyone else been experiencing Seamonkey Crashing after updating?

I've had to revert the other computer that I use for business
purposes
to an older release of Seamonkey.  The other OS is Windows 7 Home
Premium 64 bit.

Here is what I've done to try and fix the crash problem.

On update, I'll do a warm boot of the system.  Crash.

Download and instal latest release of Seamonkey. Crash

warm boot.  Crash.

Revert to an older version 2.3.1. Crash.

warm boot.  Works.

I'm at my wits end with the crashes on the windows 7 machine.

This doesn't happen on my Vista Machine that I'm currently writing
this on.

Any ideas?

TIA

Eric


Eric, after you've had a crash, and you get an old version of SM
running, can you enter "about:crashes" (without the quotes) in the
address line and report back what is shown??


What would you like to see from it, pretty extensive file.  The only
thing that I saw that was interesting was about Last Pass, but nothing
specific about Last Pass.

Several tabs come up available that have a lot of different info.

Let me know what you want to see and I will do my best to provide it.

Eric


Eric, the stuff from about:crashes is gobbledegook to me but it may mean
something to others here-abouts, so post the last few lines (top) of it
here and, hopefully, someone here will know what to do with it.

Additionally, I notice you mentioned "Last Pass" as being problematic in
one of your other posts. Go to Tools->Add-on Manager and disable Last
Pass and then completely close and re-start SeaMonkey and see if it
behaves better.


Okay, so it was the "Last Pass" add-on from the "Seamonkey Extensions"
site.  I did what was suggested, and Seamonkey worked again.  I then
removed the "Last Pass" extension and re-installed from "Seamonkey
Extensions" same thing happened.  Again, I removed the extension, then
downloaded the extension from "LastPass.com" and everything is now
working as it should.

Not sure, but if at all possible, I will be leaving a comment on the
"last pass" extension within "Seamonkey Extensions" about the crashing
issue.

Thanks everyone for your help.

Eric


I seem to recall you saying it worked well first time around, Eric, so
when you downloaded and installed Last Pass for the very first time, did
you get it from lastpass.com or from SeaMonkey Extensions??

For my first use of Last Pass in Seamonkey, I got it from Seamonkey 
Extensions.  Now, after updating, I had to get it from lastpass.com.


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


Re: Vertical Thread Lines Missing in 2.33

2015-03-16 Thread Gordon Weast

Daniel wrote:

On 14/03/15 00:55, Gordon Weast wrote:

Ed Mullen wrote:

Geoff Welsh wrote on 3/12/2015 11:10 PM:

WaltS48 wrote:

Evan Davidson wrote:

In the mailnews display of threaded messages, there were vertical
line
connections showing the relationship (and amount of indenting)
between
message comments. In 2.33, I no longer see them. (The amount of
indenting is OK.) Is this a bug?



Most likely. I don't see them either.


I wonder, that might be related to the Folder Tree lines being
messed-up
or missing (in the Folder Pane) and there IS a bug on that but
IDR/IDK the #

GW


Not seeing the problem on 2.33.

However, I have this in my userContent.css file since ancient days:

/* set message window quote style */
blockquote[type=cite] {
color: navy !important;
border-color: black !important;
}

blockquote[type=cite] blockquote {
color: maroon !important;
border-color: navy !important;
}

blockquote[type=cite] blockquote blockquote {
color: green ! important;
border-color: maroon !important;
}

blockquote[type=cite] blockquote blockquote blockquote {
color: purple !important;
border-color: green !important;
}

blockquote[type=cite] blockquote blockquote blockquote blockquote {
color: teal !important;
border-color: purple !important;
}

blockquote[type=cite] blockquote blockquote blockquote blockquote
blockquote {
color: gray !important;
border-color: teal !important;
}

blockquote[type=cite] blockquote blockquote blockquote blockquote
blockquote blockquote {
color: navy !important;
border-color: black !important;
}

blockquote[type=cite] blockquote blockquote blockquote blockquote
blockquote blockquote blockquote {
color: maroon !important;
border-color: navy !important;
}

and I do have the vertical colored bars on threads.



Ed,

This all looks like it refers to the quote bars running down the left
margin when you're looking at a single message.

We aren't seeing the threading connections when looking at the message
title listing in the upper pane.  That's missing now in 2.33.  It makes
figuring out which message is a precursor to a given message harder to
figure out.

Gordon Weast


Gordon, what are your settings under View->Sort By?? I have mine set to
Order Received, Threaded and Ascending and have little problem in
working out which message is the precursor to the current message.

In addition, in the Headers section of an e-mail/News post, do you see
the References: line?? Clicking there should take you back to the
previous post.


Daniel,

Losing the lines is an annoyance, not a fatal error.  Yes, it is 
possible to get the same information, just not in the simple manner that 
the lines gave us.


I think we're just reacting to any accumulation of annoyances.

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


Problem with both 1-Click and Flash Got downloader in Seamonkey 2.33

2015-03-16 Thread Chuck

This seems to happen on You-Tube only but, I am not sure about that
The file opens in Download Manager but never starts.
I tried another site and It downloaded fine.
I uninstalled 2.33 and reinstalled 2.32.1 and everything works fine
Any suggestions?
Chuck
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Enigmail and SeaMonkey 2.33

2015-03-16 Thread W3BNR
On 3/15/2015 10:49 PM, NoOp wrote:
> I found that upgrading to SeaMonkey 2.33 (linux and Windows) with the
> Enigmail extension causes mailnews accounts to show as "Invalid
> Account". So I checked around and found a few bugs related. Asked on the
> Enigmail mail list & this is the result:
> 
> 
> Subject: [Enigmail] SeaMonkey 2.33 & Enigmail 1.7.2
>> With both the linux and Windows versions of SeaMonkey Enigmail causes
>> the mailnews accounts to show invalid. I notice these bug reports:
>>
>> http://sourceforge.net/p/enigmail/bugs/372/
>> (#372 Enigmail breaks Account Settings in Thunderbird Aurora)
>>
>> http://sourceforge.net/p/enigmail/bugs/429/
>> (#429 Mail Account Settings in SeaMonkey 2.33 broken by Enigmail)
>>
>> 372 states "Fixed in version: --- --> 1.8.0"
>> Unfortunately 1.8.0 isn't release yet, and is not an option from the
>> Download page.
>>
>> 429 shows that the bug report is invalid and states "This was fixed
>> several months ago. Please use the latest nightly build form
>> https://www.enigmail.net/download/nightly.php";
>> The nightly 1.8.a1pre does resolve that issue in SeaMonkey.
>>
>> 1.7.2 seems to work with Thunderbird 31.5.0 but does not work with
>> SeaMonkey 2.33. Why is 429 closed as invalid?
>>
>> So now every SeaMonkey 2.33 Enigmail user is now expected to run
>> Enigmail nightlys in order to not have Enigmail destroy the ability to
>> edit SeaMonkey mailnews accounts?
> 
> Response:
> 
>> On 15.03.15 00:55, NoOp wrote:
>>
 So now every SeaMonkey 2.33 Enigmail user is now expected to run 
 Enigmail nightlys in order to not have Enigmail destroy the ability
 to edit SeaMonkey mailnews accounts?
>>
>> 1. The current nightly is nearly - if not completeley - identical with
>>the release version 1.8. Expect the release of 1.8 within days.
>>
>> 2. Seamonkey 2.33 is now 4 days old. So "now" will be very short.
>>
>> 3. Seamonkey users are small in number compared with total users.
>>AMO says, Seamonkey 2.33 are about 400 "average daily users".
>>Total is about 150'000.
>> (https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/statistics/
>> usage/applications/?last=30)
>>
>> Given our limited resources it is not possible to publish an
>> intermediate version for such a small number of users for such a small
>> period of time.
>>
>> Ludwig
> 
> So there you go. If you use enigmail you will need to use the 1.8
> nightlies until 1.8 is officially realeased.
> 
> Seems that the:
> 
> "Enigmail is a security extension to Mozilla Thunderbird and Seamonkey.
> It enables you to write and receive email messages signed and/or
> encrypted with the OpenPGP standard."
> Should probably be changed to "Enigmail is a security extension to
> Mozilla Thunderbird & if resources are available maybe SeaMonkey"...
> 
> Is there a viable alternative to Enigmail for SeaMonkey (Windows and Linux)?
> 

I've been running enigmail 1.8a1pre (20150108-0013) since SM 2.32.
No problems.

-- 
Ed, W3BNR
HTTP://JonesFarm.us/W3BNR
Tags by Pick-a-Tag 1.60ß1

"So once you do know what the question actually is,
 you'll know what the answer means."-Douglas Adams (1952-2001)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Seamonkey update Crash

2015-03-16 Thread Daniel

On 16/03/15 04:42, Eric wrote:

Daniel wrote:

On 15/03/15 07:25, Eric wrote:

Daniel wrote:

On 14/03/15 11:26, Eric wrote:

Has anyone else been experiencing Seamonkey Crashing after updating?

I've had to revert the other computer that I use for business purposes
to an older release of Seamonkey.  The other OS is Windows 7 Home
Premium 64 bit.

Here is what I've done to try and fix the crash problem.

On update, I'll do a warm boot of the system.  Crash.

Download and instal latest release of Seamonkey. Crash

warm boot.  Crash.

Revert to an older version 2.3.1. Crash.

warm boot.  Works.

I'm at my wits end with the crashes on the windows 7 machine.

This doesn't happen on my Vista Machine that I'm currently writing
this on.

Any ideas?

TIA

Eric


Eric, after you've had a crash, and you get an old version of SM
running, can you enter "about:crashes" (without the quotes) in the
address line and report back what is shown??


What would you like to see from it, pretty extensive file.  The only
thing that I saw that was interesting was about Last Pass, but nothing
specific about Last Pass.

Several tabs come up available that have a lot of different info.

Let me know what you want to see and I will do my best to provide it.

Eric


Eric, the stuff from about:crashes is gobbledegook to me but it may mean
something to others here-abouts, so post the last few lines (top) of it
here and, hopefully, someone here will know what to do with it.

Additionally, I notice you mentioned "Last Pass" as being problematic in
one of your other posts. Go to Tools->Add-on Manager and disable Last
Pass and then completely close and re-start SeaMonkey and see if it
behaves better.


Okay, so it was the "Last Pass" add-on from the "Seamonkey Extensions"
site.  I did what was suggested, and Seamonkey worked again.  I then
removed the "Last Pass" extension and re-installed from "Seamonkey
Extensions" same thing happened.  Again, I removed the extension, then
downloaded the extension from "LastPass.com" and everything is now
working as it should.

Not sure, but if at all possible, I will be leaving a comment on the
"last pass" extension within "Seamonkey Extensions" about the crashing
issue.

Thanks everyone for your help.

Eric


I seem to recall you saying it worked well first time around, Eric, so 
when you downloaded and installed Last Pass for the very first time, did 
you get it from lastpass.com or from SeaMonkey Extensions??


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 
SeaMonkey/2.32 Build identifier: 20141218225909

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 
SeaMonkey/2.33 Build identifier: 20150215202114

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


Re: Printing out a Letter - Control of what is printed ?

2015-03-16 Thread Daniel

On 16/03/15 09:35, mozilla-lists.mbou...@spamgourmet.com wrote:

Daniel wrote:

On 14/03/15 07:53, mozilla-lists.mbou...@spamgourmet.com wrote:

DoctorBill wrote:

Whenever I print out an e-mail, all of the "heading" (?) stuff gets
printed also.
user-agent, MIME stuff, X-Mozilla-Status etc.


It sounds like you've got SeaMonkey set to display all headers.


Is there some way that I can just print out the e-mail w/o all that
"Stuff" at the top ?

i.e. - Subject, From, Date,  then the text...?


Before printing, go to View > Headers > Normal.

If you want all the headers displayed on screen, but not printed, I'm
not sure how to do that other than changing that option every time you
print. I keep it set to Normal, and on occasions when I want to check
other headers I just press Ctrl+U (shortcut for View > Message Source).

Mark.


What DB can do "on the fly" is click the little, downward pointing,
triangle next to Subject, turning the downwards pointing triangle into a
sideways pointing triangle:. This should reduce the Header area to just
one line, the Subject: line.


That doesn't affect what's printed though. If View > Headers is set to
All, it still prints all the headers.

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com


O.K., you're right, so I guess you'll just have to remember to switch 
View->Headers to normal.


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 
SeaMonkey/2.32 Build identifier: 20141218225909

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 
SeaMonkey/2.33 Build identifier: 20150215202114

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