Closed
Bug 691155
Opened 13 years ago
Closed 13 years ago
New profile incorrectly uses Roaming for Local data location
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 640989
People
(Reporter: stanio, Unassigned)
Details
(Whiteboard: [DUPEME])
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a1) Gecko/20111002 Firefox/10.0a1 SeaMonkey/2.7a1 Appears to happen starting with SM 2.0. SM 1.1 appears fine: 1. Start with -ProfileManager option; 2. Create new profile and start with it; 3. Open Edit -> Preferences: Advanced / Cache and observe the "Cache Folder Location"; 4. Exit and start again using the same profile; 5. Open Edit -> Preferences: Advanced / Cache and observe the "Cache Folder Location". Actual: On step 3 the location shown (and actually used) is: C:\Users\<username>\AppData\Roaming\Mozilla\SeaMonkey\Profiles\<salt>.<profile_name> On step 5 the location shown (and used) is: C:\Users\<username>\AppData\Local\Mozilla\SeaMonkey\Profiles\<salt>.<profile_name> Expected: Observing location on steps 3 and 5 should show the same location used: C:\Users\<username>\AppData\Local\Mozilla\SeaMonkey\Profiles\<salt>.<profile_name> ----- There are few more things which gets initially saved to the Roaming location on the first profile start and subsequently saved to the Local location like: OfflineCache startupCache
Comment 1•13 years ago
|
||
this is shared code in toolkit. moving.
Component: Startup & Profiles → Startup and Profile System
Product: SeaMonkey → Toolkit
QA Contact: profile-manager → startup
Version: Trunk → 10 Branch
Reporter | ||
Comment 2•13 years ago
|
||
Yep, I've just tried I get the same behavior with Firefox.
Comment 4•13 years ago
|
||
(In reply to Philip Chee from comment #1) > this is shared code in toolkit. moving. Fairly certain this bug is a duplicate of a wontfix bug.
Reporter | ||
Comment 5•13 years ago
|
||
O.k. Found it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•