190077 - 1/3 of my screen is used by some "underwaterscreen" displaying code, how to remove?

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[donald]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.2.1) Gecko/20021130

It looks like since I installed the dutch languagepack some ünderwaterscreen is
displayed in the lower 1/3 f my screen. how do I get rid of it???

Reproducible: Always

Steps to Reproduce:
1.every time I start up it is there
2.
3.

Actual Results:  
???

Expected Results:  
display full screen standard mode(not F11 mode)

bug is there in both classic and modern theme

Comment 1

[Gilles Durys]

not a documentation bug, -> browser

Comment 2

[Ruslan Ismailov]

Could not you provide a screenshoot of this underwaterscreen?

Comment 3

[Ashley Bischoff (blog at handcoding.com)]

Reporter: Your build is really old. Could you try one of these newer builds?
http://ftp.mozilla.org/pub/mozilla/nightly/latest/

(as always, be sure to delete your old Mozilla directory before installing the
new one)

Comment 4

[R.K.Aa.]

*** This bug has been marked as a duplicate of 126138 ***

Comment 5

[R.K.Aa.]

reporter mailed a screenshot - in a .doc file.
This is a dup of bug 130331, which acclaimedly was fixed in 1.2.1
(see comment 171 there)

Reporter also writes:

"As you can see it is not the same problem, but I solved it after a tip of alex
bischoff to delete the old mozilla-map before installing a new version."

Comment 6

[R.K.Aa.]

Attachment: the mentioned "screenshot in a .doc"

attaching as binary file. Original filename was Underwaterscreen.doc

Comment 7

[R.K.Aa.]

Reporter: You write that you've seen the bug "since i installed the dutch
languagepack". But when did you install it? Did you install Mozilla 1.2.1, and
all was fine - and then you installed the language pack, and Mozilla broke?

Comment 8

[Ashley Bischoff (blog at handcoding.com)]

Marking as INVALID. Reporter e-mailed me to state that after reinstalling
Mozilla (but deleting the old directory first, this time), his setup is now fine.