Bug 306073 - Kmail fails to retrieve Yahoo Mail via POP3 them crashes
Summary: Kmail fails to retrieve Yahoo Mail via POP3 them crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: POP3 Resource (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
: 325633 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-08-31 11:03 UTC by Alexis Kauffmann
Modified: 2018-09-28 02:21 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.28 KB, text/plain)
2013-01-12 09:51 UTC, prjolivet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexis Kauffmann 2012-08-31 11:03:32 UTC
Application: akonadi_pop3_resource (4.8)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-29-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: I was downloading email from Yahoo (pop.mail.yahoo.com) when Kmail sent a system message that said something to the likes of "Sorry, your POP account does not support the UDL command so the 'leave messages on server' function will not work". Following this message, Kmail crashed.

-- Backtrace:
Application: Alexei (Yahoo) do tipo Servidor de e-mails POP3 (akonadi_pop3_resource), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  setCurrentJob (job=0x1d51450, this=0x0) at ../../../resources/pop3/jobs.cpp:72
#7  SlaveBaseJob::SlaveBaseJob (this=0x1d51450, POPSession=0x0) at ../../../resources/pop3/jobs.cpp:200
#8  0x0000000000425369 in FetchJob::FetchJob (this=0x1d51450, session=<optimized out>) at ../../../resources/pop3/jobs.cpp:457
#9  0x000000000041225a in POP3Resource::doStateStep (this=0x1884d70) at ../../../resources/pop3/pop3resource.cpp:353
#10 0x00000000004158bb in advanceState (nextState=POP3Resource::Download, this=0x1884d70) at ../../../resources/pop3/pop3resource.cpp:221
#11 POP3Resource::uidListJobResult (this=0x1884d70, job=<optimized out>) at ../../../resources/pop3/pop3resource.cpp:568
#12 0x000000000040d1a4 in POP3Resource::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at moc_pop3resource.cpp:104
#13 0x00007f111de01281 in QMetaObject::activate (sender=0x1e0b0e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff26c3d990) at kernel/qobject.cpp:3547
#14 0x00007f111c982182 in KJob::result (this=<optimized out>, _t1=0x1e0b0e0) at ./kjob.moc:208
#15 0x00007f111c9821c0 in KJob::emitResult (this=0x1e0b0e0) at ../../kdecore/jobs/kjob.cpp:318
#16 0x0000000000424ca2 in SlaveBaseJob::slotSlaveResult (this=0x1e0b0e0, job=0x1e0af50) at ../../../resources/pop3/jobs.cpp:225
#17 0x00007f111de01281 in QMetaObject::activate (sender=0x1e0af50, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff26c3db20) at kernel/qobject.cpp:3547
#18 0x00007f111c982182 in KJob::result (this=<optimized out>, _t1=0x1e0af50) at ./kjob.moc:208
#19 0x00007f111c9821c0 in KJob::emitResult (this=0x1e0af50) at ../../kdecore/jobs/kjob.cpp:318
#20 0x00007f111c485c64 in KIO::SimpleJob::slotFinished (this=0x1e0af50) at ../../kio/kio/job.cpp:494
#21 0x00007f111c48d7ed in KIO::TransferJob::slotFinished (this=0x1e0af50) at ../../kio/kio/job.cpp:1081
#22 0x00007f111de01281 in QMetaObject::activate (sender=0x191f630, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#23 0x00007f111c534251 in KIO::SlaveInterface::dispatch (this=<optimized out>, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:172
#24 0x00007f111c530fa5 in KIO::SlaveInterface::dispatch (this=0x191f630) at ../../kio/kio/slaveinterface.cpp:88
#25 0x00007f111c52422e in KIO::Slave::gotInput (this=0x191f630) at ../../kio/kio/slave.cpp:344
#26 0x00007f111de01281 in QMetaObject::activate (sender=0x18c8e10, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#27 0x00007f111c4565e7 in dequeue (this=<optimized out>) at ../../kio/kio/connection.cpp:82
#28 KIO::ConnectionPrivate::dequeue (this=0x1e473f0) at ../../kio/kio/connection.cpp:71
#29 0x00007f111de06446 in QObject::event (this=0x18c8e10, e=<optimized out>) at kernel/qobject.cpp:1195
#30 0x00007f111d16f894 in notify_helper (e=0x1e76020, receiver=0x18c8e10, this=0x16ddda0) at kernel/qapplication.cpp:4559
#31 QApplicationPrivate::notify_helper (this=0x16ddda0, receiver=0x18c8e10, e=0x1e76020) at kernel/qapplication.cpp:4531
#32 0x00007f111d174713 in QApplication::notify (this=0x7fff26c3ed80, receiver=0x18c8e10, e=0x1e76020) at kernel/qapplication.cpp:4420
#33 0x00007f111ba7e9e6 in KApplication::notify (this=0x7fff26c3ed80, receiver=0x18c8e10, event=0x1e76020) at ../../kdeui/kernel/kapplication.cpp:311
#34 0x00007f111ddece9c in QCoreApplication::notifyInternal (this=0x7fff26c3ed80, receiver=0x18c8e10, event=0x1e76020) at kernel/qcoreapplication.cpp:876
#35 0x00007f111ddf0c6a in sendEvent (event=0x1e76020, receiver=0x18c8e10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x16b5f10) at kernel/qcoreapplication.cpp:1500
#37 0x00007f111de1bf93 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#38 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#39 0x00007f11199ead53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#40 0x00007f11199eb0a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#41 0x00007f11199eb164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#42 0x00007f111de1c3bf in QEventDispatcherGlib::processEvents (this=0x16b73d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#43 0x00007f111d217d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#44 0x00007f111ddebc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#45 0x00007f111ddebed7 in QEventLoop::exec (this=0x7fff26c3ed00, flags=...) at kernel/qeventloop.cpp:204
#46 0x00007f111ddf0f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#47 0x00007f111e4e4326 in Akonadi::ResourceBase::init (r=0x1884d70) at ../../akonadi/resourcebase.cpp:412
#48 0x0000000000419956 in Akonadi::ResourceBase::init<POP3Resource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/KDE/Akonadi/../../akonadi/resourcebase.h:188
#49 0x00007f111af9576d in __libc_start_main (main=0x40c6b0 <main(int, char**)>, argc=3, ubp_av=0x7fff26c3ee98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff26c3ee88) at libc-start.c:226
#50 0x000000000040c775 in _start ()

Reported using DrKonqi
Comment 1 prjolivet 2013-01-12 09:51:12 UTC
Created attachment 76412 [details]
New crash information added by DrKonqi

kmail (1.13.7) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2

- What I was doing when the application crashed:
I was only retrieving email from Yahoo IMAP imap.mail.yahoo.com, after most of the email were downloaded (reported as 100%) Kmail continued to check email then frozed and then crashed

- Custom settings of the application:

-- Backtrace (Reduced):
#13 0x00007f23dc6d69d2 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5
#14 0x00007f23dc6d6a10 in KJob::emitResult() () from /usr/lib/libkdecore.so.5
#15 0x00007f23d73a3475 in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5
#16 0x00007f23d73aa892 in KIO::TransferJob::slotFinished() () from /usr/lib/libkio.so.5
#17 0x00007f23d73a35e6 in KIO::SimpleJob::slotError(int, QString const&) () from /usr/lib/libkio.so.5
Comment 2 Allen Winter 2013-01-13 16:54:27 UTC
prjolivet@yahoo.fr your report is invalid since we don't maintain kmail 1 any longer.

Alexis, KMail 4.8.4 is getting old now.  Is this still happening for you with newer versions?
Comment 3 prjolivet 2013-01-13 17:11:04 UTC
Thank you for your feedback.
Yes it happened to me on KMail 4.8.4 last week.

----
De : 
Allen Winter <winter@kde.org>
  À : 
prjolivet@yahoo.fr
  Date : 
Aujourd'hui 17:54:27
   
https://bugs.kde.org/show_bug.cgi?id=306073

Allen Winter <winter@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |winter@kde.org

--- Comment #2 from Allen Winter <winter@kde.org> ---
prjolivet@yahoo.fr your report is invalid since we don't maintain kmail 1 any
longer.

Alexis, KMail 4.8.4 is getting old now.  Is this still happening for you with
newer versions?
Comment 4 Jekyll Wu 2013-10-04 20:39:28 UTC
*** Bug 325633 has been marked as a duplicate of this bug. ***
Comment 5 Albert Astals Cid 2016-03-29 22:25:19 UTC
Can you still reproduce this crash in newer versions of akonadi/kdepim? Specially the ones based in KDE Frameworks 5?
Comment 6 Andrew Crouthamel 2018-09-26 22:10:39 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 set the bug status 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 7 prjolivet 2018-09-27 03:54:19 UTC
I'm not using KDE since many years now and have switched to GNOME so I can't tell if it's working again or not in KMail sorry.
Comment 8 prjolivet 2018-09-27 03:55:41 UTC
Marked as Reported as I given a feedback (even if it's not really usually)
Comment 9 Albert Astals Cid 2018-09-27 22:45:41 UTC
Yeaaaaah, no.
Comment 10 Andrew Crouthamel 2018-09-28 02:21:39 UTC
Thanks for the update!