[kmail2] [Bug 414839] Folder expiration not automatic
https://bugs.kde.org/show_bug.cgi?id=414839 Laurent Montel changed: What|Removed |Added Version Fixed In||5.13.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/mai ||lcommon/50c4c271080a144fd64 ||5892081c0f623aee2e6b2 --- Comment #2 from Laurent Montel --- Git commit 50c4c271080a144fd645892081c0f623aee2e6b2 by Laurent Montel. Committed on 06/12/2019 at 07:50. Pushed by mlaurent into branch 'release/19.12'. Fix Bug 414839 - Folder expiration not automatic FIXED-IN: 5.13.0 M +3-3src/folder/foldercollectionmonitor.cpp https://commits.kde.org/mailcommon/50c4c271080a144fd645892081c0f623aee2e6b2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #4 from Attila --- I suggest that this bug should be classified as a serious bug, because I lose every day a lot of emails. This bug should be fixed as soon as possible. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 414528] kmail moving mail (delete, move, read) crash akonadi
https://bugs.kde.org/show_bug.cgi?id=414528 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414839] Folder expiration not automatic
https://bugs.kde.org/show_bug.cgi?id=414839 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I will investigate soon -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kcalendarcore] [Bug 412025] Wrong timezone offset with TZID=Western/Central Europe
https://bugs.kde.org/show_bug.cgi?id=412025 --- Comment #8 from Roland Tapken --- I've checked the diff from 3.0.5 to 3.0.6, it might be possible that the problem has really been solved since the new version contains new code to parse TZOFFSETFROM and TZOFFSETTO, which might resolve the issue. I'll try to backport the patch to 3.0.5 and update my Ubuntu package. -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kcalendarcore] [Bug 412025] Wrong timezone offset with TZID=Western/Central Europe
https://bugs.kde.org/show_bug.cgi?id=412025 --- Comment #7 from Roland Tapken --- Correction: I wrote it on September 18th, your first comment was from October. But still in DST, which might matter regarding a 1-hour-offset. -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kcalendarcore] [Bug 412025] Wrong timezone offset with TZID=Western/Central Europe
https://bugs.kde.org/show_bug.cgi?id=412025 --- Comment #6 from Roland Tapken --- Allen, I wrote the bug report on October 14th, in Daylight Saving Time (CEST). Can you change your system date to summer and check again? Ubuntu still delivery libical 3.0.5, so I cannot test directly. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414864] New: kmail crash quite ramdomly
https://bugs.kde.org/show_bug.cgi?id=414864 Bug ID: 414864 Summary: kmail crash quite ramdomly Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: r...@fc.ul.pt Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-2-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: Most of the times I was selecting a folder. Sometimes it hapens without any user action at the moment but it may be indexing or syncronizing. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103 [Current thread is 1 (Thread 0x7fac6a820440 (LWP 92910))] Thread 24 (Thread 0x7fab57fff700 (LWP 93391)): #0 0x7fac7b56a139 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fac7b51f1aa in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fac7d5f780b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fac7d5a071b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fac7d3e1751 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fac7d3e28d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fac7be76fb7 in start_thread (arg=) at pthread_create.c:486 #7 0x7fac7d06a2cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fab5700 (LWP 93089)): #0 0x7fac7d05b89c in __GI___libc_read (nbytes=16, buf=0x7fab5fffe490, fd=80) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fac7d05b89c in __GI___libc_read (fd=80, buf=0x7fab5fffe490, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fac7b565d4f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fac7b51ebee in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fac7b51f042 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fac7b51f1bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fac7d5f780b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fac7d5a071b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fac7d3e1751 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fac7d3e28d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fac7be76fb7 in start_thread (arg=) at pthread_create.c:486 #11 0x7fac7d06a2cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fab717b9700 (LWP 92957)): #0 0x7fac7d05b89c in __GI___libc_read (nbytes=16, buf=0x7fab717b8490, fd=78) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fac7d05b89c in __GI___libc_read (fd=78, buf=0x7fab717b8490, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fac7b565d4f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fac7b51ebee in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fac7b51f042 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fac7b51f1bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fac7d5f780b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fac7d5a071b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fac7d3e1751 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fac7d3e28d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fac7be76fb7 in start_thread (arg=) at pthread_create.c:486 #11 0x7fac7d06a2cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7fab71fba700 (LWP 92956)): #0 0x7fac7d3e2d3c in QMutex::lock() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fac7d5f76fe in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fac7b51e61f in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fac7b51efcb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fac7b51f1bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fac7d5f780b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fac7d5a071b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fac7d3e1751 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
[frameworks-kholidays] [Bug 414369] Please add Lebanon to the list of holidays.
https://bugs.kde.org/show_bug.cgi?id=414369 --- Comment #10 from Hussam Al-Tayeb --- (In reply to Christophe Giboudeaux from comment #9) > You can find examples of islamic holidays in a couple files (holiday_bh_ar, > holiday_dz_ar, holiday_eg_ar, holiday_ma_ar) This clarifies it a bit https://cgit.kde.org/kholidays.git/tree/holidays/plan2/holiday_bh_ar Thank you. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[frameworks-kholidays] [Bug 414369] Please add Lebanon to the list of holidays.
https://bugs.kde.org/show_bug.cgi?id=414369 Christophe Giboudeaux changed: What|Removed |Added Latest Commit|https://commits.kde.org/kho | |lidays/748d0219f3f34c729f21 | |fe670030a3986c774342| Version Fixed In|5.65| -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[frameworks-kholidays] [Bug 414369] Please add Lebanon to the list of holidays.
https://bugs.kde.org/show_bug.cgi?id=414369 --- Comment #9 from Christophe Giboudeaux --- You can find examples of islamic holidays in a couple files (holiday_bh_ar, holiday_dz_ar, holiday_eg_ar, holiday_ma_ar) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[frameworks-kholidays] [Bug 414369] Please add Lebanon to the list of holidays.
https://bugs.kde.org/show_bug.cgi?id=414369 Luigi Toscano changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[frameworks-kholidays] [Bug 414369] Please add Lebanon to the list of holidays.
https://bugs.kde.org/show_bug.cgi?id=414369 --- Comment #8 from Luigi Toscano --- Git commit df770235396d5e7c1dd98cdfeb02eea38660df14 by Luigi Toscano. Committed on 05/12/2019 at 14:18. Pushed by ltoscano into branch 'master'. Revert "add Lebanon holidays" As discussed in the bug, the change is not complete and having it as it is in the released Frameworks may be more problematic than not having it. Specifically, all the religious date should use the proper rule for dynamic calculation. This applies to both Christian holidays like Western and Eastern Easter and all Islamic holidays, which use a different calendar. The initial proposal is interesting but it should go through a few cycles of reviews, addressing the This reverts commit 748d0219f3f34c729f21fe670030a3986c774342. M +0-1holidays/holidays.qrc D +0-52 holidays/plan2/holiday_lb_ar https://commits.kde.org/kholidays/df770235396d5e7c1dd98cdfeb02eea38660df14 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kmail2] [Bug 414171] Set values in KMail2-options are not written back
https://bugs.kde.org/show_bug.cgi?id=414171 --- Comment #15 from Harold Becker --- Created attachment 124327 --> https://bugs.kde.org/attachment.cgi?id=124327=edit Empty identities in file emailidentities Hello, what's about the identities in emaildentities shown by attachment? Shown empty identities are only a little view of hundreds of empty identities. That are no emailidentities I entered. They inflate the file for what? Best wishes Harold Becker -- You are receiving this mail because: You are the assignee for the bug.
