On Wed, 14 Jun 2006, Justin Pryzby wrote:
> > # id
> > uid=0(root) gid=0(root) groups=0(root),1003(lpadmin)
> > # /bin/rm -rf .mozilla
> > # firefox
> >
> > Now I get three copies of the warnings, not just one. Hm.
> As root and the user both?
I see the same thing for both users if
a) the Extensions.rdf is missing and
b) the .mozilla directory is missing for the user I am running as.
If only a) is true, I see one message, in both cases.
> > Things I tried:
> >
> > # /bin/rm -rf .mozilla
> /root/.mozilla or /home/~vmi/.mozilla?
/root/.mozilla
> > # dpkg -L mozilla-firefox | grep -i extens |xargs ls -l
> > I could find no files or directories that were not owned by root
> > or were not writeable by root.
> Actually, permissions checks should be bypassed for the root user
> anyway. access() is a special case, and uses the ruid not the euid.
> This doesn't seem to be relevant here.
>
> > The only funny I noticed was that:
> > /etc/mozilla-firefox/profile/extensions/Extensions.rdf
> How did you notice that?
>From the output of the command string above; dpkg -L said the file
should be there but ls -l was unable to find it.
> > So the actual problem is that somehow this extensions file got deleted.
> > It would have been helpful for Firefox to report that, instead of the
> > gibberish it gave me. Hopefully later releases from upstream have attended
> > to this.
> Indeed; it probably does
>
> FILE *fp;
> if (NULL==(fp=fopen(fn, s)))
> error_msg()
>
> But since the error indicates that the file is missing, it is wrong;
> either the message should be generalized, or the check should confirm
> that errno==ENOENT before displaying that message, and use a different
> message otherwise.
I agree.
> > That leaves why the file was missing in the first place.
> > Perhaps that is something that the package postinst or postrm scripts
> > could do, on a bad day? Or an incomplete purge after an
> > apt-get remove mozilla-firefox?
> This might be the case, see below.
>
> > It may be worth checking the package pre- & post- scripts to see if
> > this is something that could possibly happen.
> FYI these are stored in /var/lib/dpkg/info/mozilla-firefox.p*
ah, thanks.
> > Perhaps also it is something to do with the plugin set I have;
> > libmozsvgdec.so, libjavaplugin_oji.so, libflashplayer.so
> Would you try disabling those extensions by running mozilla-firefox
> -safe-mode and see if that changes anything?
My thought was that installing these may have nuked the Extensions.rdf
file. -safe-mode didn't seem to have much effect.
# pwd
/root
# mv .mozilla nomozilla
# mv /etc/mozilla-firefox/profile/extensions/Extensions.rdf /tmp
# firefox -safe-mode
This sequence gives me the three error messages.
> /var/lib/mozilla-firefox/extensions/Extensions.rdf is a link to
> /usr/lib/mozilla-firefox/extensions/Extensions.rdf.
>
> /var/lib/mozilla-firefox/extensions/Extensions.rdf and
> /usr/lib/mozilla-firefox/defaults/profile/extensions/Extensions.rdf
> are removed on prerm remove.
>
> The postinst and postrm all call
> update-mozilla-firefox-chrome, which does:
>
> cat <<EOF > ${LIBDIR}/extensions/Extensions.rdf
> [...]
> mv ${LIBDIR}/extensions/Extensions.rdf ${VARDIR}/extensions/
> ln -fs ${VARDIR}/extensions/Extensions.rdf ${LIBDIR}/extensions/
>
> So reconfiguring *should* have fixed it. If prerm remove fails, this
> could have been deleted, but, if postinst returned successfully, they
> should have been recreated. Can you check what package state
> mozilla-firefox is in? dpkg -l mozilla-firefox
ii mozilla-firefox 1.0.4-2sarge7 lightweight web browser based on Mozilla
> I see the following changelog entry:
> | * debian/update-mozilla-firefox-chrome: Re-initialize Extensions.rdf
> | inside the script instead of relying on mozilla-firefox's default
> | behaviour, which just fails when defaults/profile/extensions/ \
> | Extensions.rdf doesn't exist (and it seems some people like to remove
> | files in /etc). (Closes: #294175)
This seems pretty relevant.
I am fairly sure no-one would have intentionally removed the file, this
is why I am wondering if plugin/extension installation could cause the
problem. I have tried out various extensions (eg for CSS editing) and
mostly deleted them again. Installation of these usually requires running
the browser as root.
Thanks for the fast response, hope this helps
Vince
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
