Hi, I reassing this bug to mozilla-firefox because
update-mozilla-firefox-chrome is the failing script.
I've tried to reproduce the bug, but I didn't get it with "standard" methods
(installing and removing packages).
There are two reporters of the bug. The second one got the bug because he
removed /etc/mozilla-firefox/profile. I can reproduce the problem in this
way, but I'm unsure if this is a bug or it's the user's fault because he
deleted some necessary files.
The first reporter didn't do anything special to get the problem, but he
doesn't have it anymore so I can't get any new clue.
I deleted my /etc/mozilla-firefox/profile to reproduce the error and try to
find the exact point where update-mozilla-firefox-chrome was failing.
I replaced the line:
# gen
firefox-bin -register >/dev/null 2>&1 || echo "E: Registration process existed
with status: $?" >&2
with the following line:
# gen
firefox-bin -register 2>&1 && echo "E: Registration process existed with
status: $?" >&2
Then I got the following messages:
"Updating mozilla-firefox chrome registry...Extension System Warning: Failed
to set up default extensions files probably because you do not have write
privileges to this location. While you can run Firefox like this, it is
recommended that you run it at least once with privileges that allow it to
generate these initial files to improve start performance. Running froma disk
image on MacOS X is not recommended.Extension System Warning: Failed to set
up default extensions files probably because you do not have write privileges
to this location. While you can run Firefox like this, it is recommended that
you run it at least once with privileges that allow it to generate these
initial files to improve start performance. Running froma disk image on MacOS
X is not recommended.E: Registration process existed with status: 0
E: /usr/lib/mozilla-firefox/extensions/installed-extensions.txt still present.
Registration might have gone wrong.
mv: cannot stat `/usr/lib/mozilla-firefox/defaults.ini': No such file or
directory"
It seems that firefox-bin -register fails, but then returns status 0!!
As far as I understand, the normal process inside
update-mozilla-firefox-chrome is:
1) rm -f ${LIBDIR}/defaults.ini
2) then firefox-bin -register creates a new defaults.ini
3) mv ${LIBDIR}/defaults.ini ${VARDIR}/
ln -fs ${VARDIR}/defaults.ini ${LIBDIR}/
As firefox-bin -register is failing, default.ini isn't created, and then mv
${LIBDIR}/defaults.ini ${VARDIR}/ is failing.
I hope my explaination was useful (or maybe was I explaining obvious things
for you?).
Regards,
César
