Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Jonathan N. Little
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]

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Jonathan N. Little
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread David E. Ross
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 >

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Rob Steinmetz
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread WaltS48
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Jonathan N. Little
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Jonathan N. Little
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Jonathan N. Little
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Rob Steinmetz
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Rob Steinmetz
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread WaltS48
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Rob Steinmetz
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.

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Jonathan N. Little
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

Re: SeaMonkey not recognizing existing profiles

2017-10-12 Thread Rob Steinmetz
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