Now running Hardy. The bug is still present. The workaround does nothing for me. Version information:
compiz: Installed: 1:0.7.4-0ubuntu7 Candidate: 1:0.7.4-0ubuntu7 Version table: *** 1:0.7.4-0ubuntu7 0 500 http://us.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 1:0.7.4-0ubuntu6 0 500 http://us.archive.ubuntu.com hardy/main Packages
firefox: Installed: 3.0.2+build6+nobinonly-0ubuntu1~fta1~hardy Candidate: 3.0.2+build6+nobinonly-0ubuntu1~fta1~hardy Version table: *** 3.0.2+build6+nobinonly-0ubuntu1~fta1~hardy 0 500 http://ppa.launchpad.net hardy/main Packages 100 /var/lib/dpkg/status 3.0.1+build1+nobinonly-0ubuntu0.8.04.3 0 500 http://us.archive.ubuntu.com hardy-updates/main Packages 500 http://security.ubuntu.com hardy-security/main Packages 3.0~b5+nobinonly-0ubuntu3 0 500 http://us.archive.ubuntu.com hardy/main Packages
[Yeah, I'm using the fta Firefox but I've had this issue with all Firefoxes I've used in compiz.]
nvidia-glx-new: Installed: 169.12+2.6.24.13-19.45 Candidate: 169.12+2.6.24.13-19.45 Version table: *** 169.12+2.6.24.13-19.45 0 500 http://us.archive.ubuntu.com hardy-updates/restricted Packages 500 http://security.ubuntu.com hardy-security/restricted Packages 100 /var/lib/dpkg/status 169.12+2.6.24.12-16.34 0 500 http://us.archive.ubuntu.com hardy/restricted Packages
xorg: Installed: 1:7.3+10ubuntu10.2 Candidate: 1:7.3+10ubuntu10.2 Version table: *** 1:7.3+10ubuntu10.2 0 500 http://us.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 1:7.3+10ubuntu10 0 500 http://us.archive.ubuntu.com hardy/main Packages
As I mentioned in an earlier comment, this bug is not always present. Firefox can run fine for several hours and then the bug shows up. I do not know of a sequence of actions to reproduce the bug.
Now running Hardy. The bug is still present. The workaround does nothing for me. Version information:
compiz: us.archive. ubuntu. com hardy-updates/main Packages dpkg/status 0.7.4-0ubuntu6 0 us.archive. ubuntu. com hardy/main Packages
Installed: 1:0.7.4-0ubuntu7
Candidate: 1:0.7.4-0ubuntu7
Version table:
*** 1:0.7.4-0ubuntu7 0
500 http://
100 /var/lib/
1:
500 http://
firefox: nobinonly- 0ubuntu1~ fta1~hardy nobinonly- 0ubuntu1~ fta1~hardy nobinonly- 0ubuntu1~ fta1~hardy 0 ppa.launchpad. net hardy/main Packages dpkg/status 0.1+build1+ nobinonly- 0ubuntu0. 8.04.3 0 us.archive. ubuntu. com hardy-updates/main Packages security. ubuntu. com hardy-security/main Packages 0~b5+nobinonly- 0ubuntu3 0 us.archive. ubuntu. com hardy/main Packages
Installed: 3.0.2+build6+
Candidate: 3.0.2+build6+
Version table:
*** 3.0.2+build6+
500 http://
100 /var/lib/
3.
500 http://
500 http://
3.
500 http://
[Yeah, I'm using the fta Firefox but I've had this issue with all Firefoxes I've used in compiz.]
nvidia-glx-new: 2.6.24. 13-19.45 2.6.24. 13-19.45 2.6.24. 13-19.45 0 us.archive. ubuntu. com hardy-updates/ restricted Packages security. ubuntu. com hardy-security/ restricted Packages dpkg/status 12+2.6. 24.12-16. 34 0 us.archive. ubuntu. com hardy/restricted Packages
Installed: 169.12+
Candidate: 169.12+
Version table:
*** 169.12+
500 http://
500 http://
100 /var/lib/
169.
500 http://
xorg: us.archive. ubuntu. com hardy-updates/main Packages dpkg/status 7.3+10ubuntu10 0 us.archive. ubuntu. com hardy/main Packages
Installed: 1:7.3+10ubuntu10.2
Candidate: 1:7.3+10ubuntu10.2
Version table:
*** 1:7.3+10ubuntu10.2 0
500 http://
100 /var/lib/
1:
500 http://
As I mentioned in an earlier comment, this bug is not always present. Firefox can run fine for several hours and then the bug shows up. I do not know of a sequence of actions to reproduce the bug.