This suggests that either:
1) The trigger was a change in some other package (firefox seems like the most likely bet, but I'm not prepared to try downgrading firefox on my live desktop without some more thought)
2) I messed up my testing somehow, and even when I thought I had reinstalled things, I had not. Since the plugin is running out-of-process, though, I'm not sure how that would be possible. If anyone wants to confirm these tests, with a reboot in between each to make sure that all state is cleared, feel free. Basically what you have to do is:
a) Add jaunty lines to your /etc/apt/sources.list (but leave your karmic lines there!):
deb http://us.archive.ubuntu.com/ubuntu/ jaunty main universe restricted multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty main universe restricted multiverse
b) apt-get update
c) Downgrade with 'apt-get install flashplugin-installer=jaunty', 'apt-get install nspluginwrapper=jaunty'. Well, except that didn't want to work for me, so I used 'apt-get install flashplugin-installer=10.0.22.87ubuntu2', 'apt-get install nspluginwrapper=1.2.2-0ubuntu5' which happen to be the versions in jaunty.
d) Don't forget to remove the jaunty lines from /etc/apt/sources.list (though they are unlikely to hurt anything)
e) 'apt-get install nspluginwrapper flashplayer-nonfree' should re-upgrade you to the latest version from karmic.
My tests are on Karmic, firefox 3.5.3+build1+nobinonly-0ubuntu3, on amd64, with metacity window manager, intel video.
I just tested whether downgrading the flash plugin or nspluginwrapper to the versions in jaunty affected this bug.
For me, I see:
karmic nspluginwrapper, karmic flashplayer.so: buggy
karmic nspluginwrapper, jaunty flashplayer.so: buggy
jaunty nspluginwrapper, karmic flashplayer.so: buggy
jaunty nspluginwrapper, jaunty flashplayer.so: buggy
This suggests that either:
1) The trigger was a change in some other package (firefox seems like the most likely bet, but I'm not prepared to try downgrading firefox on my live desktop without some more thought)
2) I messed up my testing somehow, and even when I thought I had reinstalled things, I had not. Since the plugin is running out-of-process, though, I'm not sure how that would be possible. If anyone wants to confirm these tests, with a reboot in between each to make sure that all state is cleared, feel free. Basically what you have to do is:
a) Add jaunty lines to your /etc/apt/ sources. list (but leave your karmic lines there!): us.archive. ubuntu. com/ubuntu/ jaunty main universe restricted multiverse us.archive. ubuntu. com/ubuntu/ jaunty main universe restricted multiverse installer= jaunty' , 'apt-get install nspluginwrapper =jaunty' . Well, except that didn't want to work for me, so I used 'apt-get install flashplugin- installer= 10.0.22. 87ubuntu2' , 'apt-get install nspluginwrapper =1.2.2- 0ubuntu5' which happen to be the versions in jaunty. sources. list (though they are unlikely to hurt anything) nonfree' should re-upgrade you to the latest version from karmic.
deb http://
deb-src http://
b) apt-get update
c) Downgrade with 'apt-get install flashplugin-
d) Don't forget to remove the jaunty lines from /etc/apt/
e) 'apt-get install nspluginwrapper flashplayer-
My tests are on Karmic, firefox 3.5.3+build1+ nobinonly- 0ubuntu3, on amd64, with metacity window manager, intel video.