kword crashed with SIGSEGV in KoFilterChain::ChainLink::invokeFilter()

[kikoloche]

Binary package hint: koffice2

kword crashed with SIGSEGV in KoFilterChain::ChainLink::invokeFilter()

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kword
NonfreeKernelModules: nvidia
Package: kword-kde4 1:1.9.98.7-0ubuntu2
ProcCmdline: /usr/bin/kword /media/Datos/7\ y.docx
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: koffice2
StacktraceTop:
 ?? () from /usr/lib/kde4/libmswordodf_import.so
 ?? () from /usr/lib/kde4/libmswordodf_import.so
 KoFilterChain::ChainLink::invokeFilter ()
 KoFilterChain::invokeChain ()
 KoFilterManager::importDocument ()
Title: kword crashed with SIGSEGV in KoFilterChain::ChainLink::invokeFilter()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:~Document (this=0x225dce0)
MSWordOdfImport::convert (this=0x2312660,
KoFilterChain::ChainLink::invokeFilter (
KoFilterChain::invokeChain (this=0x2304e10)
KoFilterManager::importDocument (this=0x22712c0,

[Tomasz Czapiewski (xeros)]

The same crash happened to me in kword-kde4 1:1.9.99.9-0ubuntu1.

[Harald Sitter (apachelogger)]

Heya!

I assume this crash happened when you tried to open a .docx file? Please always add a description of what you were doing at the time the crash happened when you report one, it makes tracing the issue a lot easier :)

In any case, please upgrade to KOffice 2.0.0
http://www.kubuntu.org/news/koffice-2
and, if possible, install the package koffice-kde4-dbg. Then try to retrigger the crash, should it stil affect 2.0.0 you should get a new, more useful backtrace (crash log) than the one from earlier (thanks to the magic -dbg package :))

Also, if it is really because you are trying to open a .docs file, it would be very awesome if you could attach the file to this report (that is, if it doesn't contain any data that shouldn't be published).

Thanks in advance and have a nice day :)

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!