Bug 143350

Summary:	Debug message displayed every time JavaScript extension initiated
Product:	[Applications] kst	Reporter:	Andrew Walker <arwalker>
Component:	general	Assignee:	kst
Status:	RESOLVED LATER
Severity:	normal
Priority:	NOR
Version:	1.x
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andrew Walker 2007-03-22 18:29:28 UTC

Version:           HEAD (using KDE KDE 3.5.1)
Installed from:    Compiled From Sources
OS:                Linux

PROBLEM:

Every time the JS extension is initiated (the first time it is shown in a session or every time it is shown after the user closes it by typing "exit") a debug message reading "Uh oh.. can't write data.." is displayed

STEPS TO REPRODUCE:

Start Kst
Enable the JavaScript extension if necessary
Select Tools... Show JavaScript Console

RESULTS:

Debug message "Uh oh.. can't write data.." is displayed

EXPECTED RESULTS:

No such debug message is displayed

Comment 1 Netterfield 2007-03-29 00:16:36 UTC

I can't confirm this exact bug, but instead I get the following "useful" collection of comments (with --disable-debug or with --enable-debug=no):

kst: WARNING: KGenericFactory: instance requested but no instance name or about data passed to the constructor!
kio (KMimeType): WARNING: KServiceType::offers : servicetype JSBindingPlugin/Binding not found
kst: WARNING: addBindingsClass() KJSEmbed::KJSEmbedPart not known
kst: WARNING: addBindingsClass() KJSEmbed::Bindings::Config not known
kst: WARNING: addBindingsClass() KstUIMerge not known

I can find most of these as kdWarning() in jsobjectproxy.cpp in kjsembed.

Comment 2 George Staikos 2007-03-29 00:24:50 UTC

There is nothing we can do about these.

--
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/

Comment 3 Netterfield 2007-03-29 00:40:35 UTC

Why not? (just curious).

On Wednesday 28 March 2007 6:24:51 pm George Staikos wrote:
> There is nothing we can do about these.

Comment 4 George Staikos 2007-03-29 01:09:56 UTC

We don't control KJSEmbed.  We don't even use our fork of it unless  
absolutely necessary and it's only one strange combination that  
triggers it. (KDE recent enough to use kjsembed but too old for our  
purposes)

--
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/

Comment 5 George Staikos 2007-03-30 20:31:07 UTC

Sorry, we really can't do anything here.  Eventually we'll use something else which won't display these messages.  For what it's worth some people might get even more warnings because of kjsembed loading plugins.