[kmail2] [Bug 423794] 'kmail --identity' doesn't set the identity's sent folder
https://bugs.kde.org/show_bug.cgi?id=423794 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- kmail 5.7.3 is too old. It seems to work here (kmail 5.15.1) Please test with new version and reopen it Thanks -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426509] No mails shown in KMail after synching
https://bugs.kde.org/show_bug.cgi?id=426509 stakano...@libero.it changed: What|Removed |Added CC||stakano...@libero.it --- Comment #1 from stakano...@libero.it --- I can confirm this for my system: opensuse 15.1 with plasma 5.12.8 Frameworks 5.55.0 QT 5.9.7 4.12.14-lp151.28.67-default The bug hits all mailinglists (in my case the ones of opensuse). Settings are: SSL/TLS port 993. The accounts with STARTTLS and 143 (CRAMMD5) are not hit by this. An active refresh of the folders does not change. The number of the messages is indicated normally and in order of arrival but they are not displayed. When exiting the program and restarting, the mails appear, so there is not data loss. The messages appear also correctly filtered when they do not display and the notification is displayed timely and correctly, so this does not seem filter related. I did run akonadictl fsck and vacuum but there are no errors. Some times a crash of akonadi can be seen when exiting the program but does not seem to be related with this problem (as the bug presents 100% of the time, the crash maybe 10% of the exit / restart procedures. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426509] New: No mails shown in KMail after synching
https://bugs.kde.org/show_bug.cgi?id=426509 Bug ID: 426509 Summary: No mails shown in KMail after synching Product: kmail2 Version: 5.14.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: kozuchowsk...@int.pl Target Milestone: --- SUMMARY No mails appears in KMail after synching an IMAP account from the "int.pl" domain. The connection if working for sure, since the catalogs themselves are synched. Even after restarting akonadi, or the system itself, nothing changes. STEPS TO REPRODUCE 1. Configure the IMAP account (https://help.int.pl/news-parametry-do-konfiguracji-programow-pocztowych,nId,2258146) I used the following configuration: crypt: SSL/TLS port: 993 - using the default port 143, the account is unavailable login method: PLAIN 2. Check the e-mails. Reproducible: always. OBSERVED RESULT KMail is acting as it is synching the mail account, but afterwards, there is no mail at all in any of the IMAP account. I checked with other accounts, on other domains, and everything works just fine. EXPECTED RESULT Having access to the e-mails SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I am using Gentoo, but tried and had the same result with Arch Linux on a virtual machine, and Ubuntu on a live USB stick. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425619] Application: akonadi_imap_resource_5 (akonadi_imap_resource), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425619 --- Comment #6 from john4deidre2...@xtra.co.nz --- Created attachment 131618 --> https://bugs.kde.org/attachment.cgi?id=131618=edit New crash information added by DrKonqi akonadi_imap_resource (5.15.1 (20.08.1)) using Qt 5.15.0 - What I was doing when the application crashed: Not too sure what happened here. it seems to crash intermittently when kmail goes to check for emails now. -- Backtrace (Reduced): #4 QHash::findNode(QByteArray const&, unsigned int*) const (ahp=, akey=..., this=) at /usr/src/debug/akonadi-server-20.08.1-1.1.x86_64/src/core/attributestorage.cpp:69 #5 QHash::contains(QByteArray const&) const (akey=..., this=) at /usr/include/qt5/QtCore/qhash.h:920 #6 Akonadi::AttributeStorage::hasAttribute(QByteArray const&) const (type=..., this=0x40) at /usr/src/debug/akonadi-server-20.08.1-1.1.x86_64/src/core/attributestorage.cpp:69 #7 Akonadi::Collection::hasAttribute(QByteArray const&) const (this=this@entry=0x55ceef4a86f0, type=...) at /usr/src/debug/akonadi-server-20.08.1-1.1.x86_64/src/core/collection.cpp:166 #8 0x7f295d74fdcf in Akonadi::Collection::hasAttribute() const (this=0x55ceef4a86f0) at /usr/include/qt5/QtCore/qarraydata.h:257 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 405922] Very frequent akonadi crash in QLocale::dayName
https://bugs.kde.org/show_bug.cgi?id=405922 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Ahmad Samir --- Do you still see this issue? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 374514] Crash on akonadictl stop
https://bugs.kde.org/show_bug.cgi?id=374514 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Ahmad Samir --- Is this still valid? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426472] New: search contains results not matching the criteria
https://bugs.kde.org/show_bug.cgi?id=426472 Bug ID: 426472 Summary: search contains results not matching the criteria Product: kmail2 Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: gran...@tempmail.de Target Milestone: --- i have a search folder with some specific folders. The criterion is: message status is not read The search folder contains a lot of emails that are read. Furthermore: when i click search, a window pops up asking to reindex some of the folders - but everytime! Is there an indexing problem? Doesnt help if I manually click "reindex" within the folder properties either -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #14 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #13) > For (current stable) Gentoo users: place it beneath > /etc/portage/kde-apps/kdepim-runtime-20.04.3/ and re-emerge kdepim-runtime. Typo alert. It should be /etc/portage/patches/kde-apps/kdepim-runtime-20.04.3/ Note the ‘patches’. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #13 from Erik Quaeghebeur --- Created attachment 131589 --> https://bugs.kde.org/attachment.cgi?id=131589=edit patch that makes sure internal date is used in changeitem-task This patch fixed my issue (limited testing, however). For (current stable) Gentoo users: place it beneath /etc/portage/kde-apps/kdepim-runtime-20.04.3/ and re-emerge kdepim-runtime. Restart akonadi and check whether or not this solves your issue. (It should apply as well to earlier versions and current 20.08.z versions. I'm hoping to get it into a later 20.08.z version.) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 426432] kmail 5.15.1: Crash when sending encrypted mail
https://bugs.kde.org/show_bug.cgi?id=426432 --- Comment #5 from Axel Braun --- (In reply to Christoph Feck from comment #4) > You need to use the 'bt' command in gdb after the crash to get the actual > backtrace. For more information, please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Thanks for the hint, Christoph. I was actually following https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash which leads to a kontact window not being properly redrawn, means showing the background of whatever was just on the screen. So I cant use kontact to reproduce the crash. Tried already to switch video driver from nvidia to intel, no change in results. Any idea? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426463] New: kmail crashes after start
https://bugs.kde.org/show_bug.cgi?id=426463 Bug ID: 426463 Summary: kmail crashes after start Product: kmail2 Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: michael.hael...@online.de Target Milestone: --- Application: kmail (5.14.1 (20.04.0)) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.0-3-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: the PC ran unattended all night. After I switched on the terminal, I started kmail and it crashed. -- 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 0x7fb5f9fb73c0 (LWP 43150))] Thread 28 (Thread 0x7fb5de955700 (LWP 75145)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fb5de953f70, clockid=-560644352, expected=0, futex_word=0x7fb5de9540b8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fb5de953f70, clockid=-560644352, mutex=0x7fb5de954068, cond=0x7fb5de954090) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fb5de954090, mutex=0x7fb5de954068, abstime=0x7fb5de953f70) at pthread_cond_wait.c:656 #3 0x7fb607e5d9ba in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x0001556b in ?? () #5 0x080c89ee in ?? () #6 0x0001554a in ?? () #7 0x080c8dd6 in ?? () #8 0x in ?? () Thread 27 (Thread 0x7fb54e8fa700 (LWP 75144)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fb54e8f8f70, clockid=1318031104, expected=0, futex_word=0x7fb54e8f90b8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fb54e8f8f70, clockid=1318031104, mutex=0x7fb54e8f9068, cond=0x7fb54e8f9090) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fb54e8f9090, mutex=0x7fb54e8f9068, abstime=0x7fb54e8f8f70) at pthread_cond_wait.c:656 #3 0x7fb607e5d9ba in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x0001556b in ?? () #5 0x080d9b74 in ?? () #6 0x0001554a in ?? () #7 0x080d9f5c in ?? () #8 0x in ?? () Thread 26 (Thread 0x7fb5a37fe700 (LWP 75142)): #0 0x7fb6101cc4bf in __GI___poll (fds=0x7fb5880222d0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb60d1977ee in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb60d19790f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61076231b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb61070b4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb6105328de in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb610533a01 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb60dc0eea7 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb6101d6eaf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7fb5bd7fa700 (LWP 56793)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fb5bd7f8f70, clockid=-1115713792, expected=0, futex_word=0x7fb5bd7f90b8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fb5bd7f8f70, clockid=-1115713792, mutex=0x7fb5bd7f9068, cond=0x7fb5bd7f9090) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fb5bd7f9090, mutex=0x7fb5bd7f9068, abstime=0x7fb5bd7f8f70) at pthread_cond_wait.c:656 #3 0x7fb607e5d9ba in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x0001556b in ?? () #5 0x0788e9fc in ?? () #6 0x0001554a in ?? () #7 0x0788ede4 in ?? () #8 0x in ?? () Thread 24 (Thread 0x7fb5bcff9700 (LWP 47135)): #0 0x7fb6101cc4bf in __GI___poll (fds=0x7fb598016f10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb60d1977ee in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb60d19790f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61076231b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb61070b4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb6105328de in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb610533a01 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb60dc0eea7 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb6101d6eaf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 --- Comment #2 from Vadim A. Misbakh-Soloviov (mva) --- as far a I heard, this is related to dovecot on the server end (well, otoh, I personally didn't hear about any other popular non-proprietary sieve daemon). And I think, it can be somehow related to the script path here: https://invent.kde.org/pim/libksieve/-/blob/master/src/kmanagesieve/sievejob.cpp#L79-80 maybe there is a slash missed, or something like that. Unfortunatelly, I failed to debug that properly (wireshark doesn't want to decrypt my sieve traffic even with RSA key used by the server, and I failed to find the place where kmail logs sieve commands (it it does that at all)) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 Vadim A. Misbakh-Soloviov (mva) changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||k...@mva.name -- You are receiving this mail because: You are the assignee for the bug.
