Version: (using KDE 4.2.0) Installed from: Ubuntu Packages When using kmail, the kio_imap4 process dies frequently. with SIGABRT. .xsession-errors tells: ASSERT: "i >= 0 && i < size()" in file /usr/include/qt4/QtCore/qbytearray.h, line 379 kioslave: ####### CRASH ###### protocol = imap pid = 13869 signal = 6 It seems it only occurs when automatically cheching for new mail (set it to 5mins), however that's not for sure. I'm running a Zarafa IMAP server. Other applications (Squirrelmail) run quite well with that server. Two different backtraces: (gdb) bt #0 0xb7f23430 in __kernel_vsyscall () #1 0xb66438a0 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb6645268 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7d13795 in qt_message_output () from /usr/lib/libQtCore.so.4 #4 0xb7d13872 in qFatal () from /usr/lib/libQtCore.so.4 #5 0xb7d13915 in qt_assert () from /usr/lib/libQtCore.so.4 #6 0xb5f175c8 in imapParser::parseFetch (this=0x950b578, inWords=@0xbfa24990) at /usr/include/qt4/QtCore/qbytearray.h:379 #7 0xb5f19772 in imapParser::parseUntagged (this=0x950b578, result=@0xbfa24990) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imapparser.cpp:497 #8 0xb5f19ca7 in imapParser::parseLoop (this=0x950b578) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imapparser.cpp:1753 #9 0xb5f04428 in IMAP4Protocol::get (this=0x950b560, _url=@0xbfa24d0c) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imap4.cpp:345 #10 0xb7881c74 in KIO::SlaveBase::dispatch (this=0x950b560, command=67, data=@0xbfa24de0) at /build/buildd/kde4libs-4.2.0/kio/kio/slavebase.cpp:1035 #11 0xb5ef4d0e in IMAP4Protocol::dispatch (this=0x950b560, command=67, data=@0xbfa24de0) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imap4.cpp:1836 #12 0xb788029c in KIO::SlaveBase::dispatchLoop (this=0x950b560) at /build/buildd/kde4libs-4.2.0/kio/kio/slavebase.cpp:282 #13 0xb5ef4500 in kdemain (argc=4, argv=0x94ee028) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imap4.cpp:136 #14 0x0804dec1 in launch (argc=4, _name=0x94edbac "kio_imap4", args=0x94edc2a "", cwd=0x0, envc=0, envs=0x94edc2f "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050e73 "0") ---Type <return> to continue, or q <return> to quit--- at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:690 #15 0x0804e6cd in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:1270 #16 0x0804ec1a in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:1463 #17 0x0804f86c in main (argc=2, argv=0xbfa25514, envp=0xbfa25520) at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:1939 (gdb) x 0xbfa24990 0xbfa24990: "" (gdb) x/1xw 0xbfa24990 0xbfa24990: 0x095afa00 (gdb) x/s 0x095afa00 0x95afa00: "\001" (gdb) x/20s 0x095afa00 0x95afa00: "\001" 0x95afa02: "" 0x95afa03: "" 0x95afa04: "d" 0x95afa06: "" 0x95afa07: "" 0x95afa08: "b" 0x95afa0a: "" 0x95afa0b: "" 0x95afa0c: "\020�Z\t* 8109 FETCH (UID 34352 RFC822.SIZE 11244 FLAGS (\\Seen) NIL BODY[HEADER.FIELDS (REFERENCES)] NIL)" 0x95afa73: "\n" 0x95afa75: "" 0x95afa76: " " 0x95afa78: "`" 0x95afa7a: "" 0x95afa7b: "" 0x95afa7c: "\237" 0x95afa7e: "" 0x95afa7f: "" 0x95afa80: "\210" (gdb) Program received signal SIGABRT, Aborted. [Switching to Thread 0xb60799b0 (LWP 25012)] 0xb7f23430 in __kernel_vsyscall () (gdb) bt #0 0xb7f23430 in __kernel_vsyscall () #1 0xb66438a0 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb6645268 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7d13795 in qt_message_output () from /usr/lib/libQtCore.so.4 #4 0xb7d13872 in qFatal () from /usr/lib/libQtCore.so.4 #5 0xb7d13915 in qt_assert () from /usr/lib/libQtCore.so.4 #6 0xb5f175c8 in imapParser::parseFetch (this=0x950b500, inWords=@0xbfa24990) at /usr/include/qt4/QtCore/qbytearray.h:379 #7 0xb5f19772 in imapParser::parseUntagged (this=0x950b500, result=@0xbfa24990) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imapparser.cpp:497 #8 0xb5f19ca7 in imapParser::parseLoop (this=0x950b500) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imapparser.cpp:1753 #9 0xb5f04428 in IMAP4Protocol::get (this=0x950b4e8, _url=@0xbfa24d0c) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imap4.cpp:345 #10 0xb7881c74 in KIO::SlaveBase::dispatch (this=0x950b4e8, command=67, data=@0xbfa24de0) at /build/buildd/kde4libs-4.2.0/kio/kio/slavebase.cpp:1035 #11 0xb5ef4d0e in IMAP4Protocol::dispatch (this=0x950b4e8, command=67, data=@0xbfa24de0) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imap4.cpp:1836 #12 0xb788029c in KIO::SlaveBase::dispatchLoop (this=0x950b4e8) at /build/buildd/kde4libs-4.2.0/kio/kio/slavebase.cpp:282 #13 0xb5ef4500 in kdemain (argc=4, argv=0x94ee138) at /build/buildd/kdepimlibs-4.2.0/kioslave/imap4/imap4.cpp:136 #14 0x0804dec1 in launch (argc=4, _name=0x94edbac "kio_imap4", args=0x94edc2a "", cwd=0x0, envc=0, envs=0x94edc2f "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050e73 "0") at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:690 #15 0x0804e6cd in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:1270 #16 0x0804ec1a in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:1463 #17 0x0804f86c in main (argc=2, argv=0xbfa25514, envp=0xbfa25520) at /build/buildd/kde4libs-4.2.0/kinit/kinit.cpp:1939 (gdb) x 0xbfa24990 0xbfa24990: 0x09524c98 (gdb) x/20s 0x9524c98 0x9524c98: "\001" 0x9524c9a: "" 0x9524c9b: "" 0x9524c9c: "c" 0x9524c9e: "" 0x9524c9f: "" 0x9524ca0: "a" 0x9524ca2: "" 0x9524ca3: "" 0x9524ca4: "�LR\t* 12 FETCH (UID 34312 RFC822.SIZE 117527 FLAGS (\\Seen) NIL BODY[HEADER.FIELDS (REFERENCES)] NIL)" 0x9524d0a: "\n" 0x9524d0c: "=" 0x9524d0e: " �\"" 0x9524d12: "\"" 0x9524d14: " " 0x9524d16: "" 0x9524d17: "" 0x9524d18: "\210" 0x9524d1a: "" 0x9524d1b: "\f\031" (gdb)
@busquad, mailtransport component is for outgoing mail, imap is incoming. Maybe kio_imap component somewhere? If not, kmail as it is the only user of that kio.
Reassigning as requested by Tom Albers.
This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
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!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!