[21025] in Athena Bugs
Re: Mozilla bugs continues
daemon@ATHENA.MIT.EDU (t. belton)
Tue Nov 5 14:19:30 2002
Date: Tue, 5 Nov 2002 14:19:28 -0500 (EST)
From: "t. belton" <tbelton@MIT.EDU>
To: Kev <klmitch@MIT.EDU>
cc: <bugs@MIT.EDU>
In-Reply-To: <200211051843.NAA04168@quantum-2.mit.edu>
Message-ID: <Pine.GSO.4.33L.0211051416310.14658-100000@iphigenia.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 5 Nov 2002, Kev wrote:
> OK, so I finally fiddled around with Mozilla some more. This time, after
> waiting a judicious period of time and verifying that the directory was
> populated, I used an X server kill to kill the window telling me that the
> profile conversion was in progress. Much to my surprise, Mozilla popped
> up shortly after.
>
> I then pulled up the preferences dialog to do some customization and
> discovered that it refused to accept any key press events. It
> understands mouse clicks just fine and deals with them properly, but
> if I click in a text field, such as the home page field, no text
> cursor appears and no text is entered if typed. If I highlight some
> text and type, again, nothing happens--the text I highlighted should
> be replaced with what I type, which is what Mozilla on my (non-Athena)
> home machine does.
This refusal to accept input sounds like a possible symptom of a mangled
profile, which is what you'd likely get from interrupting the conversion.
So I'm not surprised.
> Why do I have so many problems with Mozilla on Athena? It certainly has
> never given me this much trouble on my RedHat box at home! (Well, other
> than a few strange crashes, but...)
Well, one problem that we have had consistently with Mozilla AND Netscape
is that they seem to be built with a basic assumption that they are
installing in a single-user environment, which on Unix is a little
ridiculous, but never mind that. We always have to do at least a little
finagling to be able to run any of them in a locker, with preferences
stored somewhere local but everything else global - and that alone can
explain many of the differences between the way Mozilla runs for Athena
and the way it runs on your home box.
I still don't know what to tell you to do about the problem, but I'm still
looking.
