Bug#443600: konqueror-nsplugins: I think this was marked done prematurely

2007-10-06 Thread Shai Berger
On Saturday 06 October 2007, Kevin Krammer wrote: > > Adobe wrote a plugin for an application supporting the Netscape Plugin API. > Since this API does not in any way specify that GTK is used for the APIs > implementation, they can not assume this. > With this, I stand corrected on all claims abou

Bug#443600: konqueror-nsplugins: I think this was marked done prematurely

2007-10-06 Thread Kevin Krammer
On Saturday 06 October 2007, Shai Berger wrote: > Hi Sune, > > Thanks for your clarification about the reason for the 100% CPU. For the > rest, however, > > On Saturday 06 October 2007, Sune Vuorela wrote: > > nspluginviewer can't initialize any kind of environment that a plugin > > might or might

Bug#443600: konqueror-nsplugins: I think this was marked done prematurely

2007-10-06 Thread Shai Berger
Hi Sune, Thanks for your clarification about the reason for the 100% CPU. For the rest, however, On Saturday 06 October 2007, Sune Vuorela wrote: > > nspluginviewer can't initialize any kind of environment that a plugin might > or might not use. remember that this is plugins. If a plugin needs >

Bug#443600: konqueror-nsplugins: I think this was marked done prematurely

2007-10-06 Thread Sune Vuorela
On Monday 01 October 2007, Shai Berger wrote: > > It is even arguable that initializing an environment (like gtk) > is something only an app (like nspluginviewer) should do, > and not a library (like flash) -- even though I've seen it > argued that multiple GTK initialization is harmless. > nspl

Bug#443600: konqueror-nsplugins: I think this was marked done prematurely

2007-09-30 Thread Shai Berger
Package: konqueror-nsplugins Version: 4:3.5.7-4 Followup-For: Bug #443600 Hi, This bug still bites hard. While it is true that Adobe is ultimately to blame (as it is their code which uses GTK without initializing it), nspluginviewer could initialize GTK for their library, and allow debian/konque