Summary: | kword kpart crashes konqueror and ark (embedded viewer) | ||
---|---|---|---|
Product: | kword | Reporter: | George Kiagiadakis <mail> |
Component: | general | Assignee: | Thomas Zander <zander> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, kde-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
George Kiagiadakis
2008-10-28 11:36:49 UTC
*** Bug 177374 has been marked as a duplicate of this bug. *** Fixed in 895414 (In reply to comment #2) > Fixed in 895414 > What beta release of koffice does that relate to? I just tried Koffice Beta 5 and got the crash. Application: Ark (ark), signal SIGSEGV Thread 1 (Thread 0xb5fbf6c0 (LWP 9631)): [KCrash Handler] #6 0xb6ebfd59 in QWidget::setContextMenuPolicy (this=0x0, policy=Qt::ActionsContextMenu) at kernel/qwidget.cpp:6144 #7 0xb3abd3f0 in KWStatusBar (this=0xaae6ad0, statusBar=0x0, view=0xa4290d8) at /tmp/buildd/koffice-1.9.98.5/kword/part/KWStatusBar.cpp:52 #8 0xb3ab0bda in KWView (this=0xa4290d8, viewMode=@0xa3174e4, document=0xa317470, parent=0xa37bd28) at /tmp/buildd/koffice-1.9.98.5/kword/part/KWView.cpp:126 #9 0xb3aa4f13 in KWDocument::createViewInstance (this=0xa317470, parent=0xa37bd28) at /tmp/buildd/koffice-1.9.98.5/kword/part/KWDocument.cpp:157 #10 0xb33fdeb1 in KoDocument::createView (this=0xa317470, parent=0xa37bd28) at /tmp/buildd/koffice-1.9.98.5/libs/main/KoDocument.cpp:338 #11 0xb340bf61 in KoDocument::openFile (this=0xa317470) at /tmp/buildd/koffice-1.9.98.5/libs/main/KoDocument.cpp:1577 #12 0xb7eaf6fa in KParts::ReadOnlyPart::openUrl (this=0xa317470, url=@0xbf831510) at ../../kparts/part.cpp:558 #13 0xb3406832 in KoDocument::openUrl (this=0xa317470, _url=@0xbf8315e4) at /tmp/buildd/koffice-1.9.98.5/libs/main/KoDocument.cpp:1385 #14 0xb4614557 in ArkViewer::viewInInternalViewer (this=0xbf8316b4, filename=@0xbf831780) at ../../../ark/part/arkviewer.cpp:158 #15 0xb4614c59 in ArkViewer::view (filename=@0xbf831780, parent=0xa1124f0) at ../../../ark/part/arkviewer.cpp:106 #16 0xb4608ce1 in Part::slotPreviewExtracted (this=0xa0e6f78, job=0xa2c44d8) at ../../../ark/part/part.cpp:454 #17 0xb460634f in Part::qt_metacall (this=0xa0e6f78, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xa079188) at moc_part.cpp:120 #18 0xb6c65d7b in QMetaCallEvent::placeMetaCall (this=0xa2cc928, object=0xa0e6f78) at kernel/qobject.cpp:529 #19 0xb6c678f1 in QObject::event (this=0xa0e6f78, e=0xa2cc928) at kernel/qobject.cpp:1155 #20 0xb6e7879c in QApplicationPrivate::notify_helper (this=0x9fe00b0, receiver=0xa0e6f78, e=0xa2cc928) at kernel/qapplication.cpp:3803 #21 0xb6e8061e in QApplication::notify (this=0xbf831fe4, receiver=0xa0e6f78, e=0xa2cc928) at kernel/qapplication.cpp:3393 #22 0xb7a4f77d in KApplication::notify (this=0xbf831fe4, receiver=0xa0e6f78, event=0xa2cc928) at ../../kdeui/kernel/kapplication.cpp:307 #23 0xb6c580e1 in QCoreApplication::notifyInternal (this=0xbf831fe4, receiver=0xa0e6f78, event=0xa2cc928) at kernel/qcoreapplication.cpp:587 #24 0xb6c58d65 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9fd42f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209 #25 0xb6c58f5d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1091 #26 0xb6f12e6f in QEventDispatcherX11::processEvents (this=0x9fdfbd0, flags={i = -1081925992}) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:214 #27 0xb6c567aa in QEventLoop::processEvents (this=0xbf831f10, flags={i = -1081925928}) at kernel/qeventloop.cpp:143 #28 0xb6c5696a in QEventLoop::exec (this=0xbf831f10, flags={i = -1081925864}) at kernel/qeventloop.cpp:194 #29 0xb6c59025 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #30 0xb6e78617 in QApplication::exec () at kernel/qapplication.cpp:3331 #31 0x08051fca in main (argc=5, argv=0xbf832384) at ../../../ark/app/main.cpp:204 Should the bug be re-opened? And how to re-open it? @Ritesh: the backtrace is a lot different from the original one. So, even when the effect (ark crashing) is the same, the crash source is different. I think you need to file a new bug report with your information. Thanks :) |