60856 - Preferences do not save

Status: VERIFIED WONTFIX

(SeaMonkey :: Preferences, defect, P3)

Description

[Devin Weaver]

I sure hope this isn't a duplicate but a quick query on "save preferances"
returned nothing.

Using Nightly Build ID: 2000111506
Mozilla/5.0 (X11; U; Linux 2.2.16 i686; en-US; m18) Gecko/20001115

Reproducable: Open Edit Preferences, make change, hit "OK" button. Nothing will
appear to happen. Must exit via "Cancle" button or Window Close command.

The error message it produces on the console:
JavaScript error:
 line 0: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPref.SavePrefFile]"  nsresult: "0x8000ffff
(NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://communicator/content/pref/nsPrefWindow.js :: anonymous :: line 248"
data: no]

Comment 1

[André Dahlqvist]

I think this is a dupe of #40617, but that bug has been marked VERIFIED FIXED
on 2000-11-13. Could also be related to #30801 I guess.

Devin, could you try the latest Linux build and see if you can reproduce it?
Also try to find out exactly what change in the Preferences dialog makes the OK
button not work.

Comment 2

[Devin Weaver]

I just downloaded the latest linux build (ID: 2000111506) about 20 Min. ago.

In fact you don't have to make a change at all. I appears to me that any attemt
to use the "OK" button causes this error including not making a single change.

Let me know if you need more. I'll rm -rf package/* and re-untar the latest nightly.

Comment 3

[Devin Weaver]

Ok I feel stupid now. I wasn't using the very latest. But now I am.

I just verified that the same error bug accures in build ID: 2000112021

Should I remove my ~/.mozilla directory and try?

Comment 4

[André Dahlqvist]

Yes, please try with a fresh ~/.mozilla directory and see if you can reproduce
it. I used to see this before, but I can't reproduce it on 2000111721. I will
try a more recent Linux build soon.

Comment 5

[Devin Weaver]

I found it!

After I rm -rf ~/.mozilla and started her up again. I got the must convert
profile from version 4. I when the usual way and took all the defaults (hit the
convert button) and then tried preferences. same deal. I then thought maybe the
merge is messing with things. So I mv ~/.netscape ~/_netscaperc_ and did the
above only this time it didn't ask for a conversion and when strat to the
browser after creating a default user. This made the save preferences bug
dissapear. I then mv _netscaperc_ back to normal and now all is happy again

Looks like the merge/convert proccess can hose things up. Hope this helps. ;-)

Comment 6

[Kathleen :Brade]

with my debug mozilla build from today (11/21), I can't reproduce this problem
on Linux.

Comment 7

[André Dahlqvist]

I'm pretty sure that what Devin saw was a dupe of #40617. I can still
reproduce that bug on 2000112108 on Linux. This bug should probably be marked a
duplicate of that bug, because that's the only way to trigger this behaviour
that I know of.

Comment 8

[Devin Weaver]

I've verified that this bug is unreproducable in a sane user enviroment. I
currently have some custom preferences in my netscape 4.75 setup which seem to
be the culporate. At some point I'll weed out my preferences and try to pinpoint
the setting that trips this. (ie. mutt mailer plugin)

If I move my .netscape directory out of the way temporarily as I run mozilla for
the first time it avoids converting my old netscape profile and builds a fresh one.

I don't feel this is a dupe of #40617 since The symtoms are produced without
following the same steps and dissapear after my workaround above.

This bug probubly should be marked for WONTFIX. It might be nice to note in a
NS6 IFAQ (InFrequntly-Ask-Questions) someday. I'll update this bug if I ever
fully nail the preference setting and/or plugin that causes the bug. I
appologize for any inconvinence from this report. Cheers.

Comment 9

[Daniel Veditz [:dveditz]]

Sounds like a js error in the Preferences front end, reassigning.

Comment 10

[Keyser Sose]

So shall I go ahead and mark this WONTFIX as per comments?

Comment 11

[Mark Olson]

Marking WONTFIX at reporter's request.  Reporter, if you do eventually find the
root cause please REOPEN and add the relevant data.  Thanks.

Comment 12

[sairuh (rarely reading bugmail)]

v