kttsmgr crashed with SIGSEGV in QDBusAbstractInterface::callWithArgumentList()

Bug #285348 reported by Maxim
18
Affects Status Importance Assigned to Milestone
KDE Accessibility
Unknown
High
kdeaccessibility (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdeaccessibility

I just run text-to-speech program, then the program ask me to configure it. I press yes. And crash !

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kttsmgr
NonfreeKernelModules: ath_hal
Package: kttsd 4:4.1.2-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/kttsmgr -caption kttsmgr -icon preferences-desktop-text-to-speech
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
Signal: 11
SourcePackage: kdeaccessibility
Stacktrace:
 #0 0xb6debc5d in QDBusAbstractInterface::callWithArgumentList ()
    from /usr/lib/libQtDBus.so.4
 #1 0x0804f3f2 in _start ()
StacktraceTop:
 QDBusAbstractInterface::callWithArgumentList ()
 _start ()
ThreadStacktrace:
 .
 Thread 1 (process 8002):
 #0 0xb6debc5d in QDBusAbstractInterface::callWithArgumentList ()
    from /usr/lib/libQtDBus.so.4
 #1 0x0804f3f2 in _start ()
Title: kttsmgr crashed with SIGSEGV in QDBusAbstractInterface::callWithArgumentList()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Maxim (moonwallker) wrote :
Revision history for this message
In , pleabargain (dennisgdaniels) wrote :

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 ()

Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

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

Revision history for this message
In , Jeremy Whiting (jpwhiting) wrote :

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.

Changed in kdeaccessibility (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in kdeaccessibility:
status: Unknown → New
Revision history for this message
In , Harald Sitter (apachelogger) wrote :
Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing in favor of upstream report since this needs ot be fixed upstream. Please refer there for status updates.

Thanks.

Changed in kdeaccessibility (Ubuntu):
status: Triaged → Invalid
Changed in kdeaccessibility:
importance: Unknown → High
Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

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)

Changed in kdeaccessibility:
status: New → Incomplete
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.

Changed in kdeaccessibility:
status: Incomplete → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.