I can confirm this bug, using a new firefox 3.2 profile, and with my current 3.1 profile too.
So I guess its not so low priority like that.
$ apt-cache policy firefox-3.2 firefox-3.2: Installed: 3.2~a1~hg20090127r24317+nobinonly-0ubuntu1~fta1 Candidate: 3.2~a1~hg20090127r24317+nobinonly-0ubuntu1~fta1 Version table: *** 3.2~a1~hg20090127r24317+nobinonly-0ubuntu1~fta1 0 500 http://ppa.launchpad.net jaunty/main Packages 100 /var/lib/dpkg/status
$ apt-cache policy firefox-3.1 firefox-3.1: Installed: 3.1~b3~hg20090122r22900+nobinonly-0ubuntu1 Candidate: 3.1~b3~hg20090122r22900+nobinonly-0ubuntu1 Version table: *** 3.1~b3~hg20090122r22900+nobinonly-0ubuntu1 0 500 ftp://darkstar.ist.utl.pt jaunty/universe Packages 500 ftp://archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status 3.1~b3~hg20090122r22900+nobinonly-0ubuntu1~fta1 0 500 http://ppa.launchpad.net jaunty/main Packages
I can confirm this bug, using a new firefox 3.2 profile, and with my current 3.1 profile too.
So I guess its not so low priority like that.
$ apt-cache policy firefox-3.2 hg20090127r2431 7+nobinonly- 0ubuntu1~ fta1 hg20090127r2431 7+nobinonly- 0ubuntu1~ fta1 hg20090127r2431 7+nobinonly- 0ubuntu1~ fta1 0 ppa.launchpad. net jaunty/main Packages dpkg/status
firefox-3.2:
Installed: 3.2~a1~
Candidate: 3.2~a1~
Version table:
*** 3.2~a1~
500 http://
100 /var/lib/
$ apt-cache policy firefox-3.1 hg20090122r2290 0+nobinonly- 0ubuntu1 hg20090122r2290 0+nobinonly- 0ubuntu1 hg20090122r2290 0+nobinonly- 0ubuntu1 0 ist.utl. pt jaunty/universe Packages ubuntu. com jaunty/universe Packages dpkg/status 1~b3~hg20090122 r22900+ nobinonly- 0ubuntu1~ fta1 0 ppa.launchpad. net jaunty/main Packages
firefox-3.1:
Installed: 3.1~b3~
Candidate: 3.1~b3~
Version table:
*** 3.1~b3~
500 ftp://darkstar.
500 ftp://archive.
100 /var/lib/
3.
500 http://