The backtrace and the situation seems similar to the ones in bug 206519 and  bug 168427, could you check them ?
Thanks

I can reproduce the crash with the steps in the bug report 168427. The stack trace i think its a bit different, but maybe i'm wrong.
Here's the trace if i reproduce the bug:

Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  KJob::kill (this=0x1848ec0, verbosity=KJob::EmitResult) at /build/buildd/kde4libs-4.3.2/kdecore/jobs/kjob.cpp:106
#6  0x00007f0420e52a52 in KUiServerJobTracker::qt_metacall (this=0x1823920, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffadb55fe0)
    at /build/buildd/kde4libs-4.3.2/obj-x86_64-linux-gnu/kdeui/kuiserverjobtracker.moc:94
#7  0x00007f041f44cea2 in QMetaObject::activate (sender=0x1a2b3b0, from_signal_index=<value optimized out>, to_signal_index=5, argv=0x1808da0) at kernel/qobject.cpp:3113
#8  0x00007f0420fa0bb8 in OrgKdeJobViewInterface::qt_metacall (this=0x1a2b3b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffadb565a0)
    at /build/buildd/kde4libs-4.3.2/obj-x86_64-linux-gnu/kdeui/jobviewiface.moc:90
#9  0x00007f042032c453 in QDBusConnectionPrivate::deliverCall (this=0xd552e0, object=0x1a2b3b0, msg=@0xfad848, metaTypes=@0xfad850, slotIdx=5) at qdbusintegrator.cpp:891
#10 0x00007f0420333e5f in QDBusCallDeliveryEvent::placeMetaCall (this=0x200000001, object=0x1) at qdbusintegrator_p.h:101
#11 0x00007f041f4475d8 in QObject::event (this=0x1a2b3b0, e=0xfad800) at kernel/qobject.cpp:1111
#12 0x00007f041f8ccf4d in QApplicationPrivate::notify_helper (this=0xd683a0, receiver=0x1a2b3b0, e=0xfad800) at kernel/qapplication.cpp:4056
#13 0x00007f041f8d518a in QApplication::notify (this=0x7fffadb56fc0, receiver=0x1a2b3b0, e=0xfad800) at kernel/qapplication.cpp:4021
#14 0x00007f0420e57abb in KApplication::notify (this=0x7fffadb56fc0, receiver=0x1a2b3b0, event=0xfad800) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#15 0x00007f041f4376ac in QCoreApplication::notifyInternal (this=0x7fffadb56fc0, receiver=0x1a2b3b0, event=0xfad800) at kernel/qcoreapplication.cpp:610
#16 0x00007f041f43831a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xd3b320) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x00007f041f460e03 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 0x00007f041aab620a in IA__g_main_context_dispatch (context=0xd63120) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#19 0x00007f041aab98e0 in g_main_context_iterate (context=0xd63120, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#20 0x00007f041aab9a7c in IA__g_main_context_iteration (context=0xd63120, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#21 0x00007f041f460a8f in QEventDispatcherGlib::processEvents (this=0xd3ab50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007f041f965bdf in QGuiEventDispatcherGlib::processEvents (this=0x1848ec0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f041f435f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1380618512}) at kernel/qeventloop.cpp:149
#24 0x00007f041f436314 in QEventLoop::exec (this=0x7fffadb56f30, flags={i = -1380618432}) at kernel/qeventloop.cpp:201
#25 0x00007f041f4385e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x00000000004397cd in main (argc=1, argv=0x7fffadb574a8) at /build/buildd/kdebase-4.3.2/apps/dolphin/src/main.cpp:94

From bug 215698:
---
What I was doing when the application crashed:
While copying several files from one folder to the other (on the same hard
drive) I've noticed that the progress wheel in the Notifications and Jobs was
still runnign although the files has finished copying and that subsequent jobs,
although completed, still showed as outstanding.

Could not recreate the original problem of jobs still showing as in progress
while actually completed and things are working as expected now.

*** Bug 215698 has been marked as a duplicate of this bug. ***

*** Bug 217940 has been marked as a duplicate of this bug. ***

From bug 228649:
-- Information about the crash:
When i try to stop a transfer via the knotifiy bubble dolphin crashed,possible
duplicates and full backtrace attached

*** Bug 228649 has been marked as a duplicate of this bug. ***

This could also be related to bug 192547 / bug 168427

From bug 227772:
-- Information about the crash:
Dolphin crashed after pressing the stop button in the notifications systray.

1. Before this I deleted a log file in a folder in Dophin it was a log file.
2. I could see the logfile disappear (has been moved to trash)
3. A moment later the server created the logfile again - the file re-appeared
4. I hit Ctrl+Z to undo the deletion 
5. A message appeared that that file already exists.
6. I think that I deleted the file again - The notification systray showed a
process in action.
7. After hours I realised that there is a process running in the systray
8. the crash log appeared after hitting the stop button in the notification
systray

 -- Backtrace:
#6  0x080cc73d in QString::shared_null ()
#7  0x088a10b2 in KJob::kill (this=0x9fb5b20, verbosity=KJob::EmitResult) at
../../kdecore/jobs/kjob.cpp:106
#8  0x00fe2057 in KUiServerJobTracker::Private::_k_killJob (this=0x9d427a8) at
../../kdeui/jobs/kuiserverjobtracker.cpp:58
#9  0x00fe20c9 in KUiServerJobTracker::qt_metacall (this=0x9d4f1e0,
_c=QMetaObject::InvokeMetaMethod, _id=25, _a=0xbfdad02c) at
./kuiserverjobtracker.moc:100
#10 0x02883f6a in QMetaObject::metacall (object=0x9d4f1e0,
cl=QMetaObject::QueryPropertyEditable, idx=25, argv=0xbfdad02c) at
kernel/qmetaobject.cpp:237
#11 0x02892705 in QMetaObject::activate (sender=0x971bfa8, m=0x11b74a4,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3275
#12 0x01163687 in OrgKdeJobViewInterface::cancelRequested (this=0x971bfa8) at
jobviewiface.moc:119
#13 0x01163a83 in OrgKdeJobViewInterface::qt_metacall (this=0x971bfa8,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfdad2ec) at jobviewiface.moc:96
#14 0x0023e034 in QDBusConnectionPrivate::deliverCall (this=0x92ecb30,
object=0x971bfa8, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:904
...

*** Bug 227772 has been marked as a duplicate of this bug. ***

Created attachment 43161 [details]
New crash information added by DrKonqi

My steps to reproduce it
* Create a folder a
* Create a folder b
* Create a text file t inside a
* Move t to folder b
* Erase permanently folder a (ie shift+del)
* Undo moving t to folder b (may mistake i was trying to undo folder deletion), since a no longer exist it show a message saying such.
* If I stop tray bar notification dolphin crashes

It does happen 100% of the time.

fixed in r1134645

*** Bug 237172 has been marked as a duplicate of this bug. ***

*** Bug 245220 has been marked as a duplicate of this bug. ***

*** Bug 234868 has been marked as a duplicate of this bug. ***

[Comment from a bug triager]
According to bug 240752, there are some cases on KDE SC 4.5.x; so this may should be reopened.

*** Bug 215316 has been marked as a duplicate of this bug. ***

*** Bug 232526 has been marked as a duplicate of this bug. ***

*** Bug 256877 has been marked as a duplicate of this bug. ***

*** Bug 274092 has been marked as a duplicate of this bug. ***

*** Bug 280909 has been marked as a duplicate of this bug. ***

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!