krusader crashes with BadWindow - invalid Window parameter

Krusader when doing some simple operation like creating new folder or moving the files.

See the following details:

$ krusader
krusader(7345)/kdeui (kdelibs) KDialogPrivate::queuedLayoutUpdate: QueueDialog created with a layout; don't do that, KDialog takes care of it, use mainWidget or setMainWidget instead
This is SMPlayer v. 0.8.3 running on Linux
The program 'krusader' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 103429 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
A KUiServerJobTracker instance contains 1 stalled jobs

$ krusader --sync
This is SMPlayer v. 0.8.3 running on Linux
The program 'krusader' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 91698 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

This one happened when executed picture file:

(gdb) run
Starting program: /usr/bin/krusader --sync
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb2e44b40 (LWP 10853)]
[New Thread 0xb24ffb40 (LWP 10854)]
[New Thread 0xb0a1eb40 (LWP 10855)]
[Thread 0xb2e44b40 (LWP 10853) exited]
krusader(10852)/kdeui (kdelibs) KDialogPrivate::queuedLayoutUpdate: QueueDialog created with a layout; don't do that, KDialog takes care of it,
use mainWidget or setMainWidget instead
krusader(10852)/kparts KParts::PartManager::addPart: Part ' "" ' has a widget "" with a focus policy of NoFocus. It should have at least a ClickFocus policy, for part activation to work well.

krusader(10852)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x8d11388 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
krusader(10852)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Message did not receive a reply (timeout by message bus)"

[New Thread 0xb2e44b40 (LWP 10923)]
[Thread 0xb2e44b40 (LWP 10923) exited]
[New Thread 0xb2e44b40 (LWP 10925)]
[Thread 0xb2e44b40 (LWP 10925) exited]
krusader(10852)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Message did not receive a reply (timeout by message bus)"
[New Thread 0xb2e44b40 (LWP 10950)]

(process:10951): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
The program 'krusader' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 203385 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
A KUiServerJobTracker instance contains 1 stalled jobs
[Thread 0xb2e44b40 (LWP 10950) exited]
[Thread 0xb24ffb40 (LWP 10854) exited]
[Thread 0xb55a0740 (LWP 10852) exited]
[Inferior 1 (process 10852) exited with code 01]