Chris Howells wrote:
>
> I was able to do all up to here...
>
> > touch chrome/user-{skins,locales}.rdf
>
> But I didn't really understand this bit I'm afraid. The only rdf files
> under chrome/ are:
>
> chris@venus: chrome$ ls *.rdf
> all-locales.rdf all-packages.rdf all-skins.rdf user-locales.rdf
> chris@venus: chrome$
>
> Are they the ones you mean? If so, I've touched them.
>
> Sadly this doesn't seem to work -- I still get the segfault when running
> as a normal user.
"touch" is just a convenient command that can be used in unix to create
an empty file. You could create them in a text editor or any other way
if you prefer (although make sure they're owned by root and not
writeable by the user who will be running mozilla). I should have
clarified that I was speaking in literal shell commands, and also that
that specific line of instruction was bash-specific (there may be other
shells that also support the syntax, but I know it isn't true of all
shells - the original sh for example). A portable version of the command
would be:
touch chrome/user-skins.rdf chrome/user-locales.rdf
Unless I'm misremembering, when you untar a clean tarball, there
shouldn't be *any* user-*.rdf files in the chrome directory. By running
"touch", you create these files.
>From my (limited) understanding, running my sequence of commands
(regxpcom, regchrome, and creating those two files) is more or less
equivalent to the important parts of what mozilla does when run as root.
Since you don't seem to have a user-skins.rdf file, it could be that
something's changed recently that makes mozilla not create this file,
even when run as root.
The first thing I'd try is creating an (empty) user-skins.rdf in your
existing mozilla/chrome directory and see whether that solves your
problem. If not, try again from scratch with an empty /usr/local/mozilla
and do *only* the sequence of steps I suggested (in particular, don't
run mozilla as root ever). If you are using bash, type the "touch" line
from my original email literally; if not, substitute the touch line
above (which will work under bash too but it's longer to type :) )
If none of that works, then I'm afraid I don't know what could have
broken. Hope you get more luck on n.p.m.unix :)
Stuart.
