Version: (using KDE 4.2.1) OS: Linux Installed from: Ubuntu Packages Application: kttsd (kttsd), signal SIGSEGV Thread 1 (Thread 0xb5d599f0 (LWP 9649)): [KCrash Handler] #6 0x0805d16c in _start ()
this bug doesn't allow me to make the okular read the document. Please help me with this as need to read a lot of document on the daily basis and reading is a better stress free way of doing the same. Hope to get the solution for the same! :) Thanks in advance...
Here is a somewhat more complete backtrace we received in a downstream report of the crash (https://launchpad.net/bugs/279595), though even this backtrace seems a bit mangled: #0 SpeechData::getAppData (this=0x0, appId=@0x7fff0e96cdf0) at /build/buildd/kdeaccessibility-4.1.2/kttsd/kttsd/speechdata.cpp:166 No locals. #1 0x00000000004090f4 in KSpeech::setApplicationName (this=0x11272a0, applicationName=@0x107a020) at /build/buildd/kdeaccessibility-4.1.2/kttsd/kttsd/kspeech.cpp:143 No locals. #2 0x000000000040bfbb in KSpeech::qt_metacall (this=0x11272a0, _c=QMetaObject::InvokeMetaMethod, _id=17965088, _a=0x7fff0e96cfa0) at /build/buildd/kdeaccessibility-4.1.2/obj-x86_64-linux-gnu/kttsd/kttsd/kspeech.moc:176 No locals. #3 0x000000371e95d351 in QMetaObject::invokeMethod () from /usr/lib/libQtCore.so.4 #4 0x000000000042e223 in KSpeechAdaptor::setApplicationName (this=0x1140aa0, applicationName=@0x107a020, msg=<value optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:388 No locals. #5 0x00000000004325a4 in KSpeechAdaptor::qt_metacall (this=0x1140aa0, _c=QMetaObject::InvokeMetaMethod, _id=17965088, _a=0x7fff0e96d7b0) at /build/buildd/kdeaccessibility-4.1.2/obj-x86_64-linux-gnu/kttsd/kttsd/kspeechadaptor_p.moc:344 No locals. #6 0x000000371fc24ea3 in ?? () from /usr/lib/libQtDBus.so.4 #7 0x000000371fc260b4 in ?? () from /usr/lib/libQtDBus.so.4 #8 0x000000371fc26791 in ?? () from /usr/lib/libQtDBus.so.4 #9 0x000000371fc26aa8 in ?? () from /usr/lib/libQtDBus.so.4 #10 0x000000371e963c75 in QObject::event () from /usr/lib/libQtCore.so.4 #11 0x00000031adbc872d in ?? () #12 0x0000000000000000 in ?? ()
@Jonathan: your backtrace seems to be bug 164518 We don't know if the originally reported crash is the same as it is incomplete. @chirag149: If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
No response. Marking as NEEDSINFO
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.