For bugs that result from SeaMonkey build problems. ("Building" is the process of converting the thousands of Mozilla source code files into a actual executable software.) If a file in a newly-downloaded build is missing or corrupted, file the bug in this component.
Examples of appropriate bugs: Build date in browser window is incorrect; DLL files are missing from the ZIP file; or Build contains a zero K executable.

I've been seeing this ever since I've been using the tarballs (say, about a
week, week and a half.) What it boils down to is that Mozilla is unable to
create or manage or really even think about profiles in any way; having created
a single default profile in M18, though, I can start the nightlies up without
problems, and the changes I make are saved properly.

I see this problem with the 2001-01-25-11 mozilla build but I do not see it with
the 2001-01-25-09 mozilla-gcc295 build. The absence or presence of an existing
mozilla or netscape profile does not appear to make a difference.
And I don't see this with my current tip build which is also gcc 2.95.2.

The tree was red at the time that build was done (in a way that would cause that
error if the build was done as a depend build on top of the 6am build). Setting
back to WORKSFORME.
According to kysmith's email, respins for Linux and Win have started and he's
working on Mac.