Bug 236108 - kword crash on close after opening .odt
Summary: kword crash on close after opening .odt
Status: RESOLVED DUPLICATE of bug 235345
Alias: None
Product: kword
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Thomas Zander
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-03 02:20 UTC by Rex Dieter
Modified: 2010-05-12 17:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.85 KB, text/plain)
2010-05-03 16:50 UTC, Rex Dieter
Details
New crash information added by DrKonqi (3.85 KB, text/plain)
2010-05-03 16:57 UTC, Rex Dieter
Details
New crash information added by DrKonqi (3.85 KB, text/plain)
2010-05-03 16:57 UTC, Rex Dieter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rex Dieter 2010-05-03 02:20:44 UTC
Application: kword (2.2 RC 1)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.33.2-57.fc13.x86_64 x86_64
Distribution: "Fedora release 13 (Goddard)"

-- Information about the crash:
ingwa asked if I could reproduce a kword crash on close after opening any .odt file using a vanilla/unpatched qt build.  Here it is.

The crash can be reproduced every time.

 -- Backtrace:
Application: KWord (kword), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f95e8f64de8 in ?? () from /usr/lib64/libQtGui.so.4
#6  0x00007f95e8dc098c in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4
#7  0x00007f95ec552c2b in KoMainWindow::~KoMainWindow (this=0x1961890, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>)
    at /usr/src/debug/koffice-2.1.91/libs/main/KoMainWindow.cpp:416
#8  0x00007f95ec552d49 in KoMainWindow::~KoMainWindow (this=0x1961890, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>)
    at /usr/src/debug/koffice-2.1.91/libs/main/KoMainWindow.cpp:416
#9  0x00007f95e7c89d35 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#10 0x00007f95e8dba12f in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#11 0x00007f95e914f0ab in QMainWindow::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007f95e9d4c123 in KXmlGuiWindow::event (this=0x1961890, ev=0x1f1a030) at /usr/src/debug/kdelibs-4.4.2/kdeui/xmlgui/kxmlguiwindow.cpp:131
#13 0x00007f95e8d6fa0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f95e8d759db in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f95e9c4eda6 in KApplication::notify (this=0x7fffcbd8fcb0, receiver=0x1961890, event=0x1f1a030) at /usr/src/debug/kdelibs-4.4.2/kdeui/kernel/kapplication.cpp:302
#16 0x00007f95e7c7acdc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#17 0x00007f95e7c7ba27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#18 0x00007f95e7ca0ac3 in ?? () from /usr/lib64/libQtCore.so.4
#19 0x00007f95e2675d02 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x00007f95e2679ae8 in ?? () from /lib64/libglib-2.0.so.0
#21 0x00007f95e2679c9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x00007f95e7ca0603 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#23 0x00007f95e8e0e9de in ?? () from /usr/lib64/libQtGui.so.4
#24 0x00007f95e7c79722 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f95e7c799ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f95e7c7bcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#27 0x00007f95ec8100fd in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/koffice-2.1.91/kword/part/main.cpp:38
#28 0x00007f95e6dfcd2d in __libc_start_main () from /lib64/libc.so.6
#29 0x00000000004007d9 in _start ()

Possible duplicates by query: bug 172026.

Reported using DrKonqi
Comment 1 Rex Dieter 2010-05-03 16:50:07 UTC
Created attachment 43191 [details]
New crash information added by DrKonqi

Sorry, previous backtrace may be useless, was still inadvertantly using fedora's stock qt (and using vanilla -debuginfo).  Here's a better backtrace using matching vanilla (unpatched) qt + qt-debuginfo.
Comment 2 Rex Dieter 2010-05-03 16:57:50 UTC
Created attachment 43192 [details]
New crash information added by DrKonqi

Sorry, previous backtrace may be useless, was still inadvertantly using fedora's stock qt (and using vanilla -debuginfo).  Here's a better backtrace using matching vanilla (unpatched) qt + qt-debuginfo.
Comment 3 Rex Dieter 2010-05-03 16:57:50 UTC
Created attachment 43193 [details]
New crash information added by DrKonqi

Sorry, previous backtrace may be useless, was still inadvertantly using fedora's stock qt (and using vanilla -debuginfo).  Here's a better backtrace using matching vanilla (unpatched) qt + qt-debuginfo.
Comment 4 Rex Dieter 2010-05-03 17:09:12 UTC
oops, sorry, drkonqi had *claimed* sending the new backtrace had failed, so I resent it.
Comment 5 Thomas Zander 2010-05-09 20:56:13 UTC
lets merge

*** This bug has been marked as a duplicate of bug 235345 ***
Comment 6 Thomas Zander 2010-05-12 17:25:05 UTC
You say a vanilla Qt 4.6.2, can you confirm that that is the actual git tag or the actual released tarball and not the 4.6 branch?
Comment 7 Rex Dieter 2010-05-12 17:32:48 UTC
tarball