here is the output on running krunner from console:



KCrash: Attempting to start /usr/bin/krunner from kdeinit
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
KCrash: Application 'krunner' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
unnamed app(9841): Communication problem with  "krunner" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

All dependencies are satisfied. Using KDE Factory for openSUSE 11.3

[Comment from a bug triager]
- Try using GDB to retrieve a backtrace:

- Run Konsole
- Type "killall -9 krunner" + Enter to quit all the possible KRunner instances
- Type "gdb krunner" + Enter
- On the GDB prompt type "r" + Enter
KRunner should start and crash
- When you are on the GDB prompt again, type "thread apply bt full" + Enter
- Then type "bt full" + Enter (press Enter a couple of times)
- Copy the output of that last command here.

You can get more information at: http://techbase.kde.org/User:DarioAndres/CreateUsefulReports#Retrieving_a_backtrace_with_GDB

Thanks

(In reply to comment #3)
> [Comment from a bug triager]
> - Try using GDB to retrieve a backtrace:
> 
> - Run Konsole
> - Type "killall -9 krunner" + Enter to quit all the possible KRunner instances
> - Type "gdb krunner" + Enter
> - On the GDB prompt type "r" + Enter
> KRunner should start and crash
> - When you are on the GDB prompt again, type "thread apply bt full" + Enter
> - Then type "bt full" + Enter (press Enter a couple of times)
> - Copy the output of that last command here.

I just get "No stack". 

I have both installed:
kdebase4-debuginfo
kdebase4-workspace-debuginfo

Any suggestions?

Application: Run Command Interface (krunner), signal: Floating point exception
[Current thread is 1 (Thread 0xb0e78b10 (LWP 18270))]

Thread 2 (Thread 0xae7cbb70 (LWP 18271)):
#0  0xb32c922b in clock_gettime () from /lib/librt.so.1
#1  0xb5d8f265 in do_gettime () at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb5e62d26 in updateCurrentTime (this=0xade01a74, tm=...) at kernel/qeventdispatcher_unix.cpp:339
#4  QTimerInfoList::timerWait (this=0xade01a74, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0xb5e6155b in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xae7cb05c) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb5e615fd in timerSourcePrepare (source=0xade01a40, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb34cb0c0 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#8  0xb34cbf22 in ?? () from /usr/lib/libglib-2.0.so.0
#9  0xb34cc60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#10 0xb5e61da7 in QEventDispatcherGlib::processEvents (this=0x81677a8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0xb5e3289d in QEventLoop::processEvents (this=0xae7cb1f0, flags=...) at kernel/qeventloop.cpp:149
#12 0xb5e32ac9 in QEventLoop::exec (this=0xae7cb1f0, flags=...) at kernel/qeventloop.cpp:201
#13 0xb5d317a9 in QThread::exec (this=0x80b6188) at thread/qthread.cpp:490
#14 0xb5e124ad in QInotifyFileSystemWatcherEngine::run (this=0x80b6188) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb5d3439a in QThreadPrivate::start (arg=0x80b6188) at thread/qthread_unix.cpp:285
#16 0xb37b1cd7 in ?? () from /usr/X11R6/lib/libGL.so.1
#17 0xb778146e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb0e78b10 (LWP 18270)):
[KCrash Handler]
#7  0xb789610a in enter.8102 () from /lib/ld-linux.so.2
#8  0xb7896771 in do_lookup_x () from /lib/ld-linux.so.2
#9  0xb7896b49 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#10 0xb789845b in _dl_relocate_object () from /lib/ld-linux.so.2
#11 0xb789f823 in dl_open_worker () from /lib/ld-linux.so.2
#12 0xb789b50f in _dl_catch_error () from /lib/ld-linux.so.2
#13 0xb789f2e6 in _dl_open () from /lib/ld-linux.so.2
#14 0xb3573bdd in dlopen_doit () from /lib/libdl.so.2
#15 0xb789b50f in _dl_catch_error () from /lib/ld-linux.so.2
#16 0xb3574342 in _dlerror_run () from /lib/libdl.so.2
#17 0xb3573ca7 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2
#18 0xb5e234b5 in QLibraryPrivate::load_sys (this=0x83fe5e0) at plugin/qlibrary_unix.cpp:205
#19 0xb5e1dff4 in QLibraryPrivate::load (this=0x83fe5e0) at plugin/qlibrary.cpp:446
#20 0xb5e1e0d8 in QLibraryPrivate::loadPlugin (this=0x83fe5e0) at plugin/qlibrary.cpp:478
#21 0xb5e17ed3 in QPluginLoader::load (this=0xbf9fb818) at plugin/qpluginloader.cpp:227
#22 0xb6109608 in KPluginLoader::load() () from /usr/lib/libkdecore.so.5
#23 0xb6109a25 in KPluginLoader::pluginVersion() const () from /usr/lib/libkdecore.so.5
#24 0xb747ef07 in Plasma::RunnerManagerPrivate::loadInstalledRunner (this=0x8169280, service=...) at /usr/src/debug/kdelibs-4.5.90/plasma/runnermanager.cpp:251
#25 0xb747fd86 in Plasma::RunnerManagerPrivate::loadRunners (this=0x8169280) at /usr/src/debug/kdelibs-4.5.90/plasma/runnermanager.cpp:218
#26 0xb747b569 in Plasma::RunnerManager::reloadConfiguration (this=0x8169140) at /usr/src/debug/kdelibs-4.5.90/plasma/runnermanager.cpp:441
#27 0xb783a08a in KRunnerApp::initialize (this=0x80b3ee8) at /usr/src/debug/kdebase-workspace-4.5.90/krunner/krunnerapp.cpp:189
#28 0xb783a990 in KRunnerApp::KRunnerApp (this=0x80b3ee8) at /usr/src/debug/kdebase-workspace-4.5.90/krunner/krunnerapp.cpp:79
#29 0xb783aa10 in KRunnerApp::self () at /usr/src/debug/kdebase-workspace-4.5.90/krunner/krunnerapp.cpp:66
#30 0xb783b1e5 in kdemain (argc=1, argv=0xbf9fbdd4) at /usr/src/debug/kdebase-workspace-4.5.90/krunner/main.cpp:62
#31 0x0804860b in main (argc=1, argv=0xbf9fbdd4) at /usr/src/debug/kdebase-workspace-4.5.90/build/krunner/krunner_dummy.cpp:3

Managed to retrieve it with kde crash widget. 

I just realised that if you select the NO when asked if you remember what you were doing prior to the crash it doesn't give you the option to get a backtrace. Having crash dialogs popping all over the screen didn't make things easy either.

[Comment from a bug triager]
1) The backtrace is the same as the crashes at bug 251719; caused by the NVidia official driver on OpenSuse. Try updating to the latest version or switching to a different driver to test.

>I just realised that if you select the NO when asked if you remember what you
>were doing prior to the crash it doesn't give you the option to get a
>backtrace.

That is done to filter out crash reports without some context information, and to reduce the work of the bug triagers and developers.

Regards

I'm using the latest version of the nvidia drivers provided by openSUSE. I know all the other crashes with the same backtrace did not happen with previous versions of the same driver (25x.xx.xx) so it shouldn't be any different with this one. 

While I understand the problem is most probably not on the KDE end, it might be worth noting that krunner did not crash with these same drivers on 4.5. Also ktorrent which did crash on 4.5 is now ok on 4.6. Clock applets and amarok crash in both 4.5 and 4.6. Maybe this can help identify what is triggering the crash and subsequently its origin.

Thank you for your time. 
Good luck with the 4.6 release.