Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 335123 - [patch] KMail imap hangs
Summary: [patch] KMail imap hangs
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 13:15 UTC by Aaron Lewis
Modified: 2011-03-05 13:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
kdepimlibs fix , kio_* (kdepimlibs-4.4.5-r1.ebuilds.tar.bz2,8.74 KB, text/plain)
2010-08-29 13:16 UTC, Aaron Lewis
Details
kmail patch (kmail-4.4.5-r1.ebuilds.tar.bz2,1.85 KB, text/plain)
2010-08-29 13:16 UTC, Aaron Lewis
Details
Patch against kdepimlibs (kmail-mapjobdata.patch,23.83 KB, text/plain)
2010-08-30 00:46 UTC, Aaron Lewis
Details
kipaddressinuse cpp implementation (kipaddressinuse.cpp,1.88 KB, text/plain)
2010-08-30 00:46 UTC, Aaron Lewis
Details
kipaddressinuse header (kipaddressinuse.h,2.09 KB, text/plain)
2010-08-30 00:46 UTC, Aaron Lewis
Details
kmail fixes (kmail-obj.patch,338 bytes, patch)
2010-08-30 00:47 UTC, Aaron Lewis
Details | Diff
log of KMail IMAP crash (kmail-error.log,7.34 KB, text/plain)
2010-12-20 23:13 UTC, Dillon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Lewis 2010-08-29 13:15:44 UTC
For details about this bug:
 see https://bugs.kde.org/show_bug.cgi?id=77862

And i've tested these patches , works.

Best way to test: get online , get kmail run , get offline , and if you get online again , try reading some mails , you'll found it never works until kio_imap restarted ( also kmail )

ebuilds , patches are attached.

Reproducible: Always

Steps to Reproduce:
1.emerge kmail
2.
3.
Comment 1 Aaron Lewis 2010-08-29 13:16:17 UTC
Created attachment 245220 [details]
kdepimlibs fix , kio_*
Comment 2 Aaron Lewis 2010-08-29 13:16:44 UTC
Created attachment 245222 [details]
kmail patch
Comment 3 Tomáš Chvátal (RETIRED) gentoo-dev 2010-08-29 14:10:55 UTC
Could you attach only the patches themselves in non-compressed format?
Comment 4 Theo Chatzimichos (RETIRED) archtester gentoo-dev Security 2010-08-29 16:12:31 UTC
For KDE 4.5.0 users, a patch against kdepimlibs-4.5.0 will also be required.
Comment 5 Aaron Lewis 2010-08-30 00:46:01 UTC
Created attachment 245285 [details]
Patch against kdepimlibs
Comment 6 Aaron Lewis 2010-08-30 00:46:27 UTC
Created attachment 245286 [details]
kipaddressinuse cpp implementation
Comment 7 Aaron Lewis 2010-08-30 00:46:42 UTC
Created attachment 245288 [details]
kipaddressinuse header
Comment 8 Aaron Lewis 2010-08-30 00:47:04 UTC
Created attachment 245290 [details, diff]
kmail fixes
Comment 9 Maciej Mrozowski gentoo-dev 2010-09-12 03:59:31 UTC
Just for the record, please try kmail 4.4.6
Comment 10 Aaron Lewis 2010-09-13 04:33:20 UTC
Anyway , this bug is kdepimlibs related bugs , upgraded to kdepim 4.4.6 , kde 4.5.1 , kmail 4.4.6 , bug was not fixed.
Comment 11 Dillon 2010-12-20 23:13:04 UTC
Created attachment 257642 [details]
log of KMail IMAP crash

I get this error message as well, but kio_imap4 dies too fast to attach gdb.
I tried the patches and they did not work for me, and I'm using hardened.

grsec: Segmentation fault occurred at (nil) in /usr/bin/kdeinit4[kio_imap4:6597] uid/euid:1000/1000 gid/egid:1022/1022, parent /usr/bin/kdeinit4[kdeinit4:17603] uid/euid:1000/1000 gid/egid:1022/1022
Comment 12 Dillon 2010-12-21 02:12:31 UTC
Edit: I neglected to mention that I am running the listed kdepimlibs ebuild and the kmail ebuild bumped to the current x86 stable version (4.4.7)
Comment 13 Dillon 2010-12-26 22:18:08 UTC
Problem went away when I rebuilt kdepimlibs, and kmail. I thought I had done that already, nevermind.
Comment 14 Theo Chatzimichos (RETIRED) archtester gentoo-dev Security 2011-03-05 13:14:36 UTC
based on the comments in kde's bug i'll have to close it, it needs some sort of upstream decision. I really hope it will be fixed for 4.6 (I'm CC'ed on the upstream bug)