Bug 117582

Summary: kmail crashes viewing imap folders when you delete a message and then try to move to the next message
Product: [Unmaintained] kmail Reporter: David Sharp <kde>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description David Sharp 2005-12-03 12:58:22 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs
OS:                Linux

Suse 10.0 (kernel 2.6.13-15-default), if/when you delete a message then immediatly try to move to the next message Kmail/Kontact crashes.

Partly a user created issue as there is no need to do this in kmail (used to Outlook which just marks the messages as deleted and doesn't remove them, then you have to move to the next message) but it still shouldn't produce a crash.

100% reproducable *but* as it has to be quick and I'm not always quick enough IYSWIM, can always manage to do it but not always the first time.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1104205760 (LWP 8747)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x00000014 in ?? ()
#5  0x424653e0 in KMMsgBase::transferInProgress ()
   from /opt/kde3/lib/libkmailprivate.so
#6  0x4261050a in KMail::ImapJob::slotGetBodyStructureResult ()
   from /opt/kde3/lib/libkmailprivate.so
#7  0x4261264a in KMail::ImapJob::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#8  0x40f7e159 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x40622702 in KIO::Job::result () from /opt/kde3/lib/libkio.so.4
#10 0x40675af2 in KIO::Job::emitResult () from /opt/kde3/lib/libkio.so.4
#11 0x40675c5e in KIO::SimpleJob::slotFinished ()
   from /opt/kde3/lib/libkio.so.4
#12 0x4067639d in KIO::TransferJob::slotFinished ()
   from /opt/kde3/lib/libkio.so.4
#13 0x406779ca in KIO::TransferJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#14 0x40f7e159 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40f7e600 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x4061d59c in KIO::SlaveInterface::finished ()
   from /opt/kde3/lib/libkio.so.4
#17 0x4068fddc in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#18 0x406358c7 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#19 0x4063a0eb in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4
#20 0x4063a29b in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4
#21 0x40f7e159 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40f7e731 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x412bf700 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40f9d430 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40f1e9f1 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x40f1f369 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x40c3097e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#28 0x40f1283d in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40eccde3 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x40f35903 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x40f357e6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x40f1e33f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x0805a1bb in ?? ()
#34 0xbfa6b040 in ?? ()
#35 0x00000001 in ?? ()
#36 0x00000001 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000001 in ?? ()
#40 0x08066cd8 in typeinfo name for QPtrList<KAction> ()
#41 0x00000000 in ?? ()
#42 0x08066320 in typeinfo name for QPtrList<KAction> ()
#43 0x0806630c in typeinfo name for QPtrList<KAction> ()
#44 0x00000021 in ?? ()
#45 0x415ed8b0 in main_arena () from /lib/tls/libc.so.6
#46 0x00000004 in ?? ()
#47 0x00000020 in ?? ()
#48 0x41535241 in _int_malloc () from /lib/tls/libc.so.6
#49 0x414e5ea0 in __libc_start_main () from /lib/tls/libc.so.6
#50 0x08057991 in ?? ()
Comment 1 Thiago Macieira 2005-12-03 16:11:15 UTC

*** This bug has been marked as a duplicate of 107914 ***
Comment 2 Carsten Burghardt 2005-12-04 19:19:08 UTC
Am Saturday 03 December 2005 12:58 schrieb David Sharp:
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/libthread_db.so.1".


Just to be sure: can you please compile kmail with debug symbols and paste the 
backtrace? I can't reproduce this here.
Comment 3 David Sharp 2005-12-05 19:35:27 UTC
On Sunday 04 December 2005 18:19, Carsten Burghardt wrote:
<snip>
> Am Saturday 03 December 2005 12:58 schrieb David Sharp:
> > (no debugging symbols found)
> > Using host libthread_db library "/lib/tls/libthread_db.so.1".
>
> Just to be sure: can you please compile kmail with debug symbols and paste
> the backtrace? I can't reproduce this here.


Short answer: no
Medium answer: No but I also can't reproduce in 3.5.0-7
Long answer: Tried recompiling and realised I was missing shed loads of 
dependencies, inc gcc[1] ;-)

One big list of packages later and kdepim3 still failed to build, realised 
that I was trying to build 3.5.0 and tried installing the kdepim3-3.5.0-7 rpm 
first and I can't manage to get 3.5.0 to crash.

Regards

David

[1] I'm running on a laptop and not done _any_ compiling on here before.