Daniel wrote:
You're stretching the old grey matter, Jonathan, but I think, as I only
start Mail & News and Chatzilla (not the Browser) when I click on the SM
icon, when I do a new install, and I then click on the icon, I then have
to set-up my Mail & News accounts ... or point SM to my profile
On 15/10/2017 1:34 AM, Jonathan N. Little wrote:
Daniel wrote:
On 13/10/2017 1:19 PM, Jonathan N. Little wrote:
Rob Steinmetz wrote:
Jonathan N. Little wrote:
Oh okay you're Windows drive mapping to the SAMBA share. Next
questions:
Is the SeaMonkey profile a subdirectory under
Daniel wrote:
On 13/10/2017 1:19 PM, Jonathan N. Little wrote:
Rob Steinmetz wrote:
Jonathan N. Little wrote:
Oh okay you're Windows drive mapping to the SAMBA share. Next
questions:
Is the SeaMonkey profile a subdirectory under ~/.seamonkey or that
directory itself? Because profiles are
On 13/10/2017 1:19 PM, Jonathan N. Little wrote:
Rob Steinmetz wrote:
Jonathan N. Little wrote:
Oh okay you're Windows drive mapping to the SAMBA share. Next questions:
Is the SeaMonkey profile a subdirectory under ~/.seamonkey or that
directory itself? Because profiles are usually a
Rob Steinmetz wrote:
Jonathan N. Little wrote:
Rob Steinmetz wrote:
Jonathan N. Little wrote:
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]
WaltS48 wrote:
On 10/12/17 5:01 PM, Jonathan N. Little wrote:
WaltS48 wrote:
On 10/12/17 2:59 PM, Rob Steinmetz wrote:
Jonathan N. Little wrote:
Rob Steinmetz wrote:
That appears to show that rob is using Profile1(with no name)from drive
U: and launching SeaMonkey using the .seamonkey
On 10/12/2017 1:05 PM, Rob Steinmetz wrote:
> Solved!
>
> Somehow the prefs.js file was overwritten with a default file that wiped
> out all previous settings and made the new instance appear to be a fresh
> profile.
>
> I was able to copy the prefs.js from a backup and the profiles started
>
Jonathan N. Little wrote:
Rob Steinmetz wrote:
Jonathan N. Little wrote:
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
On 10/12/17 5:01 PM, Jonathan N. Little wrote:
WaltS48 wrote:
On 10/12/17 2:59 PM, Rob Steinmetz wrote:
Jonathan N. Little wrote:
Rob Steinmetz wrote:
That appears to show that rob is using Profile1(with no name)from drive
U: and launching SeaMonkey using the .seamonkey command.
No
WaltS48 wrote:
On 10/12/17 2:59 PM, Rob Steinmetz wrote:
Jonathan N. Little wrote:
Rob Steinmetz wrote:
That appears to show that rob is using Profile1(with no name)from drive
U: and launching SeaMonkey using the .seamonkey command.
No .seamonkey is not the command but a Linux hidden
Rob Steinmetz wrote:
Solved!
Somehow the prefs.js file was overwritten with a default file that wiped
out all previous settings and made the new instance appear to be a fresh
profile.
I was able to copy the prefs.js from a backup and the profiles started
working.
I'm mystified as to how the
Rob Steinmetz wrote:
Jonathan N. Little wrote:
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
Solved!
Somehow the prefs.js file was overwritten with a default file that wiped
out all previous settings and made the new instance appear to be a fresh
profile.
I was able to copy the prefs.js from a backup and the profiles started
working.
I'm mystified as to how the prefs.js files
WaltS48 wrote:
On 10/12/17 2:59 PM, Rob Steinmetz wrote:
Jonathan N. Little wrote:
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
On 10/12/17 2:59 PM, Rob Steinmetz wrote:
Jonathan N. Little wrote:
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
Jonathan N. Little wrote:
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.
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
Mason83 wrote:
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
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
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
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
21 matches
Mail list logo
