Bug 192858

Summary: Kmail crashed when exiting
Product: [Applications] kmail Reporter: Daniel Duncan <xdan779>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: christophe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:

Description Daniel Duncan 2009-05-16 11:12:59 UTC
Application that crashed: kmail
Version of the application: 1.11.90
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.28.5 x86_64

What I was doing when the application crashed:
Sadly nothing sticks out from normal use, I had kmail open I selected file -> quit and I was presented with this crash dialog

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f9edf43d8a0 in QListData::shared_null () from /opt/qt-4.5/lib/libQtCore.so.4
#6  0x00007f9edfa9d832 in qDeleteAll<QList<KIO::Slave*>::const_iterator> () from /opt/lib/libkio.so.5
#7  0x00007f9edfa9e2d6 in qDeleteAll<QHash<QString, KIO::SchedulerPrivate::ProtocolInfo*>::const_iterator> () from /opt/lib/libkio.so.5
#8  0x00007f9edfa9a349 in ._257::destroy () from /opt/lib/libkio.so.5
#9  0x00007f9edd313f80 in exit () from /lib64/libc.so.6
#10 0x00007f9edd2fd16b in __libc_start_main () from /lib64/libc.so.6
#11 0x00000000004023c9 in _start ()
Comment 1 Dario Andres 2009-05-25 16:49:36 UTC
*** Bug 193992 has been marked as a duplicate of this bug. ***
Comment 2 Christophe Marin 2009-07-06 17:35:12 UTC
You're the only one with this backtrace until now. Do you still experience this crash with eg. 4.3RC1 ? If so, what is your distribution ? are you using packages ? sources ?
Comment 3 Daniel Duncan 2009-07-08 11:19:57 UTC
I have not experienced this in recent builds, it can probably be safely closed.
Comment 4 Christophe Marin 2009-07-08 11:45:33 UTC
Thank you for your feedback. Closing with 'worksforme'
Comment 5 Christophe Marin 2009-07-09 12:12:36 UTC
ok, I change my mind, there are duplicate reports.

*** This bug has been marked as a duplicate of bug 199375 ***