Open Bug 1422702 Opened 7 years ago Updated 7 years ago

Profile Location

Categories

(SeaMonkey :: Startup & Profiles, defect)

SeaMonkey 2.49 Branch
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: dx316mm068, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
Build ID: 20171016030418

Steps to reproduce:

I attempted to create a new Profile for SeaMonkey 2.49.1 at a specific location of my choice.

I clicked Tools->Switch Profiles->Manage Profiles->Create Profile and, on the second screen, I named the Profile "Dec_2017" and then clicked on "Choose Folder" and pointed to a location at E:\Internet_Programs\SeaMonkey\Profile and O.K. my way out.


Actual results:

Up screen, the "Create Profile Wizard" still indicated that my new profile "user settings, preferences and other user-related data" would be stored at C:\Users\Daniel\AppData\Roaming\Mozilla\SeaMonkey\Profiles\(gobble-de-gook.Default User and not the specific location I had pointed to.

I tried several other locations with the same result.

By-the-by, Windows Explorer still indicates that I have approx 17BG Free on E:\


Expected results:

I would expect the "user settings, preferences and other user-related data" location should change to the location that I pointed at.

Note: when I enquired in the "Where to store my profile" thread on the mozilla.support.seamonkey newsgroup on the news.mozilla.org news server, several others reported similar problems whilst several others reported no problems creating new profile locations, so it would seem this problem might be intermittent.

Related bugs might include 470927 (resolved Wontfix) and 1416013 (New Unassigned)
I see the behavious in Bug 470927. I select a folder and the sreen shows only the folder. When I then edit the Name it will be appended to the new location.

2.53 x64 local build under Windows 7.

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53
You need to log in before you can comment on or make changes to this bug.