Re: SeaMonkey not recognizing existing profiles

[Mason83]

On 12/10/2017 01:48, David E. Ross wrote:
> On 10/11/2017 2:24 PM, Rob Steinmetz wrote:
>> I have a server that had a problem with a share. I think I have fixed 
>> that but my users cannot access their existing SeaMonkey Profiles. They 
>> are located on a a SAMBA [homes] share on an Ubuntu 16.04 LTS server in 
>> a directory called ~/.seamonkey.
>>
>> In the past I have been able to conned to theses existing profiles by 
>> logging into the Profile Manager and simply pointing to the existing 
>> SeaMonkey profile.
>>
>> However when I do this on on this server now I get a SeaMonkey opening 
>> page and SeaMonkey does not recognize the existing email configuration.
>>
> 
> Locate the file named profiles.ini.  Each user needs to have a copy of
> this file locally.  For Windows 7, it is always in
> [C:\Users\xxx\AppData\Roaming\Mozilla\SeaMonkey], where "xxx" is the
> user name of the Windows account.  SeaMonkey looks for this file LOCALLY
> to determine what profiles exist and where the profiles are located.

David,

Ubuntu is a Linux distribution, i.e. not Windows.

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

Re: SeaMonkey not recognizing existing profiles

[David E. Ross]

On 10/11/2017 2:24 PM, Rob Steinmetz wrote:
> I have a server that had a problem with a share. I think I have fixed 
> that but my users cannot access their existing SeaMonkey Profiles. They 
> are located on a a SAMBA [homes] share on an Ubuntu 16.04 LTS server in 
> a directory called ~/.seamonkey.
> 
> In the past I have been able to conned to theses existing profiles by 
> logging into the Profile Manager and simply pointing to the existing 
> SeaMonkey profile.
> 
> However when I do this on on this server now I get a SeaMonkey opening 
> page and SeaMonkey does not recognize the existing email configuration.
> 

Locate the file named profiles.ini.  Each user needs to have a copy of
this file locally.  For Windows 7, it is always in
[C:\Users\xxx\AppData\Roaming\Mozilla\SeaMonkey], where "xxx" is the
user name of the Windows account.  SeaMonkey looks for this file LOCALLY
to determine what profiles exist and where the profiles are located.

The profile folders can be on a shared network file system.  However,
note the following:

*  Two or more users cannot use the same profile at the same time.  If
more than one user attempts to use the same profile simultaneously, the
profile is most likely to become corrupted.

*  For each user, there must be a local drive letter for the location of
the profiles.

For each user, open the profiles.ini file in a plain-text editor (e.g.,
Notepad, Wordpad, but definitely NOT Word).   There will be a list of
profiles identified as Profile0, Profile1, etc.  For each profile,
"Name" is the name a user sees in the Profile Manager.  With the
profiles on a shared network file system, IsRelative must be 0.  Path is
then the complete path -- using the local drive letter -- to the profile
folder, ending with the name of the folder.  The path is given in the
Windows format (e.g., G:\Mozilla profiles\SeaMonkey\guest).  Note that \
is used, not /, and that there are no quotation marks despite the
presence of spaces in the names of the path's folders.

Is this confusing?  I think so.  I would strongly recommend that users
should each have their own local profiles.  If this is an enterprise
system, you then need tools to synchronize certain parts of those
profiles; to avoid corrupting profiles, such tools would be used only
when each user's instance of SeaMonkey has been terminated.

-- 
David E. Ross


By allowing employers to eliminate coverage for birth control
from their insurance plans, President Trump has guaranteed there
will be an increase in the demand for abortions.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

SeaMonkey not recognizing existing profiles

[Rob Steinmetz]

I have a server that had a problem with a share. I think I have fixed 
that but my users cannot access their existing SeaMonkey Profiles. They 
are located on a a SAMBA [homes] share on an Ubuntu 16.04 LTS server in 
a directory called ~/.seamonkey.


In the past I have been able to conned to theses existing profiles by 
logging into the Profile Manager and simply pointing to the existing 
SeaMonkey profile.


However when I do this on on this server now I get a SeaMonkey opening 
page and SeaMonkey does not recognize the existing email configuration.

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

Re: router login - error 401, unauthorized

[Daniel]

On 11/10/2017 6:12 PM, Frank-Rainer Grahl wrote:

So using .1 does not distinguish the official build from
Adrian's ESR-based builds.


1 will be release channel and 2 it will distingush it from his 2.49
(without the .1)

FRG


Frank-Rainer, over this recent period where the SeaMonkey-Project has 
had troubles getting their Official SeaMonkey releases out, it seems to 
me that Adrian has been releasing his own versions, from his server or 
wherever, with the same User Agent as the Official version.


Perhaps it would be better if Adrian were to alter his User Agent 
string, as Hartmut Figge does with his personally built versions by 
adding, in Hartmut's case, an "-h" to the end, e.g. SeaMonkey/2.43a1-h.


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 
SeaMonkey/2.48 Build identifier: 20170329183526


Go Dallas Cowgirls!!  Err!! ... Um!! .. I mean *Go Dallas Cowboys* !!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

[Frank-Rainer Grahl]

> So using .1 does not distinguish the official build from
> Adrian's ESR-based builds.
>
1 will be release channel and 2 it will distingush it from his 2.49 
(without the .1)


FRG

Mason83 wrote:

On 10/10/2017 08:38, Frank-Rainer Grahl wrote:


You can update Adrians build to the official candidate 3:

https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/

Should behave way better than the May build I hope :)

.1 because Adrian built 2.49 from the comm-release branch and we wanted
to distinguish it from this one. All 2.49.1 ones are build from the
esr52 branch.


I'm confused. Adrian's build shows up as
SeaMonkey version 2.49.1
You are currently on the esr update channel.
User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1

So using .1 does not distinguish the official build from
Adrian's ESR-based builds.


2.49.1 is at current esr52.4 level. The next release will
be .2 Hopefully when 52.5 arrives but depends on how long it takes to
bake a release and how much time ewong has. In any case there will be a
.2 at a future 52.x esr level.


Thanks for that info.

Regards.



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

Re: "Re: Future releases"

[Frank-Rainer Grahl]

There will still be 2.49.x ESR releases. Plan is/was to do a 2.56 ESR 
later but with so much broken and the infrastucture failing it will be 
some time.


FRG

Ant wrote:

https://blog.seamonkey-project.org/2017/10/11/re-future-releases/


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