By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1468 - EmbedJS crashes
Summary: EmbedJS crashes
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: non-core programs (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2013-04-20 14:21 CDT by Darrell
Modified: 2018-08-30 02:52 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2013-04-20 14:21:20 CDT 
The EmbedJS app (Development menu) would not close when I selected the Cancel button. When I selected the OK button the app crashed.

Backtrace:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[TDECrash handler]
#5  KJS::ValueImp::dispatchType (this=0x0) at /dev/shm/tdelibs/kjs/value.cpp:174
#6  0xb75ca47d in KJS::Value::type (this=this@entry=0xbff3a8a8) at /opt/trinity/include/kjs/value.h:196
#7  0xb75c9660 in KJSEmbed::KJSEmbedPart::callMethod (this=0x8d03500, methodName=..., args=...) at kjsembedpart.cpp:392
#8  0x0804e99c in EmbedViewImp::okClicked (this=0x8ce3088) at embedviewimp.cpp:32
#9  0x08cfd628 in ?? ()
#10 0x0000001a in ?? ()
#11 0xb7476bd0 in ?? () from /opt/trinity/lib/libtqt-mt.so.3
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Comment 1 Darrell 2013-10-03 16:00:02 CDT 
I notice the following stdout/stderr messages when opening and trying to close EmbedJS:

[tdeinit] embedjs is executable. Launching with exec.
embedjs: WARNING: addBindingsClass() KJSEmbed::KJSEmbedPart not known
embedjs: WARNING: addBindingsClass() KJSEmbed::Bindings::Config not known
kjsembed: WARNING: findSignature: not supported type setEchoMode(EchoMode)
kjsembed: WARNING: findSignature: not supported type setValidator(const TQValidator*)
kjsembed: WARNING: findSignature: not supported type setPalette(const TQPalette&)
kjsembed: WARNING: findSignature: not supported type rotateText(TDECompletionBase::KeyBindingType)
kjsembed: WARNING: findSignature: not supported type setEchoMode(EchoMode)
kjsembed: WARNING: findSignature: not supported type setValidator(const TQValidator*)
kjsembed: WARNING: findSignature: not supported type setPalette(const TQPalette&)
kjsembed: WARNING: findSignature: not supported type rotateText(TDECompletionBase::KeyBindingType)
kjsembed: WARNING: findSignature: not supported type setEchoMode(EchoMode)
kjsembed: WARNING: findSignature: not supported type setValidator(const TQValidator*)
kjsembed: WARNING: findSignature: not supported type setPalette(const TQPalette&)
kjsembed: WARNING: findSignature: not supported type rotateText(TDECompletionBase::KeyBindingType)
embedjs: WARNING: addBindingsClass() EmbedViewImp not known
embedjs: WARNING: Could not open file 'test.js', No such file or directory
Comment 2 Michele Calgaro 2013-12-13 06:53:25 CST 
See this link
https://bugs.kde.org/show_bug.cgi?id=145917

Apparently the bug was fixed in KDE.

As for the Cancel button, it is not meant to close the window but to clear the three text fields. Really counter intuitive. I suggest we rename the button "Clear fields" and move it to the left, near the console button.
Comment 3 Darrell 2013-12-13 10:00:26 CST 
Somebody closing the report as fixed doesn't mean the bug was actually fixed. :-) The KDE folks have a history of doing things like that, not to mention that often the KDE bug reports fail to cite the commit number of the patch. :-(

The bug was filed against 3.5.7, which means the bug should not be present in 3.5.10. I tested this in 3.5.10 and the bug exists.

I don't believe the bug was fixed. I suspect the report was instead "closed as fixed" because of the timeline and non-activity from the OP.

>I suggest we rename the button "Clear fields" and move it to the left, near
>the console button.
Sounds good to me. Or just "Clear" might suffice.