RDF horkage when sharing profile between Netscape and Mozilla

RESOLVED WONTFIX

Status

()

Core
Preferences: Backend
RESOLVED WONTFIX
15 years ago
11 years ago

People

(Reporter: Claudius Gayle, Unassigned)

Tracking

(Blocks: 1 bug, {relnote})

Trunk
Future
relnote
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
This bug description isn't fully developed yet but I needed to get it into the
system so I can get a bug# and release note it.

On 3 separate occasions (bug#'s forthcoming) I have seen profile sharing be the
root cause of some problem that boils down to the rdf datasource having been
damaged. The most notable of these is the 'B.U.S.' (Bookmarks of Unbelieveable
Size) bug.
(Reporter)

Comment 1

15 years ago
bug 127856 appears to be the worst consequence, comment 17 is the most informative.
bugscape bugs 11537 and 11547 seem to be a result of profile sharing as well.
The common thread is that all rely on an rdf datasource.

Comment 2

15 years ago
Um, yeah. Don't do that.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
(Reporter)

Comment 3

15 years ago
repeating the summary because I hate when it's not in the body of a bug:
"Sharing the same profile with NS +Moz seems to cause RDF horkage"
An action intrinsically supported by our Profile Manager which recognizes them
as twin equals.


If you point someone to a door with 'Enter' on it and the handle shocks them
when they touch it - maybe they shouldn't do that, but that still makes you a
pretty mean bastard.

that is to say...
If Netscape can't use a Mozilla profile(and vice-versa) without causing nasty
corruption then it shouldn't be trying. We should offer to import and create a
new one without harming the old one - just like we do with other browsers that
we like/share users with/ and support but with which we have incompatible
profiles. (uhh 4.x)

Believe me, I'm overjoyed to mark bugs that stem from this behavior as invalid
(and I will) but that doesn't strike at the core issue. Lots of users, QA, and
developers have spent a ton of time chasing down these demons - no one knew of
this incompatibility. Isn't there something to be done?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---

Comment 4

15 years ago
bug 139926 may be related.  it deals with sharing moz+moz (migration actually).

Comment 5

15 years ago
I believe http://bugzilla.mozilla.org/show_bug.cgi?id=76431 will cover this in
some respect.

Updated

15 years ago
Blocks: 123929

Comment 6

15 years ago
Bug 76431 covered multiple instances of Mozilla running concurrently. This bug
covers different instances of Mozilla and Netscape using the same profile
nonconcurrently. This bug is related to bug 131014 and bug 134517.

The 1.0 relnote for this bug is good but not enough. The solution should be that
Netscape creates its own registry.dat and doesn't touch Mozilla's. That should
be done for the next major Netscape release, or there will be a lot of users
with profile corruption caused by sharing profiles between Netscape and Mozilla.
That could lead to user frustration.
Keywords: nsbeta1, relnote
More closely related is bug 107694. See
http://bugzilla.mozilla.org/show_bug.cgi?id=107694#c6.

  What I was talking about when I made that comment was to fix bugs such as this
which cause the problem of using the same profile (non-concurrently) between
mozilla and NS. Then, we wouldn't *have* to have separate profiles between
products as bug 107694 calls for.

  Now, I think that it would be nice to *be able to* have separate profile dirs
for the sake of distributors. For that, see bug 58327. 

Updated

15 years ago
Status: REOPENED → ASSIGNED
Target Milestone: --- → Future

Updated

15 years ago
Summary: Sharing the same profile with NS +Moz seems to cause RDF horkage → RDF horkage when sharing profile between Netscape and Mozilla

Comment 8

15 years ago
The problem with running the same profile alternately in NS and Moz is that some
themes work only for some Moz versions and not in NS7. If Moz is set for such a
theme, display problems ensue.

Work-arounds:

1. Two Profiles, each named clearly enough to indicated which profile is used
with which browser.

2. Shortcuts that aim the browser at a particular profile, as "C:\Program
Files\mozilla.org\Mozilla\mozilla.exe" "-p" "MozProfileName" (a Windows XP example)

Obviously these are kludges.

A potential fix: since NS isn't moving, move Moz, from the "Mozilla" application
directory to a "Mozilla.org" or "Moz" directory.

Comment 9

15 years ago
Mozilla should prompt a user to create a seperate Mozilla profile if the
existing profile was made by Netscape.  Conversely, Netscape should prompt a
user to create a seperate Netscape profile if the existing profile was made by
Mozilla.  When I accidently share the Netscape profile with Mozilla it usually
becomes corrupt because features implemented in Mozilla are not yet in Netscape.
 Also the bookmarks erroneously double import and become disorganized.

Comment 10

15 years ago
I totally agree with comment 3. The software by default does the wrong thing,
without a warning, so you cannot blame the user, the software is broken.

There is a bug about Netscape using a different directory.

Updated

15 years ago
QA Contact: tever → nobody

Comment 11

14 years ago
adt: nsbeta1-
Keywords: nsbeta1 → nsbeta1-

Comment 12

14 years ago
->prefs backend.
Assignee: waterson → prefs
Status: ASSIGNED → NEW
Component: RDF → Preferences: Backend

Comment 13

12 years ago
What's a Netscape? :)

Ancient history, right?
Status: NEW → RESOLVED
Last Resolved: 15 years ago12 years ago
Resolution: --- → WONTFIX

Comment 14

12 years ago
Netscape is not ancient history to me.  I just installed Netscape 7.2 on a
system last week.  Netscape 8 Beta is about to be released
(http://browser.netscape.com/nsb/).  

It's annoying to have to switch profiles when running Netscape and Mozilla on
the same machine.  Please reopen this bug.

Comment 15

11 years ago
I withdraw my request to reopen this bug.  Netscape seems to no longer be using the Mozilla profile code. 
You need to log in before you can comment on or make changes to this bug.