This bug was fixed in the package firefox - 4.0~b7+nobinonly-0ubuntu1
---
firefox (4.0~b7+nobinonly-0ubuntu1) natty; urgency=low
* New upstream release v4.0 B7 (FIREFOX_4_0b7_RELEASE)
[ Chris Coulson ]
* Don't build with -pie on Natty (LP: #663294)
- update debian/rules
Do we actually use ~/.firefox in any currently support version of
Ubuntu? Or is this from some really old and now unsupported version? If
it's the latter, then I think I'd prefer not to migrate, which would add
more complexity to the startup script. (Especially not to fix what looks
like a very rar
I have no strong opinion on migrate vs not-migrate but feel ~/.firefox to be a
worthwhile addition to the profile. If we are not going to migrate, then I
suggest the following:
- owner @{HOME}/.mozilla/ rw,
- owner @{HOME}/.mozilla/** rw,
- owner @{HOME}/.mozilla/**/*.sqlite* k,
- owner @{HOM
> Would you happen to remember which version of Firefox created these
profiles?
I'm no longer sure, but I would guess Firefox 0.9.
--
Firefox apparmor blocks old profile location
https://bugs.launchpad.net/bugs/624435
You received this bug notification because you are a member of Ubuntu
Bugs, w
Thank you for reporting this to Ubuntu. Would you happen to remember
which version of Firefox created these profiles?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
Firefox apparmor blocks old profile location
https://bugs.launchpad.net/bugs/624435
You received this bug not
@Securtiy team, Chris Coulson
I think we should migrate the old profile rather than adding this to the
apparmor profile. Thoughts?
** Tags added: apparmor lucid
--
Firefox apparmor blocks old profile location
https://bugs.launchpad.net/bugs/624435
You received this bug notification because yo
