Summary: | [patch] KMail imap hangs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aaron Lewis <aaron.lewis1989> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.kde.org/show_bug.cgi?id=77862 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kdepimlibs fix , kio_*
kmail patch Patch against kdepimlibs kipaddressinuse cpp implementation kipaddressinuse header kmail fixes log of KMail IMAP crash |
Description
Aaron Lewis
2010-08-29 13:15:44 UTC
Created attachment 245220 [details]
kdepimlibs fix , kio_*
Created attachment 245222 [details]
kmail patch
Could you attach only the patches themselves in non-compressed format? For KDE 4.5.0 users, a patch against kdepimlibs-4.5.0 will also be required. Created attachment 245285 [details]
Patch against kdepimlibs
Created attachment 245286 [details]
kipaddressinuse cpp implementation
Created attachment 245288 [details]
kipaddressinuse header
Created attachment 245290 [details, diff]
kmail fixes
Just for the record, please try kmail 4.4.6 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. 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
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) Problem went away when I rebuilt kdepimlibs, and kmail. I thought I had done that already, nevermind. 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) |