[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Raymond Wooninck <tittiatc...@gmail.com> changed: What|Removed |Added Severity|normal |major --- Comment #5 from Raymond Wooninck <tittiatc...@gmail.com> --- In a number of cases, this also causes a 100% cpu utilization of the remaining kmail process. When this happened, I attached gdb to this kmail process and exactly the same backtrace was generated. At this moment it would make kmail not really a good candidate for KDE Apps 16.04 -- 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
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #3 from Raymond Wooninck <tittiatc...@gmail.com> --- Hi Dan, As requested, I attached gdb to the running process and then entered "t a a bt" to create the backtrace. The most interesting part would be this: Thread 1 (Thread 0x7fab6bb5b800 (LWP 3532)): #0 0x7fab68b69c1d in poll () from /lib64/libc.so.6 #1 0x7fab5e6fbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fab5e6fbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fab696abb0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fab69652b23 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fab6a4671de in KJob::exec() () from /usr/lib64/libKF5CoreAddons.so.5 #6 0x7fab6b3b9106 in KMKernel::cleanup (this=this@entry=0x7ffc19a85df0) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/kmkernel.cpp:1410 #7 0x004042fa in main (argc=1, argv=0x7ffc19a86008) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/main.cpp:153 Looking at the source code of kmkernel.cpp (at line 1410) then it seems to try to run jobStatistics->exec() which somehow doesn't return. Hope this helps. Let me know if you need more info -- 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
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #4 from Raymond Wooninck <tittiatc...@gmail.com> --- A better one with also the debug info for libKF5CoreAddons. It could be that it is a change in coreaddons. Thread 1 (Thread 0x7fab6bb5b800 (LWP 3532)): #0 0x7fab68b69c1d in poll () from /lib64/libc.so.6 #1 0x7fab5e6fbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fab5e6fbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fab696abb0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fab69652b23 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fab6a4671de in KJob::exec (this=this@entry=0x96df70) at /usr/src/debug/kcoreaddons-5.19.0git.20160109T125454~e8444d1/src/lib/jobs/kjob.cpp:199 #6 0x7fab6b3b9106 in KMKernel::cleanup (this=this@entry=0x7ffc19a85df0) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/kmkernel.cpp:1410 #7 0x004042fa in main (argc=1, argv=0x7ffc19a86008) at /usr/src/debug/kdepim-15.12.60git.20160120T085743~887bcda/kmail/main.cpp:153 -- 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
[kmail2] [Bug 358216] kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 --- Comment #2 from Raymond Wooninck <tittiatc...@gmail.com> --- (In reply to Daniel Vrátil from comment #1) > Could you try to get a backtrace to see what KMail is doing that's > preventing it from closing? Hi Dan, Sure. As long as you let me know what exactly you are looking for or how I should get the backtrace :) -- 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
[kmail2] [Bug 358216] New: kmail keeps running in the background after quitting the program
https://bugs.kde.org/show_bug.cgi?id=358216 Bug ID: 358216 Summary: kmail keeps running in the background after quitting the program Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tittiatc...@gmail.com I have noticed that kmail actually keeps running in the background after you try to close the program. Selecting "File -> Quit" makes the systray icon disappear, but the kmail process is still active in the background. Even with "Alt-Tab" window switcher, you can not find the kmail window anymore. One would expect that kmail is gone. When you now start a new kmail session, you suddenly get a crash reported from kmail indicating if you want to report a bug or to restart the program. The newly started kmail functions normally. This also applies to kontact !! Reproducible: Always Steps to Reproduce: 1. Start kmail or kontact. 2. Choose File -> Quit (kmail or kontact will close normally) 3. Open a konsole and check with ps if kmail or kontact are still there Actual Results: the kmail or kontact process is still active in the background, but can not be reached. Starting now a new kmail or kontact will cause a crash report for the old active process. Expected Results: The kmail or kontact process is normally closed and disappeared. Starting a new session afterwards should not generate a crash. -- 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
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Raymond Wooninck <tittiatc...@gmail.com> changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #3 from Raymond Wooninck <tittiatc...@gmail.com> --- If everyone would have a proper look, then it would have been visible that the KDEPIM package itself was not published yet. Unfortunately KDE Applications finds itself in a slow building state, so it will take time to get this completely published. This is actually the risk of utilizing a development repository. KDE Applications would have come to Tumbleweed and Leap 42.1 as soon as everything would have been build properly. At this moment, I would suggest to revert back to the versions that are offered in Tumbleweed and/or Leap:Updates -- 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
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 --- Comment #4 from Raymond Wooninck <tittiatc...@gmail.com> --- Please close this bug as invalid and this one should have been reported at bugzilla.opensuse.org -- 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
[kmail2] [Bug 351677] After udating to 15.08 kmail crashes on pressing "new message"
https://bugs.kde.org/show_bug.cgi?id=351677 Raymond Wooninck <tittiatc...@gmail.com> changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #16 from Raymond Wooninck <tittiatc...@gmail.com> --- Everyone is indicating that kmail is crashing, but where is the backtrace ? A good bug report would have the backtrace of the crash attached. Of course make sure you have the debug packages (if required for your distro) installed and then drkonqi should be able to create a nice backtrace that the developer can use to find the issue. -- 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
[kmail2] [Bug 342655] Kmail (git master) crashes when trying to reply to a message
https://bugs.kde.org/show_bug.cgi?id=342655 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #2 from Raymond Wooninck tittiatc...@gmail.com --- Me neither :) I wasn't even aware anymore that I opened a bug report for it. Kmail at the moment is in a good shape and working perfectly. -- 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
[kmail2] [Bug 347240] KMail does not release memory
https://bugs.kde.org/show_bug.cgi?id=347240 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Raymond Wooninck tittiatc...@gmail.com --- I didn't checked the memory usage for some time and with the latest snapshot from git master, the memory usage has been heavily reduced and seems to be stable. Opening a folder and then an email will increase the memory, but when a smaller email is then selected the memory usages goes down (which is expected behavior). Closing the bug as resolved. -- 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
[kmail2] [Bug 347240] KMail does not release memory
https://bugs.kde.org/show_bug.cgi?id=347240 --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- I have tried two different setups (with and without Preview Pane), but the result remains the same. The memory usage of kmail is increased by the amount of memory required to display the email itself. Even if the case where the email is only displayed in a separate window (setup without preview), the memory is not released after closing this window. The memory is only being released once kmail itself is being closed. -- 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
[kmail2] [Bug 347240] KMail does not release memory
https://bugs.kde.org/show_bug.cgi?id=347240 --- Comment #3 from Raymond Wooninck tittiatc...@gmail.com --- I tried to use massif, but this was killing the system and I wasn't really able to click on a number of emails. I then switched to heaptrack and I have attached the logfile. I have previewed about 30 emails and the total memory consumption as reported by ksysguard was around 1.4Gb for kmail. -- 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
[kmail2] [Bug 347240] KMail does not release memory
https://bugs.kde.org/show_bug.cgi?id=347240 --- Comment #4 from Raymond Wooninck tittiatc...@gmail.com --- Created attachment 92479 -- https://bugs.kde.org/attachment.cgi?id=92479action=edit heaptrack file -- 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
[kmail2] [Bug 347240] New: KMail does not release memory
https://bugs.kde.org/show_bug.cgi?id=347240 Bug ID: 347240 Summary: KMail does not release memory Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tittiatc...@gmail.com I just started kmail and looked at a couple of emails. Checking the memory, it seems that KMail is using 1.1Gb of memory. Clicking on a new folder with emails or an email itself seems to increase the memory usage. However this seems only to be released when kmail is closed. With ksysguard, I get the following information for kmail : Process 3494 - kmail Summary The process kmail (with pid 3494) is using approximately 1.1 GB of memory. It is using 1.1 GB privately, and a further 83.1 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 15.3 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 1.1 GB. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 7 threads. Private more 1134320 KB[heap] 3268 KB/usr/lib64/libQt5WebKit.so.5.4.2 2464 KB/usr/lib64/libQt5WebEngineCore.so.5.4.2 2124 KB/usr/lib64/libkmailprivate.so.4.75.0 1008 KB/usr/share/icu/54.1/icudt54l.dat Shared more 13516 KB/usr/lib64/libQt5WebKit.so.5.4.2 3976 KB/usr/lib64/libQt5Widgets.so.5.4.2 3840 KB/usr/lib64/libQt5Core.so.5.4.2 3732 KB/usr/lib64/libQt5Gui.so.5.4.2 3568 KB/SYSV (deleted) Totals Private1157388 KB(= 13152 KB clean + 1144236 KB dirty) Shared85096 KB(= 81448 KB clean + 3648 KB dirty) Rss1242484 KB(= Private + Shared) Pss1173061 KB(= Private + Shared/Number of Processes) Swap0 KB Reproducible: Always Steps to Reproduce: 1. Start kmail 2. open ksysguard 3. start clicking on emails (email shown in preview window) Actual Results: Memory usage increases and increases Expected Results: Memory usage should not really increase or slightly and released again after some time. All kdepim components are based on git master. -- 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
[kdepim] [Bug 346175] KDE PIM 15.08 release tracking bug
https://bugs.kde.org/show_bug.cgi?id=346175 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Depends on||346370 -- 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
[Akonadi] [Bug 337686] Error occurs when a sent email is configured to be placed in the Sent Mail folder of the gmail resource.
https://bugs.kde.org/show_bug.cgi?id=337686 --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- Actually the agent is crashing upon access any emails in the sent-folder of the IMAP account and not just when email is retrieved. -- 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
[Akonadi] [Bug 342437] Akonadi_agent_launcher (imap resource for gmail) crashes when receiving emails in the send-folder
https://bugs.kde.org/show_bug.cgi?id=342437 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Component|general |IMAP resource CC||kdepim-bugs@kde.org, ||vkra...@kde.org Version|unspecified |GIT (master) Product|kde |Akonadi -- 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
[Akonadi] [Bug 342437] Akonadi_agent_launcher (imap resource for gmail) crashes when receiving emails in the send-folder
https://bugs.kde.org/show_bug.cgi?id=342437 --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- This is with Akonadi git master compiled for KDE Frameworks. All Frameworks libraries are git master. -- 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
[Akonadi] [Bug 342437] Akonadi_agent_launcher (imap resource for gmail) crashes when receiving emails in the send-folder
https://bugs.kde.org/show_bug.cgi?id=342437 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Platform|unspecified |openSUSE RPMs -- 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
[kmail2] [Bug 341457] New: Kmail (Framework branch) inserts an additional To: and Subject: into the header upon sending emails.
https://bugs.kde.org/show_bug.cgi?id=341457 Bug ID: 341457 Summary: Kmail (Framework branch) inserts an additional To: and Subject: into the header upon sending emails. Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tittiatc...@gmail.com I have build/installed the full KDEPIM suite from the Framework branch and am using akonadi-runtime from the master branch. Everything seems to be working fine, however the only major issue is that upon sending emails the header block with the Addressees and Subject is duplicated. This causes that the sender (depending on his email client) sees a subject missing subject and multiple recipients are shown. Below is the paste of the email source that I send to myself: Return-Path: tittiatc...@gmail.com Received: from hqvmt44011.eur.cchbc.com ([80.108.147.43]) by mx.google.com with ESMTPSA id gy8sm3160977wib.23.2014.12.01.03.16.34 for multiple recipients (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Dec 2014 03:16:34 -0800 (PST) From: Raymond Wooninck tittiatc...@gmail.com Subject: missing subject To: tittiatc...@gmail.com Cc: raymond.wooni...@chello.at To: tittiatc...@gmail.com tittiatc...@gmail.com Cc: raymond.wooni...@chello.at raymond.wooni...@chello.at Subject: Test Date: Mon, 01 Dec 2014 12:16:25 +0100 Message-ID: 45755231.umg0vt3...@hqvmt44011.eur.cchbc.com User-Agent: KMail/4.72 pre (Linux/3.17.2-1-desktop; KDE/5.5.0; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset=us-ascii Test I am not sure if this is an issue of the sending akonadi resource (it happens with both IMAP and SMTP) or that it is kmail. The issue is bad as that e.g. GMail itself bounces the email back with the indication: Final-Recipient: RFC822; tittiatc...@gmail.com Action: failed Status: 5.1.1 Remote-MTA: dns; gmail-smtp-in.l.google.com (74.125.136.26) Diagnostic-Code: smtp; 550-5.7.1 [62.179.121.43 12] Our system has detected that this message is 550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail, 550-5.7.1 this message has been blocked. Please visit 550-5.7.1 http://support.google.com/mail/bin/answer.py?hl=enanswer=188131 for 550 5.7.1 more information. vf7si29786552wjc.81 - gsmtp Reproducible: Always Steps to Reproduce: 1. Use KMail based on Frameworks 2. Send an email 3. Actual Results: Email headers are misformed and causes rejections from email providers. Expected Results: An email with a correct header is being send -- 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
[kmail2] [Bug 341457] Kmail (Framework branch) inserts an additional To: and Subject: into the header upon sending emails.
https://bugs.kde.org/show_bug.cgi?id=341457 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Version|unspecified |Git (master) -- 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
[Akonadi] [Bug 337686] New: Error occurs when a sent email is configured to be placed in the Sent Mail folder of the gmail resource.
https://bugs.kde.org/show_bug.cgi?id=337686 Bug ID: 337686 Summary: Error occurs when a sent email is configured to be placed in the Sent Mail folder of the gmail resource. Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Gmail resource Assignee: dvra...@redhat.com Reporter: tittiatc...@gmail.com CC: kdepim-bugs@kde.org If the Identity is configured to place sent emails in a specific folder and this folder points to the Sent Mail folder of the GMail resource the following error occurs: Sending succeeded, but failed to move the message to the sent-mail folder. Moving items into virtual collection is not allowed. This leaves the email in the outbox which results that another attempt is made to send the email and move it to the configured sent-mail folder. And this goes on and on and on -- 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
[Akonadi] [Bug 337665] New: The new GMAIL resources does not change the email from unread to read
https://bugs.kde.org/show_bug.cgi?id=337665 Bug ID: 337665 Summary: The new GMAIL resources does not change the email from unread to read Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Gmail resource Assignee: dvra...@redhat.com Reporter: tittiatc...@gmail.com CC: kdepim-bugs@kde.org I managed to set up the GMail resource to work with my gmail account. I had to cleanup on both sides, but now it seems to work. However I noticed a strange behavior when reading emails. When an email is read, the unread count in the folder overview is reduced and shows the correct number of unread emails remaining. However in the message view, the email remains blue and the envelope before the email itself is not opened. Closing kmail and opening it again, shows the correct view with the read emails correctly marked by black text and an opened envelope. Switching from one folder to the next however doesn't help. -- 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
[Akonadi] [Bug 337665] The new GMAIL resources does not change the email from unread to read
https://bugs.kde.org/show_bug.cgi?id=337665 --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- I also checked through the webgui of gmail itself and it seems that the emails are correctly being marked as read. So it is purely a refresh issue of the gmail resource -- 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
[Akonadi] [Bug 337669] New: The gmail resource does not delete emails remotely which leads to a full resync of the mailbox
https://bugs.kde.org/show_bug.cgi?id=337669
Bug ID: 337669
Summary: The gmail resource does not delete emails remotely
which leads to a full resync of the mailbox
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Gmail resource
Assignee: dvra...@redhat.com
Reporter: tittiatc...@gmail.com
CC: kdepim-bugs@kde.org
I have some folders in which I just get a notification that a task needs to be
done. Afterwards I directly delete that email. Doing the same with the new
GMAIL resource, leads to unexpected results/issues.
I select the email to be deleted and press the Del-key. Nothing happens and the
email is still there. Restarting KMail resolves this issue as that the email is
now gone. However this results in a different issue as that the gmail resource
detects an inconsistency between local and remote as that it never succeeded to
delete the email remotely. The resource is now performing a full resync which
has as a consequence that the deleted email appears again.
The output log from akonadictl is:
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap) RemoveItemsTask::doStart:
Deleting 1 messages from [Gmail]/All Mail
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap) KIMAP::StoreJob::doStart:
526671 +FLAGS (\Deleted)
akonadi_baloo_indexer(3708) EmailIndexer::process: Indexing Request 241747
requires review (submit openSUSE:Factory/virt-viewer)
SEARCH:
Query: { limit : -1, negated : false, rel : 1, subTerms : [ {
cond : 0, key : email, negated : false, value :
dims...@opensuse.org } ] }
MimeTypes: (text/directory)
Collections: QVector()
Remote: false
Recursive true
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::startRetrievalTasks: Starting retrieval for [Gmail]/Trash
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: Starting message retrieval. Elapsed(ms):
2917
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: MessageCount: 0 Local message count: 0
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: UidNext: 453536 Local UidNext: 453536
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: HighestModSeq: 23670344 Local
HighestModSeq: 23670189
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: No messages present so we are done
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::taskComplete: Applying collection changes
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::taskComplete: Retrieval complete. Elapsed(ms): 2917
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveCollectionMetadataTask::doStart: /[Gmail]/Trash
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::startRetrievalTasks: Starting retrieval for [Gmail]/Trash
SEARCH:
Query: { limit : -1, negated : false, rel : 1, subTerms : [ {
cond : 0, key : email, negated : false, value :
factory-a...@kulow.org } ] }
MimeTypes: (text/directory)
Collections: QVector()
Remote: false
Recursive true
SEARCH:
Query: { limit : -1, negated : false, rel : 1, subTerms : [ {
cond : 0, key : email, negated : false, value :
factory-a...@kulow.org } ] }
MimeTypes: (text/directory)
Collections: QVector()
Remote: false
Recursive true
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: Starting message retrieval. Elapsed(ms):
4807
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: MessageCount: 0 Local message count: 0
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: UidNext: 453536 Local UidNext: 453536
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: HighestModSeq: 23670344 Local
HighestModSeq: 23670189
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::onFinalSelectDone: No messages present so we are done
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::taskComplete: Applying collection changes
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::taskComplete: Retrieval complete. Elapsed(ms): 4807
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveCollectionMetadataTask::doStart: /[Gmail]/Trash
akonadi_gmail_resource_10(3710)/kdepimlibs (kimap)
RetrieveItemsTask::startRetrievalTasks: Starting retrieval for [Gmail]/All
Mail
Tag context: -1
Collection context: 9
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString)
Notification source kmail2_3765_t9vPMD now
[Akonadi] [Bug 336758] GMail resource never starts
https://bugs.kde.org/show_bug.cgi?id=336758 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- If I look in the resource Schedulers page of akonadiconsole, then I can see that the gmail resource seems to be hanging in the step Custom-startConnect. At least this one stays on the status running . -- 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
[akregator] [Bug 336417] New: Akregator crashes when being closed
https://bugs.kde.org/show_bug.cgi?id=336417 Bug ID: 336417 Summary: Akregator crashes when being closed Classification: Unclassified Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tittiatc...@gmail.com Application: akregator (4.14 pre) KDE Platform Version: 4.13.60 Qt Version: 4.8.6 Operating System: Linux 3.15.0-3.gcc07b60-desktop x86_64 Distribution: openSUSE 13.2 Milestone 0 (Harlequin) (x86_64) -- Information about the crash: Closing akregator causes akregator to crash. Akregator functions normally without any issues until I close the window. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. To enable execution of this file add add-auto-load-safe-path /usr/lib64/libstdc++.so.6.0.19-gdb.py line to your configuration file /home/hq06/.gdbinit. To completely disable this security protection add set auto-load safe-path / line to your configuration file /home/hq06/.gdbinit. For more information about this security protection see the Auto-loading safe path section in the GDB manual. E.g., run from the shell: info (gdb)Auto-loading safe path [KCrash Handler] #5 0x7f8c57bd3dd7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #6 0x7f8c58ca1a62 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib64/libakregatorprivate.so.4 #7 0x7f8c58c988c8 in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib64/libakregatorprivate.so.4 #8 0x7f8c40c08e47 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib64/kde4/akregatorpart.so #9 0x7f8c57bd404a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x7f8c58c98349 in Akregator::FetchQueue::slotAbort() () from /usr/lib64/libakregatorprivate.so.4 #11 0x7f8c58c983ba in Akregator::FetchQueue::~FetchQueue() () from /usr/lib64/libakregatorprivate.so.4 #12 0x7f8c58c98429 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib64/libakregatorprivate.so.4 #13 0x7f8c58c973ef in Akregator::Kernel::~Kernel() () from /usr/lib64/libakregatorprivate.so.4 #14 0x7f8c5626ff99 in __run_exit_handlers () from /lib64/libc.so.6 #15 0x7f8c5626ffe5 in exit () from /lib64/libc.so.6 #16 0x7f8c56259b0c in __libc_start_main () from /lib64/libc.so.6 #17 0x0040872b in _start () Possible duplicates by query: bug 318038. Reported using DrKonqi -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #12 from Raymond Wooninck tittiatc...@gmail.com --- Issue has been resolved. Synchronizing my GMAIL account is now done is the same time as with KDE 4.13.0. -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #10 from Raymond Wooninck tittiatc...@gmail.com --- (In reply to comment #9) It means UID's 257301 to 257400 are fetched which only correlates to the number of messages that ever have been in the folder (not to the amount you currently have). So the number of flags that are going to be retrieved is only increasing with time ? I would have expected that the IMAP resource would not start retrieving flags for messages that are no longer existing. Because at this moment I see that the fetching starts with number 1 to 100 and then moves up to 100 to 200, etc. So in the above example 257400 flags are trying to be fetched despite that I have only maybe 100 messages in that particular folder. Which is quite an overkill, in my opinion. I am currently trying to increase the batchsizes, but what I have noticed is that the main issue comes from those high-volume folders where the fetching starts from 1 and goes up to 257400 (regardless of how many emails are actually in that folder (local and server). So it seems that Akonadi is just keeping the latest message number and the IMAP resource will always start from 1. In case of an empty folder, this could mean that the IMAP resource is spending 1 or more minutes on trying to retrieve thousands of non-existing flags. I am sure that there must be a better way to retrieve only the flags for existing messages. -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #4 from Raymond Wooninck tittiatc...@gmail.com --- (In reply to comment #3) The problem with gmail is that it's CONDSTORE support is broken (I think it was something with the tag folders?), and we therefore have to fetch all flags on every sync. I think the resource simply ignored flag changes But shouldn't this generate network traffic ? Because the flags needs to be retrieved from the server, but during this period I do not see any traffic at all until it reaches the point where it can retrieve some new email. Sorry if I introduced performance problems, but I'm generally preferring correctness over performance, but we can re-add optimizations as necessary. Correctness is fine, but in this world Performance is more important to the users. And it seems that this correctness also creates the situation that the IMAP resource is no longer fast enough and starts blocking itself. (As reported in the other bug). I guess that the IMAP resource now has reached a point where its developers should decide what it actually supports. If the requirement is that it needs a correct CONDSTORE, then support for gmail should be dropped. Maybe moving the gmail support to a separate resource would be much better, so that this specific gmail resource can have all the things required to support a broken GMAIL. -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #6 from Raymond Wooninck tittiatc...@gmail.com --- (In reply to comment #5) This should generate network traffic indeed. Strangely enough I didn't notice any network traffic during this period. As indicated network traffic is only visible around the end. That's just a regular bug that needs to be fixed. Ok. Just strange that it seems only to hit the gmail IMAP. Daniel is already working on a specialized IMAP resource that implements the GMAIL specific extensions, so that will be covered eventually. That is great news :) I will let him know that he already found a test person for it :) But I'd still expect the plain IMAP resource to work reasonably well with GMAIL as long as they provide regular IMAP. Ok. -- 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
[Akonadi] [Bug 334269] Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 --- Comment #3 from Raymond Wooninck tittiatc...@gmail.com --- I can confirm that with this commit the HALT situation is no longer occurring. -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #8 from Raymond Wooninck tittiatc...@gmail.com --- (In reply to comment #7) (In reply to comment #6) (In reply to comment #5) This should generate network traffic indeed. Strangely enough I didn't notice any network traffic during this period. As indicated network traffic is only visible around the end. Please let me know if the situation is improved or still the same with the fix for the other bug. With the fix for the other bug, the synchronization went back to about 5 minutes and now I see network traffic during the flag retrieval. What exactly does the number mean in this line : akonadi_imap_resource_16(30157)/kdepimlibs (kimap) BatchFetcher::fetchNextBatch: Fetching 257301 to 257400 Does that mean that I have 257400 emails in that folder ? If so, then something else is wrong. I know that I have a number of high volume email lists (e.g. kde-com...@kde.org), but I am deleting the emails from there every 3 days to reduce the total number of emails. I also cleaned up in gmail.com itself, so I shouldn't have those many emails. Flag fetching definitely is slower because I'm currently fetching the flags just as messages in batches of 100 to avoid overloading akonadi. This obviously results in many roundtrips, and I suppose the batchsize could be greatly increased for flags (because a lot less data than full messages). Can I increase the number somewhere ? Just to test if I can find a better number for my system and to retrieve things a little faster ? -- 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
[Akonadi] [Bug 334269] New: Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 Bug ID: 334269 Summary: Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error Classification: Unclassified Product: Akonadi Version: GIT (master) Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: tittiatc...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org With the latest commits regarding the IMAP resource last night (Friday May 2), the email retrieval for gmail is no longer working. I have the following experience: 1) Email retrieval is very slow. Much slower than before 2) The debug output shows that for each folder all emails are retrieved in batches until the moment that fetchNextBatch is called while a fetchBatch is still active. At this moment, the IMAP resource NO longer retrieves any emails and just comes to a full HALT. 3) You can stop the email retrieval at that moment, but with the next scheduled one, this again comes to a HALT after the same message. The debug output in the console is : akonadi_imap_resource_13(23100)/kdepimlibs (kimap) BatchFetcher::fetchNextBatch: Fetching 57401 to 57500 akonadi_imap_resource_13(23100)/kdepimlibs (kimap) BatchFetcher::fetchNextBatch: Fetching 57501 to 57600 akonadi_imap_resource_13(23100)/kdepimlibs (kimap) BatchFetcher::fetchNextBatch: Fetching 57601 to 57700 akonadi_imap_resource_13(23100)/kdepimlibs (kimap) BatchFetcher::fetchNextBatch: Fetching 57701 to 57800 akonadi_imap_resource_13(23100) BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process akonadi_imap_resource_11(23099)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_imap_resource_10(23098)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_imap_resource_10(23098)/kdepimlibs (kimap) RetrieveItemsTask::startRetrievalTasks: Starting retrieval for INBOX.Spam akonadi_imap_resource_11(23099)/kdepimlibs (kimap) RetrieveItemsTask::startRetrievalTasks: Starting retrieval for INBOX.Trash akonadi_imap_resource_10(23098)/kdepimlibs (kimap) RetrieveItemsTask::onFinalSelectDone: Starting message retrieval. Elapsed(ms): 374 akonadi_imap_resource_10(23098)/kdepimlibs (kimap) RetrieveItemsTask::onFinalSelectDone: MessageCount: 0 Local message count: 0 akonadi_imap_resource_10(23098)/kdepimlibs (kimap) RetrieveItemsTask::onFinalSelectDone: UidNext: 1 Local UidNext: 1 akonadi_imap_resource_10(23098)/kdepimlibs (kimap) RetrieveItemsTask::onFinalSelectDone: HighestModSeq: 1 Local HighestModSeq: 1 Reproducible: Always Steps to Reproduce: 1. Try to retrieve emails 2. 3. Actual Results: Emails are not retrieved and IMAP resource comes to a HALT Expected Results: Emails are retrieved normally -- 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
[Akonadi] [Bug 334269] Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- For now I have resolved the situation with reverting commit a5cd38deac8f6bbdd46bdcf88a4dfaf581b27e5c . I know that this is not optimal and I might loose locally some email, but at least I am able to synchronize. -- 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
[Akonadi] [Bug 334280] New: IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 Bug ID: 334280 Summary: IMAP Synchronisation with GMAIL takes 13 minutes to complete !! Classification: Unclassified Product: Akonadi Version: GIT (master) Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: tittiatc...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org The current state of the IMAP resource in git master delivers an unacceptable synchronization time for a Gmail resource. It takes around 13 minutes to do one synchronization. I have attached the debug log of the IMAP resource to this bug report, but what I have noticed is that during most of these 13 minutes there is no disk activity, no network connectivity and also the progress meter in kmail just stays at 0. The only thing happening during this period is that the debuglog shows the line BatchFetcher::fetchNextBatch: Fetching x to y. Strangely enough every mail check these counters always start from 1. I already made sure that all Archived emails in gmail.com itself was deleted and I recreated the gmail imap resource, but this all didn't help. At this moment it seems that it is just the gmail connectivity that is affected. Reproducible: Always -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- Created attachment 86429 -- https://bugs.kde.org/attachment.cgi?id=86429action=edit Debug output of the imap resource -- 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
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #2 from Raymond Wooninck tittiatc...@gmail.com --- I reverted the Christian's commits from Friday afternoon and tried to see where that would bring the situation. After the revert, Gmail synchronization is done in about 1 minute, which is acceptable. Comparing the logs then I can see the following Git master: Starting retrieval for INBOX Starting message retrieval. Elapsed(ms): 161 MessageCount: 626 Local message count: 626 UidNext: 59721 Local UidNext: 59721 HighestModSeq: 0 Local HighestModSeq: 0 Listing flags 1 59721 Starting flag retrieval. Elapsed(ms): 162 Fetching 1 to 100 Retrieval complete. Elapsed(ms): 27321 With the revert I see Starting retrieval for INBOX Starting message retrieval. Elapsed(ms): 167 Listing flags 1 59726 Starting flag retrieval. Elapsed(ms): 167 Retrieval complete. Elapsed(ms): 3470 So the inbox is with the latest git master retrieved in 27 seconds, while before the commits the inbox was retrieved in about 3,5 seconds. -- 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
[Akonadi] [Bug 331703] Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 --- Comment #4 from Raymond Wooninck tittiatc...@gmail.com --- @Antonio Rojas, Are you sure that you are talking about the same issue here ? The initial issue is that even after 1 hour the mail folders are not automatically refreshed. Only email in the inbox is being retrieved. What you indicate seems to be something logical. How would Kmail now if an email is read on another device until the folders are refreshed. Question is if this refresh is automatically happening (e.g. according to the time indicated) or that even after 10 hours no refresh too place. The issue indicated by me was resolved during the Beta's of KDE 4.13 and I can confirm that it works. -- 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
[Akonadi] [Bug 331703] Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 --- Comment #6 from Raymond Wooninck tittiatc...@gmail.com --- What you indicate is definitely different than my issue. But I never saw that all folders were kept in sync instantly. But maybe this is dependent on the email provider. What I see and what I also saw in 4.12 is that kmail retrieves changes on the indicated interval. -- 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
[Akonadi] [Bug 331703] New: Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 Bug ID: 331703 Summary: Auto refresh of the IMAP email accounts no longer works Classification: Unclassified Product: Akonadi Version: GIT (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: tittiatc...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Since last week Thursday evening, we are seeing the issue that kmail no longer automatically refreshes the IMAP accounts. At the given intervals nothing seems to happen, except for the INBOX. After some checking only the INBOX for the IMAP accounts is being checked, but not the folders. This is particular noticeable for GMail when the filtering is done on the GMail server and not locally. Clicking on Check email works as expected and all folders are being refreshed. Also opening a folder within kmail works and the content is refreshed with the server itself. So it seems really to be the automatic check that only functions for the INBOX, but not the other defined IMAP folders. We tried to disect by reverting certain commits in kdepimlibs and kdepim-runtime (commits done since Thursday morning), but we couldn't restore the proper function. Reproducible: Always Steps to Reproduce: 1. Set an automatic refresh for an IMAP Akonadi resource 2. Wait until the refresh time has finishes 3. Actual Results: Folders are not refreshed, only new emails in the INBOX are being received Expected Results: All folders are refreshed in the same manor as the Manual Mail Check Running latest git master for Akonadi, kdepimlibs, kdepim-runtime and kdepim -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #71 from Raymond Wooninck tittiatc...@gmail.com --- Hi Christian, I already updated kdepimlibs with your patch from the reviewboard yesterday and have been running with it during the whole day. Normally the issue occurs multiple times a day on my system, but this time all the unread emails could be seen in the folders. So I guess you hit the jackpot with your patch :) Thanks for fixing. Raymond -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #49 from Raymond Wooninck tittiatc...@gmail.com --- Hi Christian, Message count is indeed correct, as checking in akonadiconsole the new message is indeed there. Switching to another folder and back doesn't have any effect, neither does the New Tab have any effect on this. So far the only real solution is to restart kmail or to restart the akonadiserver. -- 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
[kmail2] [Bug 323155] New: Kmail no longer sends emails and the email remains in the inbox until the akonadiserver is restarted
https://bugs.kde.org/show_bug.cgi?id=323155 Bug ID: 323155 Summary: Kmail no longer sends emails and the email remains in the inbox until the akonadiserver is restarted Classification: Unclassified Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tittiatc...@gmail.com The latest versions of Akonadi and Kmail are causing a strange effect where emails are received normally, but emails are no longer send out and they remain in the outbox. During startup I also receive an warning that the mailfilteragent is not connected to the DBus (or something similar) and checking the status of the mailfilteragent in akonadiconsole, I see that the status is green, but I do not see the word Ready behind it. Restarting the agent gives exactly the same situation. At this moment I am not sure if these are two issues are that they are connected, as that restarting the mailfilteragent doesn't resolve the sending issue. But restarting the full akonadiserver does. Reproducible: Always Steps to Reproduce: 1. Start kmail as normal 2. Create an email and press send 3. Email appears in outbox and is never send Actual Results: The email sits in the outbox and is never send until I restart the akonadiserver (or the full system). No error messages, it just sits there untouched. Expected Results: Email is send directly -- 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
[kmail2] [Bug 323155] Kmail no longer sends emails and the email remains in the inbox until the akonadiserver is restarted
https://bugs.kde.org/show_bug.cgi?id=323155 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Raymond Wooninck tittiatc...@gmail.com --- Resolved with the latest akonadi commits. -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #24 from Raymond Wooninck tittiatc...@gmail.com --- Christian, Maybe you have resolved the issue for that particular use case, but I just had this issue occurring again and I am running kmail git version from last night. I don't do anything strange with kmail. Kmail is sitting in the systray and the main window is minimized. I had it active for about 3,5 hours and everything worked fine. Now I see that I have an unread email, but kmail doesn't show that unread email. Only the unread count is shown. -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #9 from Raymond Wooninck tittiatc...@gmail.com --- This seems to be a bug in Kmail itself, as that on akonadi level the emails are available. I will attach a screenshot where I have the situation that Kmail indicates unread emails, but doesn't show them, but akonadiconsole (which was opened at the same time as Kmail) clear shows those emails. I have setup the akonadi resouces to stay online all the time and when I restart Kmail, the missing emails are then shown correctly. This clearly points that somewhere Kmail looses contact with Akonadi regarding the email headers. -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 --- Comment #10 from Raymond Wooninck tittiatc...@gmail.com --- Created attachment 77288 -- https://bugs.kde.org/attachment.cgi?id=77288action=edit Kmail and Akonadiconsole showing the emails, which clearly shows the fault in kmail -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #8 from Raymond Wooninck tittiatc...@gmail.com --- I see exactly the same issue. However with me this can happen at the same time with multiple folders. I hope that this gets fixed soon, because this is really becoming annoying. Almost every mail check delivers this situation. -- 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 278068] New: Outbox directory is no longer created, which causes an startup error for KMail
https://bugs.kde.org/show_bug.cgi?id=278068 Summary: Outbox directory is no longer created, which causes an startup error for KMail Product: Akonadi Version: 4.8 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Mail Dispatcher Agent AssignedTo: kdepim-bugs@kde.org ReportedBy: tittiatc...@gmail.com CC: vkra...@kde.org Version: 4.8 (using Devel) OS:Linux In the last week I had some instability of Plasma-desktop and krunner. Both issues seemed to be related to the connectivity to the calendar and contacts data (Plasma-desktop crashed due to the digital clock plasmoid and krunner crashed based on the contacts runner). I wiped out the full Akonadi setup for my local user (wiped the directories $HOME/.local/share/akonadi, $HOME/.local/share/local-mail, $HOME/.local/share/.local-mail.directory, $HOME/.config/akonadi and the akonadi configuration files from $HOME/.kde4/share/config). I started akonadi through akonadictl startup and everything seemed to be fine. Starting Kmail to define my email accounts however gave the error : KMail encountered a fatal error and will terminate now. The error was: Failed to fetch the resource collection. Further checking learned that the directory $HOME/.local/share/.local-mail.directory is missing and this would be the outbox. The local folders resource is created fine ($HOME/.local/share/local-mail). Deleting the akonadi resources Mail Dispatcher Agent and Local Folders and then to add them again, does not resolve the issue. I am currently using the latest git for KDE (including Akonadi-runtime and kdepim), but talking to the openSUSE KDE Maintainers this problem also occurs with KDE 4.7 rc2. Reproducible: Always Steps to Reproduce: Setup Akonadi for the first-time. Actual Results: Missing outbox that causes KMail to crash Expected Results: The folder that contains the outbox is created -- 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 278068] Outbox directory is no longer created, which causes an startup error for KMail
https://bugs.kde.org/show_bug.cgi?id=278068 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID --- Comment #2 from Raymond Wooninck tittiatcoke gmail com 2011-07-19 12:19:33 --- With the help of Christophe, I managed to find the real cause of the issue. It seems that the Akonadi-runtime package was not correctly build or contained errors. A local build of akonadi-runtime resolved the above mentioned issue and everything seemed to be working fine again. I am closing this bug report as resolved/invalid. -- 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 254388] No longer possible to send emails
https://bugs.kde.org/show_bug.cgi?id=254388 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #6 from Raymond Wooninck tittiatcoke gmail com 2010-10-21 15:53:16 --- The bug is fixed with commit 1188123. -- 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 254388] New: No longer possible to send emails
https://bugs.kde.org/show_bug.cgi?id=254388 Summary: No longer possible to send emails Product: kmail2 Version: 2.0.89 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions AssignedTo: kdepim-bugs@kde.org ReportedBy: tittiatc...@gmail.com Version: 2.0.89 (using Devel) OS:Linux Since Thursday evening, the kmail2 version from SVN trunk is no longer capable of sending emails. In the settings/accounts/sending, I initially had Never Automatically, Send Now options, but whatever I put there, emails are not send out. I tried to send them manually, but it seems that this command is completely ignored. Changing the setting to On every Mailcheck, shows that there is not a single attempt to send the mail in the outbox. Just as if the folder does not exist. Retrieving emails works fine. This behavior has been confirmed by two other people, one of them being Christophe Giboudeaux (IRC: krop). Reproducible: Always Steps to Reproduce: 1. Create a new email 2. Send it. Actual Results: Email remains in the outbox, unsent. Expected Results: Email is being send and a confirmation is given that the email has been send. -- 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 254388] No longer possible to send emails
https://bugs.kde.org/show_bug.cgi?id=254388 --- Comment #1 from Raymond Wooninck tittiatcoke gmail com 2010-10-16 18:49:02 --- When started from the konsole, kmail gives the following output: hq000...@hqvmt61003:/usr/lib64/chromium kmail Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) hq000...@hqvmt61003:/usr/lib64/chromium kmail2(16136)/kdepimlibs (mailtransport): Could not access Outbox. kmail2(16136)/kdepimlibs (mailtransport) MailTransport::SendQueuedAction::itemAccepted: Item doesn't have DispatchModeAttribute. KConfigIni: In file /usr/share/kde4/config/libkleopatrarc, line 42: Invalid entry (missing '=') kmail2(16136)/kdepimlibs (mailtransport) MailTransport::SendQueuedAction::itemAccepted: Item doesn't have DispatchModeAttribute. I assume that the two errors regarding the DispatchModeAttribute are because of the two emails in the outbox. -- 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 254395] New: pop3 resources switches itself from offline to online if interval mail checking is enabled
https://bugs.kde.org/show_bug.cgi?id=254395 Summary: pop3 resources switches itself from offline to online if interval mail checking is enabled Product: Akonadi Version: 1.4.50 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: POP3 Resource AssignedTo: mcgu...@kde.org ReportedBy: tittiatc...@gmail.com CC: vkra...@kde.org, kdepim-bugs@kde.org Version: 1.4.50 (using Devel) OS:Linux The pop3 resource is created through kmail2 and in the retrieval options it is indicated that the resource should be switched offline on kmail shutdown. When the system is booted up, then the pop3 resource is indeed offline. However after the indicated timing for the Interval Mail Checking, the resource switches to online and tries to check for email. If the system at that moment does not have a network connection, then a dialog is presented to adjust the password settings as that the mailbox couldn't be checked. Especially on a laptop this is not wanted as that it could happen quite often that there is no network connection available. If it was just a silent check without the dialog, then it would be a little bit better. But the best thing would be that the resource obeys it's settings and that if the resource is offline, the interval mail checking should not switch it online Reproducible: Always Steps to Reproduce: 1. Define a pop3 resource in kmail2 2. Enable interval mail checking. 3. Select switch offline when kmail shutdown in the retrieval options 4. Shutdown kmail 5. Validate that the pop3 resource is indeed offline (akonadiconsole) 6. Disconnect the network Actual Results: After a number of minutes (based on the defined interval for the automatic mail checking), a dialog is shown which indicates that the pop3 account could not be reached and if you want to change the authentication settings for this account. Checking with akonadiconsole, it appears that the pop3 resource has been switched to online Expected Results: The pop3 resource should remain offline until kmail2 is started. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 248091] Conflict box shown when opening new emails
https://bugs.kde.org/show_bug.cgi?id=248091 Raymond Wooninck tittiatc...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #1 from Raymond Wooninck tittiatcoke gmail com 2010-08-17 13:30:18 --- The latest svn snapshot of KDEPIM resolves this issue. I will close this report. Thanks -- 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
