[Bug 227004] New: Kontact crashes after saving an attachment

[Stephan Kleine]

https://bugs.kde.org/show_bug.cgi?id=227004

           Summary: Kontact crashes after saving an attachment
           Product: kontact
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: bitdealer at gmail.com


Application: kontact (4.4)
KDE Platform Version: 4.4.00 (KDE 4.4.0) "release 223"
Qt Version: 4.6.1
Operating System: Linux 2.6.31.12-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

-- Information about the crash:
The attachment is a .txt file. I click on it, select the place where to save it
and click the save button and then Kontact crashes. The attachment is correctly
saved to disk though.

The crash can be reproduced every time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  detach (this=<value optimized out>) at /usr/include/QtCore/qlist.h:122
#6  begin (this=<value optimized out>) at /usr/include/QtCore/qlist.h:248
#7  KDirWatchPrivate::Entry::removeClient (this=<value optimized out>) at
/usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:456
#8  0x00007fbdf044b007 in KDirWatchPrivate::removeEntry (this=0x1469bc0,
instance=0x0, e=0x0, sub_entry=0x0) at
/usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:890
#9  0x00007fbdf044b3ae in KDirWatchPrivate::slotRemoveDelayed (this=0x1469bc0)
at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:1313
#10 0x00007fbdf0466f3c in KDirWatchPrivate::qt_metacall (this=0x1469bc0,
_c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffa87731c0)
    at /usr/src/debug/kdelibs-4.4.0/build/kio/kdirwatch_p.moc:84
#11 0x00007fbdf2b6fbff in QMetaObject::activate (sender=0x108ddb0, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x0) at
kernel/qobject.cpp:3275
#12 0x00007fbdf2b7735f in QSingleShotTimer::timerEvent (this=0x108ddb0) at
kernel/qtimer.cpp:308
#13 0x00007fbdf2b6c853 in QObject::event (this=0x108ddb0, e=0x7fffa8773960) at
kernel/qobject.cpp:1212
#14 0x00007fbdf1f1bc9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQtGui.so.4
#15 0x00007fbdf1f2227b in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#16 0x00007fbdf34ba456 in KApplication::notify (this=0x7fffa8773d70,
receiver=0x108ddb0, event=0x7fffa8773960) at
/usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302
#17 0x00007fbdf2b5cdfc in QCoreApplication::notifyInternal
(this=0x7fffa8773d70, receiver=0x108ddb0, event=0x7fffa8773960) at
kernel/qcoreapplication.cpp:704
#18 0x00007fbdf2b89ac5 in sendEvent (event=<value optimized out>,
receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (event=<value optimized out>,
receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#20 0x00007fbdf2b86634 in timerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:184
#21 0x00007fbdea376dee in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#22 0x00007fbdea37a7b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fbdea37a8e0 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#24 0x00007fbdf2b86323 in QEventDispatcherGlib::processEvents (this=0x613810,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007fbdf1fc9dce in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007fbdf2b5b712 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007fbdf2b5baec in QEventLoop::exec (this=0x7fffa8773cb0, flags=) at
kernel/qeventloop.cpp:201
#28 0x00007fbdf2b5f83b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:981
#29 0x0000000000403ede in _start ()

Possible duplicates by query: bug 226788, bug 226608.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.