Bug 188451 - speak the whole document' in tools crashes the application kttsd
Summary: speak the whole document' in tools crashes the application kttsd
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kttsd
Classification: Unmaintained
Component: kttsd (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Jeremy Whiting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-30 08:20 UTC by Prashanth Iyer
Modified: 2018-09-04 14:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kttsd debug trace (147.51 KB, application/octet-stream)
2009-09-30 20:09 UTC, p92
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Prashanth Iyer 2009-03-30 08:20:03 UTC
Version:           0.7.4 (using KDE 4.1.4)
Compiler:           Application: kttsd (kttsd), signal SIGSEGV
[Current thread is 1 (Thread 0xb7f05770 (LWP 3427))]

Thread 1 (Thread 0xb7f05770 (LWP 3427)):
[KCrash Handler]
#6  0x0805a9ac in _start ()
OS:                Linux
Installed from:    Fedora RPMs

when I selected ¨speak the whole document¨ in tools menu, KDE crashed with the following errors : 

The application kttsd (kttsd) crashed and caused the signal 11 (SIGSEGV).

Application: kttsd (kttsd), signal SIGSEGV
[Current thread is 1 (Thread 0xb7f05770 (LWP 3427))]

Thread 1 (Thread 0xb7f05770 (LWP 3427)):
[KCrash Handler]
#6  0x0805a9ac in _start ()
Comment 1 Christoph Feck 2009-05-24 18:12:36 UTC
Hi! If you can reproduce the crash, you could install the debug enabled
packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 p92 2009-09-30 20:09:58 UTC
Created attachment 37267 [details]
kttsd debug trace
Comment 3 Christoph Feck 2009-09-30 22:16:29 UTC
kttsd is part of kdeaccessibility, so that may be the name you have to look for when installing debug packages. If unsure, ask in your distributions forum.

Comment #2 looks like a Phonon or xine problem. I do not know if it is related to the initial report, but that is quite old (from KDE 4.1.4).

The interesting part of the backtrace is that kttsd seems to initiate a Phonon request for each word or sentence, as the trace has 290 threads. No wonder Phonon cannot cope...

Partial backtrace from comment #2:

Application that crashed: kttsd
Version of the application: 0.4.0
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-11-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
in konqueror I select tool -> speak text
this was a long text
I close konqueror

the text is still beeing read
then kttsd crashed

PS: there is no kttsd dbg or dbgsym ine the repositories

 -- Backtrace:
Application: kttsd (kttsd), signal: Aborted
[Current thread is 0 (LWP 5372)]

Thread 1 (Thread 0xb5a479e0 (LWP 5372)):
[KCrash Handler]                        
#6  0xb7f49430 in __kernel_vsyscall ()  
#7  0xb62a56d0 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0xb62a7098 in *__GI_abort () at abort.c:88
#9  0xb3751a9e in _x_ao_new_port (xine=0xbc697ef0, driver=0x4afc260, grab_only=0) at audio_out.c:2292
#10 0xb37a27af in lookupConfigEntry (xine=0xbc697ef0, key=0xb37ce158 "audio.device.alsa_default_device", entry=0xbfe64250, driver=0xb37cde66 "alsa")
    at /build/buildd/phonon-4.3.1/xine/audiooutput.cpp:111
#11 0xb37a2bab in Phonon::Xine::AudioOutput::createPort (this=0x4afb020, deviceDesc=@0x4afb044) at /build/buildd/phonon-4.3.1/xine/audiooutput.cpp:170
#12 0xb37a422c in Phonon::Xine::AudioOutput::xineEngineChanged (this=0x4afb020) at /build/buildd/phonon-4.3.1/xine/audiooutput.cpp:295
#13 0xb3789ab3 in Phonon::Xine::SinkNode::downstreamEvent (this=0x4afb028, e=0x4afb0a8) at /build/buildd/phonon-4.3.1/xine/sinknode.cpp:139
#14 0xb37a13e3 in Phonon::Xine::AudioOutput::downstreamEvent (this=0x4afb020, e=0x4afb0a8) at /build/buildd/phonon-4.3.1/xine/audiooutput.cpp:327
#15 0xb378ad95 in Phonon::Xine::SourceNode::downstreamEvent (this=0x13433b0, e=0x4afb0a8) at /build/buildd/phonon-4.3.1/xine/sourcenode.cpp:110
#16 0xb37a5e47 in Phonon::Xine::MediaObject::downstreamEvent (this=0x13433a0, e=0x4afb0a8) at /build/buildd/phonon-4.3.1/xine/mediaobject.cpp:683
#17 0xb37aa244 in Phonon::Xine::MediaObject::upstreamEvent (this=0x13433a0, e=0x8540ac8) at /build/buildd/phonon-4.3.1/xine/mediaobject.cpp:654
#18 0xb3789577 in Phonon::Xine::SinkNode::upstreamEvent (this=0x4afb028, e=0x8540ac8) at /build/buildd/phonon-4.3.1/xine/sinknode.cpp:89
#19 0xb378952c in Phonon::Xine::SinkNode::findXineEngine (this=0x4afb028) at /build/buildd/phonon-4.3.1/xine/sinknode.cpp:102
#20 0xb37b4c6e in Phonon::Xine::Backend::endConnectionChange (this=0xa11e838, nodes={q_hash = {{d = 0xbfe647a0, e = 0xbfe647a0}}}) at /build/buildd/phonon-4.3.1/xine/backend.cpp:466
#21 0xb38bbe6b in Phonon::PathPrivate::executeTransaction (this=0x1341878, disconnections=@0xbfe647f8, connections=@0xbfe647f4) at /build/buildd/phonon-4.3.1/phonon/path.cpp:46
#22 0xb38bd51e in Phonon::Path::reconnect (this=0xbfe648c8, source=0x1341848, sink=0x12d8d148) at /build/buildd/phonon-4.3.1/phonon/path.cpp:197
#23 0xb38bd68b in Phonon::createPath (source=0x1341848, sink=0x12d8d148) at /build/buildd/phonon-4.3.1/phonon/path.cpp:432
#24 0xb4153f52 in ?? () from /usr/lib/kde4/libkttsd_phononplugin.so
#25 0xb415374c in ?? () from /usr/lib/kde4/libkttsd_phononplugin.so
#26 0xb699356c in KPluginFactory::create (this=0xa084db8, iface=0xb7e458a0 "Player", parentWidget=0x0, parent=0xa0be370, args=@0xbfe64a0c, keyword=@0xbfe64a08)
    at /build/buildd/kde4libs-4.3.1/kdecore/util/kpluginfactory.cpp:176
#27 0x08058304 in _start ()
Comment 4 Christoph Feck 2013-09-12 21:43:15 UTC
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)
Comment 5 Andrew Crouthamel 2018-09-04 14:25:38 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.