Bug 181564

Summary: Crash on system shutdown
Product: [Applications] kdepimlibs Reporter: Geoff Madden <mgmadden>
Component: mailtransportAssignee: Tom Albers <toma>
Status: RESOLVED WORKSFORME    
Severity: normal CC: andresbajotierra, kdepim-bugs
Priority: NOR Keywords: investigated, triaged
Version: 4.1   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Geoff Madden 2009-01-22 07:11:53 UTC 
Version:           kde-4.1.2 (using KDE 4.1.2)
Compiler:          gcc-4.1.3 
OS:                Linux
Installed from:    Compiled From Sources

 Application: KMail (kmail), signal SIGSEGV
0x00007f993c4ebd90 in nanosleep () from /lib64/libc.so.6

Thread 1 (Thread 0x7f9948ea8750 (LWP 13718)):
[KCrash Handler]
#5  0x00007f994756e923 in KCompositeJobPrivate::~KCompositeJobPrivate () from /usr/kde/4.1/lib64/libkdecore.so.5
#6  0x00007f994756f6ad in KJob::~KJob () from /usr/kde/4.1/lib64/libkdecore.so.5
#7  0x00007f994572c19e in MailTransport::SmtpJob::~SmtpJob () from /usr/kde/4.1/lib64/libmailtransport.so.4
#8  0x00007f9948a132d8 in QObjectPrivate::deleteChildren () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007f9948a1be9f in QObject::~QObject () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007f9945728963 in ?? () from /usr/kde/4.1/lib64/libmailtransport.so.4
#11 0x00007f9948a06285 in qt_call_post_routines () from /usr/lib64/qt4/libQtCore.so.4
#12 0x00007f993eae2ed8 in QApplication::~QApplication () from /usr/lib64/qt4/libQtGui.so.4
#13 0x00000000004032e7 in _start ()
Comment 1 Dario Andres 2009-01-22 09:49:12 UTC 
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Dario Andres 2009-03-25 19:28:09 UTC 
No response. Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:36:29 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Geoff Madden 2018-09-19 07:47:53 UTC 
(In reply to Andrew Crouthamel from comment #3)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least 15 days.
> Please provide the requested information as soon as possible and set the bug
> status as REPORTED. Due to regular bug tracker maintenance, if the bug is
> still in NEEDSINFO status with no change in 30 days the bug will be closed
> as RESOLVED > WORKSFORME due to lack of needed information.
> 
> For more information about our bug triaging procedures please read the wiki
> located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> If you have already provided the requested information, please mark the bug
> as REPORTED so that the KDE team knows that the bug is ready to be confirmed.
> 
> Thank you for helping us make KDE software even better for everyone!

Considering the time of this original report,I would suggest that it be closed,as a world of upgrades have been completed since,also the problem is not evident in the latest versions .
Comment 5 Andrew Crouthamel 2018-09-19 15:43:21 UTC 
Thanks for the update.

Thank you for helping us make KDE software even better for everyone!