Comment 16 for bug 462433

Should we expect an update for F8 as well? This is a small sample from
one of machines with nspluginwrapper-0.9.91.5-18.fc8:

Oct 20 17:17:28 epsilon kernel: npviewer.bin[19769]: segfault at 0 ip 0 sp ffeb191c error 14
Oct 20 17:17:29 epsilon kernel: npviewer.bin[19785]: segfault at 0 ip 0 sp ffa6bcdc error 14
Oct 20 17:17:30 epsilon kernel: npviewer.bin[19801]: segfault at 0 ip 0 sp ff960bcc error 14
Oct 21 19:35:22 epsilon kernel: npviewer.bin[4142]: segfault at 0 ip 0 sp ffdcb84c error 14
Oct 21 19:35:23 epsilon kernel: npviewer.bin[4178]: segfault at 0 ip 0 sp fff2b1ac error 14
Oct 21 19:35:24 epsilon kernel: npviewer.bin[4214]: segfault at 0 ip 0 sp ffcaaf2c error 14
Oct 21 19:35:26 epsilon kernel: npviewer.bin[4250]: segfault at 0 ip 0 sp ff9293ac error 14
Oct 22 15:11:30 epsilon kernel: npviewer.bin[6279]: segfault at 0 ip 0 sp ffd0664c error 14
Oct 22 15:11:31 epsilon kernel: npviewer.bin[6315]: segfault at 0 ip 0 sp fffcf10c error 14
Oct 22 15:11:32 epsilon kernel: npviewer.bin[6351]: segfault at 0 ip 0 sp ff9c630c error 14
Oct 22 15:11:34 epsilon kernel: npviewer.bin[6407]: segfault at 0 ip 0 sp ff80694c error 14
Oct 22 15:30:31 epsilon kernel: npviewer.bin[27430]: segfault at 0 ip 0 sp ffd8aecc error 14
Oct 22 15:30:31 epsilon kernel: npviewer.bin[27446]: segfault at 0 ip 0 sp ff913a5c error 14
Oct 22 15:30:31 epsilon kernel: npviewer.bin[27482]: segfault at 0 ip 0 sp ff8989dc error 14

This one sports two processors though.