[Akonadi] [Bug 403903] does not respect org.kde.pim.ews.client: a:ErrorServerBusy: The server cannot service this request right now. Try again later.
https://bugs.kde.org/show_bug.cgi?id=403903 --- Comment #2 from Martin Steigerwald --- Bug 404079 - EWS will not download new email anymore after a:ErrorServerBusy: The server cannot service this request right now. Try again later. is related. Apparently Akonadi EWS can get completely stuck after not respecting a:ErrorServerBusy. (BTW for me it is complete news to me that a mail or groupware server can report that it is busy. My private Dovecot IMAP/POP3 *never* *ever* did that. And it points out that there is an issue Microsoft might be responsible for – unless Akonadi EWS is doing something excessive here. However, also if the error means that Microsoft failed to allocate sufficient resources for the service, it still would be good that Akonadi EWS respects it. :) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404079] EWS will not download new email anymore after a:ErrorServerBusy: The server cannot service this request right now. Try again later.
https://bugs.kde.org/show_bug.cgi?id=404079 Martin Steigerwald changed: What|Removed |Added Summary|EWS will not download new |EWS will not download new |email |email anymore after ||a:ErrorServerBusy: The ||server cannot service this ||request right now. Try ||again later. Severity|grave |major --- Comment #3 from Martin Steigerwald --- Okay, Aaron, thanks for your prompt update. Lowering severity as there is no data loss involved. (Severity is not how you feel about the bug, but about how severe it factually is.) I found that you already reported something similar: Bug 403903 - org.kde.pim.ews.client: a:ErrorServerBusy: The server cannot service this request right now. Try again later. I am trying to see how this bug report is not a duplicate of your older bug report: So what is new here is that you like to point out that Akonadi EWS, after not respecting ErrorServerBusy, gets stuck completely? For now I have changed the title as such. Feel free to clarify and change the title as you see fit. Do you see anything in the logs that is different from what you mentioned in bug 403903? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403903] does not respect org.kde.pim.ews.client: a:ErrorServerBusy: The server cannot service this request right now. Try again later.
https://bugs.kde.org/show_bug.cgi?id=403903 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de Summary|org.kde.pim.ews.client: |does not respect |a:ErrorServerBusy: The |org.kde.pim.ews.client: |server cannot service this |a:ErrorServerBusy: The |request right now. Try |server cannot service this |again later.|request right now. Try ||again later. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404079] EWS will not download new email
https://bugs.kde.org/show_bug.cgi?id=404079 --- Comment #2 from Aaron Williams --- The emails are still on the server, but Akonadi seems unable to download the rest of the emails. It usually downloads until it gets eServerBusy where the server tells Akonadi to wait (up to 5 minutes). Akonadi ignores this and just continues to try and download. Often Akonadi never recovers when the busy period has ended. I have 61,577 emails sitting in my inbox and I have folders with considerably more email due to some mailing lists I belong to. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404079] EWS will not download new email
https://bugs.kde.org/show_bug.cgi?id=404079 Martin Steigerwald changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mar...@lichtvoll.de Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Steigerwald --- Dear Aaron. As frustrating that experience sounds, are you actually *sure* that those mails are lost? If they are still accessible within Outlook Web Access, they are not lost. Remember – except for some state information, configuration and delayed updating of remote resources – Akonadi is just a cache. Akonadi misconception #1: where is my data? https://blogs.kde.org/2011/11/13/akonadi-misconception-1-where-my-data Please check whether the mails you miss are still accessible within Outlook Web Access (or another mail client using OWA like Evolution with evolution-ews) and report back. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404079] New: EWS will not download new email
https://bugs.kde.org/show_bug.cgi?id=404079 Bug ID: 404079 Summary: EWS will not download new email Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: aar...@doofus.org CC: kri...@op.pl Target Milestone: --- SUMMARY EWS lost most of my email and can't download any new email. I have been restarting Akonadi and trying to get it to start downloading EWS email again but for some reason it's been stuck since early this morning. At some point most of my email went poof and I can't download it again. STEPS TO REPRODUCE 1. Click on my Office365 account inbox 2. Note that no new email is displayed 3. Try and refresh the inbox (never completes) OBSERVED RESULT It seems to get stuck retrieving inbox items at some point after office365 returns eServerBusy. When the server is no longer busy, things don't recover. To make matters worse, however, it seems like it lost most of my email. I do have some emails, which are the emails it downloaded before eServerBusy started up. EXPECTED RESULT I expect it to downlSOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: OpenSUSE 15.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 Akonadi: 18.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Christian Boltz changed: What|Removed |Added CC||kde-b...@cboltz.de -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 390260] akonadi-ews-resource segfault
https://bugs.kde.org/show_bug.cgi?id=390260 Martin Steigerwald changed: What|Removed |Added Resolution|REMIND |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Martin Steigerwald --- Hello Kai. Thank you for the information. I am closing this bug cause as you do not use KDEPIM/Akonadi anymore, you would not provide any further information – for example whether this segfault still exists. If anyone finds this segfault again, please open a new bug. Thank you. As for Baloo: That is a different topic, but this bug tracker is not the place to discuss it. However, in case you can confirm [frameworks-baloo] [Bug 404057] New: Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing please comment there, so I can set it to CONFIRMED. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 401692] Akonadi components crash on logout
https://bugs.kde.org/show_bug.cgi?id=401692 Christopher Lee Thomas changed: What|Removed |Added CC||christopherlee.thomas@a08.n ||et -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390260] akonadi-ews-resource segfault
https://bugs.kde.org/show_bug.cgi?id=390260 --- Comment #3 from Kai Krakow --- I removed Akonadi completely because it started to accumulate gigabytes of RAM over time since one of the last updates (the processes growing to 9 GB of RAM usage). And there's even not a sane mail client to actually use Akonadi's potential. KMail is still very unstable, slow, and buggy. So I moved away and I am currently using Mailspring instead. I may try the KDE PIM suite some day in the future again because I'm missing the calendar feature. The next thing to go away is probably baloo because it got slow. Its processes tend to grow to 3-4 GB of RAM usage and eat a lot of IO performance during that process, the system feels very laggy until I kill the processes. Also, it started to re-index all my files on every reboot. In both cases I tried recreating the databases (Akonadi and Baloo) from scratch but it didn't solve the problem. I'm feeling a bit sad about this because usually I enjoyed the good integration of the KDE components into the complete desktop. But if it makes a quite potent system to vastly slow down for extended periods of time, I have no other choice. I needed to remove all PIM components completely to get back a snappy and stable KDE desktop. :-( I wonder why this hit me lately: I've run with both Baloo and Akonadi for years and never experienced the problems one could read about in hundreds of forums, namely that those services slow done people's systems. Now it happened to me, too, and the impact is really very big. Baloo and Akonadi really need some love, and I wish I could be part of this by contributing help with identifying and fixing bugs. But the negative impacts it had on my productivity were just too big. I'm sorry. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] Crash during/after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 --- Comment #4 from Martin Steigerwald --- Okay, on one hand DrKonqi does not thing the backtraces are related, on the other hand it truncates the backtrace when I tell it to add it to the bug report. Since I do not know whether DrKonqi got this right, this time I add the full backtrace manually: 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 0x7f0102391f00 (LWP 13263))] Thread 30 (Thread 0x7f00d8a49700 (LWP 14328)): #0 0x7f011866e3a9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f00d8a48400, expected=0, futex_word=0x7f00d8a485e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f011866e3a9 in __pthread_cond_wait_common (abstime=0x7f00d8a484a0, mutex=0x7f00d8a48598, cond=0x7f00d8a485c0) at pthread_cond_wait.c:533 #2 0x7f011866e3a9 in __pthread_cond_timedwait (cond=0x7f00d8a485c0, mutex=0x7f00d8a48598, abstime=0x7f00d8a484a0) at pthread_cond_wait.c:667 #3 0x7f0111cbaa37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0111cbd30a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0111cbd3f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0111cc1981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0111cc2e61 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0111ccbc81 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0118667fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7f011ae2e80f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7effdb1d7700 (LWP 14274)): #0 0x7f011ae3ba8b in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:63 #1 0x7f011ae3d814 in ___fprintf_chk (fp=0x7f011aef28b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f010cc59848 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f010cc41a5a in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f010cc41c34 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f010cc43588 in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f010cc39329 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f0111c8f7cd in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0111caec8b in base::RunLoop::Run() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0111cd0204 in base::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0111ccbc81 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f0118667fa3 in start_thread (arg=) at pthread_create.c:486 #11 0x7f011ae2e80f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f00caffd700 (LWP 14088)): #0 0x7f011866e3a9 in futex_reltimed_wait_cancelable (private=0, reltime=0x7f00caffc400, expected=0, futex_word=0x7f00caffc5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f011866e3a9 in __pthread_cond_wait_common (abstime=0x7f00caffc4a0, mutex=0x7f00caffc598, cond=0x7f00caffc5c0) at pthread_cond_wait.c:533 #2 0x7f011866e3a9 in __pthread_cond_timedwait (cond=0x7f00caffc5c0, mutex=0x7f00caffc598, abstime=0x7f00caffc4a0) at pthread_cond_wait.c:667 #3 0x7f0111cbaa37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0111cbd30a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0111cbd3f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0111cc1981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0111cc2e61 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0111ccbc81 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0118667fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7f011ae2e80f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f005bfff700 (LWP 13527)): #0 0x7f011866dfbc in futex_wait_cancelable (private=0, expected=0, fute
[kmail2] [Bug 404052] Crash during/after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 --- Comment #3 from Martin Steigerwald --- Created attachment 117912 --> https://bugs.kde.org/attachment.cgi?id=117912&action=edit New crash information added by DrKonqi kmail (5.9.3) using Qt 5.11.3 - What I was doing when the application crashed: Another backtrace. Let's see whether DrKonqi truncates this one as well. If it does, I will cut and paste the full backtrace in a moment. -- Backtrace (Reduced): #6 0x7f011959515a in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #7 0x7f01195db2ef in Akonadi::Item::hasAttribute(QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #8 0x7f01196c5a7e in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #9 0x7f01196c3154 in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #10 0x7f01196b342a in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 Sergey V Turchin changed: What|Removed |Added CC||z...@altlinux.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] Crash during/after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 Martin Steigerwald changed: What|Removed |Added Summary|Crash after filtering |Crash during/after |inbox, probably related to |filtering inbox, probably |Qt WebEngine integration|related to Qt WebEngine ||integration -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] Crash after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 --- Comment #2 from Martin Steigerwald --- I do not know why DrKonqi reduced the backtrace. It definately looked longer. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] Crash after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] Crash after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 --- Comment #1 from Martin Steigerwald --- Created attachment 117911 --> https://bugs.kde.org/attachment.cgi?id=117911&action=edit New crash information added by DrKonqi kmail (5.9.3) using Qt 5.11.3 - What I was doing when the application crashed: Okay, this happens also with KDEPIM/Akonadi 18.03.1 (all packages upgraded). Another backtrace attached. -- Backtrace (Reduced): #6 0x7f0f32c2c15a in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #7 0x7f0f32c722ef in Akonadi::Item::hasAttribute(QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #8 0x7f0f32d5ca7e in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #9 0x7f0f32d5a154 in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 #10 0x7f0f32d4a42a in () at /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 404058] New: Global Menu does not work if started with --iconify
https://bugs.kde.org/show_bug.cgi?id=404058 Bug ID: 404058 Summary: Global Menu does not work if started with --iconify Product: kontact Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sefa6...@gmail.com Target Milestone: --- SUMMARY When running Kontact with --iconify (e.g. on autostart) the Global Menu does not work, when the window is shown. I have to start Kontact normally (without any parameters) to get a Global Menu. STEPS TO REPRODUCE 1. Run kontact --iconify 2. Open Kontact window by clicking on the tray icon. 3. Try to use Global Menu OBSERVED RESULT Global Menu not shown, Kontact has no menu in the window EXPECTED RESULT Global Menu visible. No menu in the window SOFTWARE/OS VERSIONS Linux: Arch Linux - rolling Linux 4.20.6-zen1-1-zen (available in About System) KDE Plasma Version: 5.14.90 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 404052] New: Crash after filtering inbox, probably related to Qt WebEngine integration
https://bugs.kde.org/show_bug.cgi?id=404052 Bug ID: 404052 Summary: Crash after filtering inbox, probably related to Qt WebEngine integration Product: kmail2 Version: 5.9.1 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mar...@lichtvoll.de Target Milestone: --- Application: kmail (5.9.1) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 5.0.0-rc4-tp520 x86_64 Distribution: Debian GNU/Linux buster/sid -- Information about the crash: Please note that this may be a packaging issue within Debian Unstable. However, I am reporting it upstream nonetheless, cause it may not be and this way I may receive some hints on what to fix within Debian in case it indead is a packaging issue. # What I was doing when the application crashed: - I selected all new mails in inbox and hit Ctrl-J to filter them. The inbox is part of a maildir resource that retrieved mails from a POP3 resource. # Actual results (sometimes, but often enough, several times a day) - KMail/Akonadi starts filtering the mail into their relevant folders. - KMail crashes. Background on that: - I usually have most filters not act on any new mails, but just manually, … - so I first see all mail in inbox to skim through it and after I did… - I select them all and initiate filtring then. # Expected results - KMail completes filtering and stays around after that :) # Further information - KDEPIM 18.03.3 (with a bit of 18.03.1, just upgrading currently, I bet it does not affect the bug, as this issue happened with KDEPIM 18.03.1 as well, but when it indeed fixes the issue, I close this report). - KDE Frameworks 5.5.4 - KDE Plasma 5.14.5 - Qt 5.11.3 - on Debian Unstable The crash can be reproduced sometimes. -- 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 0x7fb3d6b8bf00 (LWP 28434))] Thread 32 (Thread 0x7fb2ae3fb700 (LWP 6853)): #0 0x7fb3ed066399 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb2ae3fa400, expected=0, futex_word=0x7fb2ae3fa5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb3ed066399 in __pthread_cond_wait_common (abstime=0x7fb2ae3fa4a0, mutex=0x7fb2ae3fa598, cond=0x7fb2ae3fa5c0) at pthread_cond_wait.c:533 #2 0x7fb3ed066399 in __pthread_cond_timedwait (cond=0x7fb2ae3fa5c0, mutex=0x7fb2ae3fa598, abstime=0x7fb2ae3fa4a0) at pthread_cond_wait.c:667 #3 0x7fb3e66b2a37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb3e66b530a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb3e66b53f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb3e66b9981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb3e66bac7f in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb3e66c3c81 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fb3ed05ffa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fb3ef8267ef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fb2aa132700 (LWP 6754)): #0 0x7fb3ed066399 in futex_reltimed_wait_cancelable (private=0, reltime=0x7fb2aa131400, expected=0, futex_word=0x7fb2aa1315e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fb3ed066399 in __pthread_cond_wait_common (abstime=0x7fb2aa1314a0, mutex=0x7fb2aa131598, cond=0x7fb2aa1315c0) at pthread_cond_wait.c:533 #2 0x7fb3ed066399 in __pthread_cond_timedwait (cond=0x7fb2aa1315c0, mutex=0x7fb2aa131598, abstime=0x7fb2aa1314a0) at pthread_cond_wait.c:667 #3 0x7fb3e66b2a37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fb3e66b530a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fb3e66b53f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fb3e66b9981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fb3e66bae61 in base::internal::SchedulerWorker::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fb3e66c3c81 in base::(anonymo
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de Status|CONFIRMED |NEEDSINFO Resolution|--- |REMIND --- Comment #17 from Martin Steigerwald --- Hello. Olivier, thanks for the bug report and all the others for their findings about it. As Stefan committed what appears to be a fix to me quite some time ago, is the issue fixed meanwhile? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403982] EWS gets stuck in "Retrieving collection tree"
https://bugs.kde.org/show_bug.cgi?id=403982 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #4 from Martin Steigerwald --- Thank you Aaron, for all your valuable bug reports. I am looking forward to use Akonadi EWS myself, however I am currently still stuck with KDEPIM 18.08.1 within Debian, at least until an updated Flatpak becomes available or I install KDE Neon or so into a VM. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403981] EWS resource needs to be able to specify identity to use
https://bugs.kde.org/show_bug.cgi?id=403981 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #1 from Martin Steigerwald --- Hi Aaron. Thanks for your bug report. A possible work-around for you could be: Having one Linux user for the work related stuff and one for the private stuff (thus separating all other user data as well). I work this way and switch using Ctrl-Alt-F7/F8 between them. That said, being able to set an identity of cause makes sense to have within EWS resource. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402599] EWS does not display progress when downloading email
https://bugs.kde.org/show_bug.cgi?id=402599 --- Comment #1 from Martin Steigerwald --- *** Bug 402178 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402178] Please show download/synchronization progress
https://bugs.kde.org/show_bug.cgi?id=402178 Martin Steigerwald changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Martin Steigerwald --- This is essentially a duplicate of bug #402599. While bug #402599 is a later report, it is more concise, so setting this earlier bug report as a duplicate of the later one *** This bug has been marked as a duplicate of bug 402599 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402178] Please show download/synchronization progress
https://bugs.kde.org/show_bug.cgi?id=402178 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de Severity|major |wishlist Summary|Email folders are all empty |Please show ||download/synchronization ||progress --- Comment #3 from Martin Steigerwald --- Setting as feature request. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 388773] Kerberos ticket is not automatically renewed when expired
https://bugs.kde.org/show_bug.cgi?id=388773 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de Resolution|--- |REMIND Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Steigerwald --- Hi Victor. Sorry that you did not receive a reply to this bug so far. Does the bug still happen with KDEPIM/Akonadi 18.12? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 390260] akonadi-ews-resource segfault
https://bugs.kde.org/show_bug.cgi?id=390260 Martin Steigerwald changed: What|Removed |Added Resolution|--- |REMIND Status|REPORTED|NEEDSINFO CC||mar...@lichtvoll.de --- Comment #2 from Martin Steigerwald --- Hi Kai. Sorry that you did not receive a reply to this bug so far. Does the crash still happen with KDEPIM/Akonadi 18.12 and recent KDE Frameworks? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 Volker Krause changed: What|Removed |Added CC||vkra...@kde.org --- Comment #10 from Volker Krause --- Hit this too. Unclear what caused it, but the workaround from #338658 seems to fix the damage: DELETE pimitemtable FROM pimitemtable LEFT JOIN parttable ON pimitemtable.id = parttable.pimItemId WHERE parttable.id IS NULL That would suggest that a part-less item can fairly reliably trigger the transaction deadlock. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 401056] akonadiserver memory leak
https://bugs.kde.org/show_bug.cgi?id=401056 Sergey V Turchin changed: What|Removed |Added CC||z...@altlinux.org -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 403982] EWS gets stuck in "Retrieving collection tree"
https://bugs.kde.org/show_bug.cgi?id=403982 --- Comment #3 from Aaron Williams --- I don't know if this is related to bug# 403903 but no matter what I did I was unable to synchronize my inbox folder which has a significant number of emails. My settings were identical to another machine. I was finally able to get it work by shutting down akonadi and kontact then replicating everything from the other computer including the database. Once I did that it started working again since it no longer had to download a lot of emails. Also, I saw it getting stuck in other stages besides retrieving collection tree. When the server tells the client it is busy the server may report that it will be busy for several minutes. I wonder if honoring the busy delay might help. When it stops, all EWS log activity stops. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402994] Kmail crashed after mailto process
https://bugs.kde.org/show_bug.cgi?id=402994 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are the assignee for the bug.
