[kmail2] [Bug 405681] New: The mail content is not displayed
https://bugs.kde.org/show_bug.cgi?id=405681 Bug ID: 405681 Summary: The mail content is not displayed Product: kmail2 Version: 5.10.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tournie...@gmail.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I launch kmail and want to display one content of a mail. The content never appears. Thanks. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd1989d0bc0 (LWP 6368))] Thread 25 (Thread 0x7fd0cd22a700 (LWP 6425)): #0 0x7fd18b1cc9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fd17b6e3fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fd17b6e3f68, cond=0x7fd17b6e3f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fd17b6e3f90, mutex=0x7fd17b6e3f68) at pthread_cond_wait.c:655 #3 0x7fd17b3ed844 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fd17b3ed889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fd18b1c66db in start_thread (arg=0x7fd0cd22a700) at pthread_create.c:463 #6 0x7fd195a1a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fd0cda2b700 (LWP 6423)): #0 0x7fd18b1cced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fd0cda2a710, expected=0, futex_word=0x7fd0cda2a8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fd0cda2a7b0, mutex=0x7fd0cda2a8a8, cond=0x7fd0cda2a8d0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fd0cda2a8d0, mutex=0x7fd0cda2a8a8, abstime=0x7fd0cda2a7b0) at pthread_cond_wait.c:667 #3 0x7fd18012b177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fd18012bada in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fd18012bbc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fd1800e9851 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fd1800ec387 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fd1800ec974 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fd18012dcd1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fd18b1c66db in start_thread (arg=0x7fd0cda2b700) at pthread_create.c:463 #11 0x7fd195a1a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fd0c700 (LWP 6420)): #0 0x7fd18b1cced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fd0cfffe710, expected=0, futex_word=0x7fd0cfffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fd0cfffe7b0, mutex=0x7fd0cfffe8a8, cond=0x7fd0cfffe8d0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fd0cfffe8d0, mutex=0x7fd0cfffe8a8, abstime=0x7fd0cfffe7b0) at pthread_cond_wait.c:667 #3 0x7fd18012b177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fd18012bada in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fd18012bbc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fd1800e9851 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fd1800ec387 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fd1800ec974 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fd18012dcd1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fd18b1c66db in start_thread (arg=0x7fd0c700) at pthread_create.c:463 #11 0x7fd195a1a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fd0e8ba6700 (LWP 6419)): #0 0x7fd18b1cced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fd0e8ba5710, expected=0, futex_word=0x7fd0e8ba58f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fd0e8ba57b0, mutex=0x7fd0e8ba58a8, cond=0x7fd0e8ba58d0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fd0e8ba58d0, mutex=0x7fd0e8ba58a8, abstime=0x7fd0e8ba57b0) at pthread_cond_wait.c:667 #3 0x7fd18012b177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fd18012bada in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5
[Akonadi] [Bug 394071] New: Kmail crash after searching message
https://bugs.kde.org/show_bug.cgi?id=394071 Bug ID: 394071 Summary: Kmail crash after searching message Product: Akonadi Version: 5.8.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: tournie...@gmail.com Target Milestone: --- Created attachment 112558 --> https://bugs.kde.org/attachment.cgi?id=112558=edit This is the crash report generated by akonadiserver. I selected "find a message" in the kmail tool menu. I filled the popup window, typed search. Then kmail asked me either to re-index the directory (during all the tests I have done in order to reproduce the crash, kmail always asked me to re-index, even I did it before) or to continue. Kmail crashed for the both choices. The message I received (in french): "Le service de gestion des informations personnelles n'est pas opérationnel. Il est impossible d'utiliser cette application sans ce service." Best regards, -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 312025] unnecessary HTML code is added to e-mail
https://bugs.kde.org/show_bug.cgi?id=312025 al...@topaze.homeip.net changed: What|Removed |Added CC||al...@topaze.homeip.net -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 240981] Crash of akonadi on login
https://bugs.kde.org/show_bug.cgi?id=240981 Alain Trocmé alain.tro...@gmail.com changed: What|Removed |Added CC||alain.tro...@gmail.com -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259987] New: KMail told to accept self-signed certificates forever but keep asking for them at each startup
https://bugs.kde.org/show_bug.cgi?id=259987 Summary: KMail told to accept self-signed certificates forever but keep asking for them at each startup Product: kmail Version: 1.13.5 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: alain.per...@gmail.com Version: 1.13.5 (using KDE 4.5.85) OS:Linux I have a mail server on my LAN running Dovecot IMAP with TLS and self-signed certificates. I told KMail to accept these certificates forever, but it keeps asking me to check them each time it is started. This is really annoying as I have ~ 10 accounts on this mail server (most of them dedicated to a mailing list). Reproducible: Always Steps to Reproduce: 1. Configure an account that use a self-signed certificate. 2. On first connection, tell KMail to accept the certificate forever. 3. Exit KMail. 4. Start KMail again. Actual Results: KMail will complain about the self-signed certificate again. Expected Results: KMail should not complain about the previously accepted self-signed certificate. I am running Kubuntu 11.04 Natty AMD64 with KDE 4.5.85 (4.6 Beta2) and KMail 1.13.5. There wasn't such an issue when I was running Kubuntu 10.10 Maverick AMD64 with KDE 4.5.1 with whatever version of KMail was packaged there. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 245790] kmail crashed after adding a new subfolder and copying a mail into it. (IMAP disconnected)
https://bugs.kde.org/show_bug.cgi?id=245790 --- Comment #1 from Alain BAECKEROOT alain baeckeroot laposte net 2010-07-26 15:35:03 --- After restart, it worked and the mail was in the correct folder. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 236824] New: Where are the Categories
https://bugs.kde.org/show_bug.cgi?id=236824 Summary: Where are the Categories Product: kaddressbook Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@kde.lka.org.lu CC: to...@kde.org Version: 4.4.2 (using 4.4.2 (KDE 4.4.2), Kubuntu packages) Compiler: cc OS:Linux (x86_64) release 2.6.32-21-generic In Kde3, it used to be possible to sort contacts into categories. This feature seems to be gone now. Why was it removed? Strangely enough, even the first Kde4 versions still had it... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 236824] Where are the Categories
https://bugs.kde.org/show_bug.cgi?id=236824 --- Comment #2 from Alain Knaff kde kde lka org lu 2010-05-08 12:14:13 --- Great news... but why is the same mistake repeated all over the place, especially a year after konsole, plasma, amarok, ... got lots of heat over exactly the same subject? Well, let's hope the new Kde 4.5 version will at least be able to pick up the categories of existing users... or did the Kde 4.4 version permanently wipe them? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 214815] New: Wish to drag n drop message to directory (instead of save as)
https://bugs.kde.org/show_bug.cgi?id=214815 Summary: Wish to drag n drop message to directory (instead of save as) Product: kmail Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: alain.baecker...@laposte.net Version:(using KDE 4.3.2) OS:Linux Installed from:Ubuntu Packages Kmail 1.12.2 (kde 4.3.2) can save as a message in one folder (a documentation directory of a project for a client) but drag'n drop does not work (even if trying to put the message in a directory opened in konqueror or dolphin (1.3) It would be very nice to enable * drag 'n drop into a folder * possibility to link instead of copy * even better : possibility to bookmark a message in konqueror (i have a documentation bookmark-folder for each client) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 179997] can't sign mails with gpg
https://bugs.kde.org/show_bug.cgi?id=179997 --- Comment #24 from Alain BAECKEROOT alain baeckeroot laposte net 2009-10-28 12:40:05 --- Finally it works :-) thanks to #22 and the installation of pinetry-qt4 and reconfiguration with kgpg. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 179997] can't sign mails with gpg
https://bugs.kde.org/show_bug.cgi?id=179997 --- Comment #18 from Alain BAECKEROOT alain baeckeroot laposte net 2009-10-27 20:54:47 --- How can this bug can be tagged resolved, when the brand new 4.3 suffers from it, and makes kmail unusable ! On 4th August 2009, KDE 4.3.0 was released by the KDE community and no distribution is shipping 4.4 ! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 179997] can't sign mails with gpg
https://bugs.kde.org/show_bug.cgi?id=179997 --- Comment #19 from Alain BAECKEROOT alain baeckeroot laposte net 2009-10-27 20:56:56 --- the workaround given in #15 does not work for me. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 122684] konqueror does not give the in-reply-to field to kmail
https://bugs.kde.org/show_bug.cgi?id=122684 --- Comment #10 from Alain BAECKEROOT alain baeckeroot laposte net 2009-10-27 21:13:43 --- 1/ This still does not work with Konqueror 4.3.2 (KDE 4.3.2) + Kmail 1.12.2 2/ clicking on url given in #7 make kmail crypting the message. something need to be done. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 122088] PGP/MIME signature check/decryption fails
https://bugs.kde.org/show_bug.cgi?id=122088 Alain BAECKEROOT alain.baecker...@laposte.net changed: What|Removed |Added CC||alain.baecker...@laposte.ne ||t --- Comment #3 from Alain BAECKEROOT alain baeckeroot laposte net 2009-10-19 17:58:51 --- I have a rather similar problem in kmail KMail Version 1.12.2 (KDE 4.3.2 ubuntu-karmic beta) I can crypt mails, but i cannot sign them ! kmail complains about no valid key or wrong pass phrase. https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 211107] New: cannot sign mails, but can crypt/decrypt them
https://bugs.kde.org/show_bug.cgi?id=211107 Summary: cannot sign mails, but can crypt/decrypt them Product: kmail Version: 1.12.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: alain.baecker...@laposte.net Version: 1.12.2 (using KDE 4.3.2) OS:Linux Installed from:Ubuntu Packages I cannot _sign_ mail (test mails i send to myself), but i can crypt/decrypt them. Kmail complains about wrong pass phrase when i try to sign a mail, but it did not asked for it (and i can crypt/decrypt whith the same key and passphrase) https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719 100% reproducible currently. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 115962] Kmail riddled with modal dialog boxes
https://bugs.kde.org/show_bug.cgi?id=115962 --- Comment #5 from Alain Knaff kde kde lka org lu 2009-09-12 15:45:06 --- You are right that this example is less bad than the initial one, as it doesn't contain ask for any input, and thus can be dismissed right away without the user needing to look information elsewhere in the application in order to fill it in. However, a similar modal box pops up when connection to the server fails for whatever reason (network disconnected, firewall rules, ...). In that case too, the box takes no input. But the user might want to keep it around in order to have the error message under his eyes when reviewing the config of the connection. Which he can't do, because the box is modal. And in the connection case, there is no second main window which he can use to access the config! Yes, the user could copy-paste the error text elsewhere, but why impose such hassle? And yes, in the case I tested (firewall rule), the error message was meaningless anyways (Unknown error, instead of Connection timed out or somesuch), but that makes it 1+1=2 bugs, not 1-1=0 bugs that cancel out :-). Btw, the system error is accessible to the application even if non-blocking connect() system call is used, via the getsockopt(Sockfd, SOL_SOCKET, SO_ERROR, error, len) call. No, I can't reproduce the initial bug _exactly_ as reported, as the relevant certificates have expired since then, and I would get different errors. But the same _category_ of issue still exists, and that is what I was trying to point out. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 115962] Kmail riddled with modal dialog boxes
https://bugs.kde.org/show_bug.cgi?id=115962 Alain Knaff k...@kde.lka.org.lu changed: What|Removed |Added Status|NEEDSINFO |ASSIGNED Resolution|WAITINGFORINFO | Ever Confirmed|0 |1 --- Comment #3 from Alain Knaff kde kde lka org lu 2009-09-03 07:21:15 --- While much progress is made (login boxes are no longer modal), there are still some left elsewhere in the code. One easy-to-find example: try composing a mail, and send it while forgetting to add a recipient. The error box that then pops up is modal, and prevents to open the addressbook via the composer window's Tools menu (...and all other items from the Composer's menu as well, but the addressbook is relevant because it helps getting the information that is being asked for). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 198687] New: Accented characters in IMAP user flags cause an infinite loop.
https://bugs.kde.org/show_bug.cgi?id=198687 Summary: Accented characters in IMAP user flags cause an infinite loop. Product: kio Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: imap AssignedTo: kdepim-bugs@kde.org ReportedBy: al...@topaze.homeip.net Version:(using KDE 4.2.4) Compiler: gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3 OS:Linux Installed from:Ubuntu Packages kio_imap4 enters an infinite loop in imapParser::parseLiteral if the fetched flags for a message contain accented characters. My IMAP server is Zimbra 5.0.14. The problem started when I marked a message with a tag named Répondre. I don't know what the imap rfc says about accented chars in flags, but an infinite loop is definitely not an appropriate behaviour... gdb on the kio_imap4 process shows: (gdb) where #0 0xb65e18b3 in memcpy () from /lib/tls/i686/cmov/libc.so.6 #1 0xb7d91a88 in QByteArray::realloc (this=0xbf8a7584, alloc=0) at /usr/include/bits/string3.h:52 #2 0xb5e0472f in imapParser::parseOneWord (inwor...@0xbf8a77ec, stopAtBracket=false) at /usr/include/qt4/QtCore/qbytearray.h:410 #3 0xb5e05c19 in imapParser::parseLiteral (this=0x9193028, inwor...@0xbf8a77ec, relay=false, stopAtBracket=40) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.cpp:1929 #4 0xb5e05f9e in imapParser::parseSentence (this=0x9193028, inwor...@0xbf8a77ec) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.cpp:1642 #5 0xb5e0ada6 in imapParser::parseFetch (this=0x9193028, inwor...@0xbf8a77ec) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.cpp:1460 #6 0xb5e0eb22 in imapParser::parseUntagged (this=0x9193028, resu...@0xbf8a77ec) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.cpp:496 #7 0xb5e0efd2 in imapParser::parseLoop (this=0x9193028) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.cpp:1752 #8 0xb5dfc3c4 in IMAP4Protocol::listDir (this=0x9193010, _u...@0xbf8a7bec) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imap4.cpp:607 #9 0xb78f3574 in KIO::SlaveBase::dispatch (this=0x9193010, command=71, da...@0xbf8a7cc0) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:1081 #10 0xb5df8548 in IMAP4Protocol::dispatch (this=0x9193010, command=71, da...@0xbf8a7cc0) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imap4.cpp:1835 #11 0xb78f1cfc in KIO::SlaveBase::dispatchLoop (this=0x9193010) at /build/buildd/kde4libs-4.2.4/kio/kio/slavebase.cpp:282 #12 0xb5de594d in kdemain (argc=4, argv=0x917bb70) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imap4.cpp:136 #13 0x0804dd11 in launch (argc=4, _name=0x9166bc4 kio_imap4, args=0x9166c3d , cwd=0x0, envc=0, envs=0x9166c42 , reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8050c93 0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:689 #14 0x0804e47d in handle_launcher_request (sock=7) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1270 #15 0x0804e9ca in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1463 #16 0x0804f604 in main (argc=2, argv=0xbf8a83f4, envp=0xbf8a8400) at /build/buildd/kde4libs-4.2.4/kinit/kinit.cpp:1951 (gdb) break imapParser::parseLiteral Breakpoint 1 at 0xb5e059bd: file /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.h, line 56. (2 locations) (gdb) cont Continuing. [Switching to Thread 0xb5f88a10 (LWP )] Breakpoint 1, imapParser::parseLiteral (this=0x9193028, inwor...@0xbf8a77ec, relay=false, stopAtBracket=false) at /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.h:56 56 /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.h: No such file or directory. in /build/buildd/kdepimlibs-4.2.4/kioslave/imap4/imapparser.h (gdb) p inWords.data.d $1 = (QByteArray::Data *) 0x923f0c0 (gdb) x/40s 0x923f0c0 0x923f0c0: \001 0x923f0c2: 0x923f0c3: 0x923f0c4: 1 0x923f0c6: 0x923f0c7: 0x923f0c8: / 0x923f0ca: 0x923f0cb: 0x923f0cc: ��#\t* 953 FETCH (UID 15518 FLAGS (\\Seen Répondre)) 0x923f100: \n (see the FETCH line). This is reproducible. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
