Bug 235626 - I had reviewed some attachment to a E-mail with Genview . After closing Gwenview and Kontact the crash happened
Summary: I had reviewed some attachment to a E-mail with Genview . After closing Gwenv...
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-28 14:28 UTC by Frans Leerink
Modified: 2010-06-07 01:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frans Leerink 2010-04-28 14:28:15 UTC
Application that crashed: kontact
Version of the application: 4.3.5
KDE Version: 4.3.5 (KDE 4.3.5) "release 0"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.2-desktop i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
Hello,

I had read in Kontact/Kmail a mail with attachments that where opened with Gwenview. After closing Gwenview I closed Kontact/kmail and that triggered the crash of Kontact.

Wlile I was entering this bug report I have restarted kontact/Kmail, reviewed the same mail with its attachments, closed Gwenview and kontact/kmail but bno new bugreport bwas tiggered

Regards,   Frans

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb3d5b920 (LWP 2793))]

Thread 2 (Thread 0xacc8cb70 (LWP 21869)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb4bd7d95 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb61d427c in pthread_cond_wait () from /lib/libc.so.6
#3  0xb6d2b750 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0xb493fa04 in QHostInfoAgent::run (this=0x8161748) at kernel/qhostinfo.cpp:260
#6  0xb6d2a623 in QThreadPrivate::start (arg=0x8161748) at thread/qthread_unix.cpp:188
#7  0xb4bd36e5 in start_thread () from /lib/libpthread.so.0
#8  0xb4bd3600 in ?? () from /lib/libpthread.so.0

Thread 1 (Thread 0xb3d5b920 (LWP 2793)):
[KCrash Handler]
#6  0xb6d6fa94 in size (this=<value optimized out>) at ../../src/corelib/tools/qstring.h:104
#7  QString::operator== (this=<value optimized out>) at tools/qstring.cpp:1912
#8  0xb583c34f in ?? () from /usr/lib/libkio.so.5
#9  0xb5838dff in ?? () from /usr/lib/libkio.so.5
#10 0xb583bfe4 in ?? () from /usr/lib/libkio.so.5
#11 0xb6e37864 in QMetaObject::activate (sender=0x8e4de88, from_signal_index=4, to_signal_index=4, argv=0xbfbf7f28) at kernel/qobject.cpp:3113
#12 0xb6e38585 in QMetaObject::activate (sender=0x8e4de88, m=0xb6f148b0, local_signal_index=0, argv=0xbfbf7f28) at kernel/qobject.cpp:3187
#13 0xb6e73585 in QSocketNotifier::activated (this=0x8e4de88, _t1=39) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#14 0xb6e3c3af in QSocketNotifier::event (this=0x8e4de88, e=0xbfbf82b4) at kernel/qsocketnotifier.cpp:316
#15 0xb64678fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb646f34e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb7364521 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#18 0xb6e2132e in QCoreApplication::notifyInternal (this=0xbfbf85b4, receiver=0x8e4de88, event=0xbfbf82b4) at kernel/qcoreapplication.cpp:610
#19 0xb6e4d3a8 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#20 socketNotifierSourceDispatch (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:110
#21 0xb476f4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb4772d98 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb4772ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb6e4d011 in QEventDispatcherGlib::processEvents (this=0x80541c0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#25 0xb650929a in ?? () from /usr/lib/libQtGui.so.4
#26 0xb6e1f98d in QEventLoop::processEvents (this=0xbfbf8514, flags=) at kernel/qeventloop.cpp:149
#27 0xb6e1fdd9 in QEventLoop::exec (this=0xbfbf8514, flags=...) at kernel/qeventloop.cpp:201
#28 0xb6e22270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0xb6467774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#30 0x0804b546 in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2010-06-07 01:09:00 UTC
Unfortunately, the backtrace is missing some important parts: 

#8  0xb583c34f in ?? () from /usr/lib/libkio.so.5
#9  0xb5838dff in ?? () from /usr/lib/libkio.so.5
#10 0xb583bfe4 in ?? () from /usr/lib/libkio.so.5

The missing details come from the kdelibs debug package, which wasn't installed when you first encountered this issue.

As this bug cannot be reproduced, I'll change its status.