On Sun, May 25, 2008 at 09:44:02AM -0000, Itachi wrote:
> Yes. Even after restarting, the problem was still there, until I ran it
> as a root user, then everything was good.
>
OK, we cannot support your bug. Instead we should fix the core issue:
running firefox as root creates garbage in pkglibdir which will break
profiles once firefox/xulrunner packages have received a considerable
upgrade.
status triaged
importance high
retitle "firefox run as root should not break profiles when firefox got upgraded"
Maybe solution: we might consider to run update-chrome scripts in
postinst again.
On Sun, May 25, 2008 at 09:44:02AM -0000, Itachi wrote:
> Yes. Even after restarting, the problem was still there, until I ran it
> as a root user, then everything was good.
>
OK, we cannot support your bug. Instead we should fix the core issue:
running firefox as root creates garbage in pkglibdir which will break
profiles once firefox/xulrunner packages have received a considerable
upgrade.
status triaged
importance high
retitle "firefox run as root should not break profiles when firefox got upgraded"
Maybe solution: we might consider to run update-chrome scripts in
postinst again.
- Alexander