84758 - Can't remove search and print buttons

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect)

Description

[tenthumbs]

I don't have the foggiest idea where this belongs so I'm putting it in
browser-general, marking it unconfirmed, and hoping someone knows where
this belongs.

I downloaded a 06-08-06 Linux nightly and ran it. The first time it
worked fine. The second time it urped and said:

XML Error in file 'file:///home/10/.mozilla/mozProfile/localstore.rdf',
Line Number: 138, Col Number: 3, Description: unclosed tokenSource Line:
<RDF:Description about="chrome://naviga

Yes, that's precisely what it said. It blew away localstore.rdf, losing
lots of settings. I reset as much as I could, including *not* displaying
the search and print buttons. Mozilla ignores this. Even closing and
restarting mozilla does not make the buttons disappear.

Everything did work with an 06-05 build. No, there was no file
corruption. Today happened to be the day when the system checked the
file systems.

I use the classic skin.

Comment 1

[Asa Dotzler [:asa]]

->XPapps

Comment 2

[Boris Zbarsky [:bzbarsky]]

[e-mail], are you seeing this problem with a new profile?

Comment 3

[tenthumbs]

A new profile works but I consider that cheating. :-)

In my case, localstore.rdf became corrupt but you can see the same thing
with this simple test. Set your mozilla to hide the search and print
buttons. Close mozilla and hide localstore.rdf. Restart mozilla and the
buttons should appear. Open the preferences dialog and see that the
search and print radio buttons are _unchecked_. To fix this, you have to
check the two radio buttons, close the preferences dialog, reopen the
preferences dialog, and then uncheck the buttons. That's less than an
obvious solution.

State is stored in both prefs.js and localstore.rdf and it's easy to get
them out of sync. Shouldn't happen.

Comment 4

[Keyser Sose]

marking WORKSFORME. The profile settings are not stable yet so its not cheating.

Comment 5

[tenthumbs]

I think I'll let someone intelligent decide if this bug should be closed.

Reopening

Comment 6

[Alvaro Munoz-Aycuens]

Please reporter be more polite, if there is anyone that can decide such things
is keyser Sosez, try to make your point about the bug instead of tell things
that way.
And WFM on linux build: 2001072106

Comment 7

[Alvaro Munoz-Aycuens]

cc'ing self

Comment 8

[Daniel Brooks [:db48x]]

of course it's a bug, it should be confirmed and set to block some meta bug on
prefs versus persist=""

Comment 9

[Grey Hodge (jX)]

We just had another case of this with the same fix working, so this is certainly
an WFM. If anyone disagrees, try a new profile; Another potential fix is to
delete localstore.rdf. If it STILL persists AFTER that, THEN, and ONLY THEN
reopen. Name calling doesn't count.

Comment 10

[sairuh (rarely reading bugmail)]

mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)