Version: (using KDE 4.2.3) OS: Linux Installed from: Ubuntu Packages Application: KTTSMgr (kttsmgr), signal SIGSEGV [Current thread is 0 (LWP 9532)] Thread 2 (Thread 0xb3c6db90 (LWP 9539)): #0 0xb7f76430 in __kernel_vsyscall () #1 0xb6ae17b1 in select () from /lib/tls/i686/cmov/libc.so.6 #2 0xb6db5380 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb6ce396e in ?? () from /usr/lib/libQtCore.so.4 #4 0xb62c64ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0xb6ae949e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb5f28700 (LWP 9532)): [KCrash Handler] #6 0xb6efd987 in QDBusAbstractInterface::asyncCallWithArgumentList () from /usr/lib/libQtDBus.so.4 #7 0x0804fc67 in _start ()
*** Bug 191731 has been marked as a duplicate of this bug. ***
If you can reproduce this bug, could you also see if it's gone in 4.3 (beta or release once it comes out). Some dbus socket stuff was fixed in kttsd recently.
Also reported at: https://bugs.launchpad.net/ubuntu/+source/kdeaccessibility/+bug/285348
This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.