| Summary: | maildir resource not working | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | kavol <kavol> |
| Component: | Maildir Resource | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | grave | CC: | bberberov+kde, g.sora, kdenis, kramski, oblivion4u4me, okurz, tim.eberhardt |
| Priority: | NOR | ||
| Version: | 5.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Output from akonadictl start | ||
(In reply to comment #0) > # rpm -qf /usr/lib64/kde4/akonadi_maildir_resource.so > kdepim-runtime-4.10.3-3.fc19.x86_64 > > ... going to try downgrade damn, nothing older available for F19 :-/ I have a similar problem that could be related using KDE 4.11.2. After many months of use and several KDE upgrades akonadi became more and more unstabel (not starting at all, producing very high disk i/o, unresponsive, local mail folders in Kmail unaccessible/offline, not able to manage resources because akonadi would crash....). I then decided to make a new KDE profile and delete ~/.kde, ~/.config and ~/.local. After this I configured my mail/dav accounts (2 IMAP with several thousand mails, and one cal/carddav over owncloud). After everything was in sync again problems started again. This time mostly the maildir_resource for the local Kmail folders was causing problems and was offline. Akonadi then tried to create maildir agent after maildir agents and I had almost 15 of them in the end. Additionally after login akonadi produced high disk i/o and sometimes failed to start. I then decided to try a local mysql server instance instead of the embedded server. I deleted akonadi config and data again and setup mysql server with a database. It looked fine yesterday and everything was a bit faster. Today problems start again and the local maildir resource is offline again. WHAT in the world one could do to to get a stable Kmail with akonadi!? My akonadiserver.error is full of lines like these: "Cannot connect to agent instance with identifier 'akonadi_maildir_resource_0', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0': no such name'" "Cannot connect to agent instance with identifier 'akonadi_akonotes_resource_0', error message: 'Could not get owner of name 'org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_0': no such name'" Yesterday I deleted akonadi config and data again and set it up with embedded server. Sync with my IMAP accounts went fine and I was happy again. Today akonadi is unavailable and I can not use kontact. When I try to start manually I get the following: $ akonadictl start Unable to register service as "org.freedesktop.Akonadi.Control.lock" Maybe it's already running? "[ 0: /usr/bin/akonadi_control(_Z11akBacktracev+0x38) [0x43a738] 1: /usr/bin/akonadi_control() [0x43a9c2] 2: /lib64/libc.so.6() [0x3618e38490] 3: /lib64/libc.so.6(gsignal+0x39) [0x3618e38419] 4: /lib64/libc.so.6(abort+0x148) [0x3618e39778] 5: /usr/lib64/qt4/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x36290777d4] 6: /usr/bin/akonadi_control(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x43c91d] 7: /usr/lib64/qt4/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4) [0x3629110944] 8: /usr/lib64/qt4/libQtCore.so.4() [0x362911b5ef] 9: /usr/lib64/qt4/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x3629123b7b] 10: /usr/bin/akonadi_control(_ZN6QDebugD1Ev+0x30) [0x41c870] 11: /usr/bin/akonadi_control(main+0x34b) [0x41967b] 12: /lib64/libc.so.6(__libc_start_main+0xf5) [0x3618e24cb5] 13: /usr/bin/akonadi_control() [0x419841] ] " Error: akonadi_control was started but didn't register at D-Bus session bus. Make sure your system is set up correctly! And yes, akonadi is already running . But nothing happens. There are no errors logged in akonadiserver.error. So I kill akonadiserver, akonadi_control and mysqld. When I restart I seems ok but I get tons og messages (see attachment). Created attachment 82964 [details]
Output from akonadictl start
I can confirm this. On my machine, this happens: 1) Running KMail -> (Fine) 2) Fetching Mail from the servers -> (Fine) 3) But when I try to read any Mail, if I simply double click on any mail, then KMail window gets greyed out, and an error message about Akonadi's failure to fetch messages (not from the mail servers, from the local akonadi server, which ever it is) is printed. Then akonadi restarst itself and starts all over again (in an infinite loop). And this started to happen in KDE 4.13. This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Hi, same annoying problem. I am using OpenSuSE Tumbleweed, Kmail 5.3.0, Akonadi 16.08.1-1.4 akonadictl stats that akonadi is running, but kmail stop itself saying akonadi is not running. Messages are the same as the ones from the previous comments. Thanks for your reply, re-setting to confirmed. Same here with akonadi 16.12.0-1 / kmail 5.4.0 on Arch Linux. Me and other people were hit by this bug and the exact symptoms the OP describes after upgrading to akonadi 16.12.0-1 / kmail 5.4.0 around christmas on Arch Linux, see https://bbs.archlinux.org/viewtopic.php?id=221050. On closing kmail (after an unsuccessful read attempt of maildir items) akonadiserver crashes. akonadiserver chrash log is here: https://dl.dropboxusercontent.com/u/48919449/akonadiserver-crash-dbg-20170104.log Seems to be related to https://bugs.kde.org/show_bug.cgi?id=352701 I still have this problem accessing an existing maildir ressource with KMail 5.4.1 (KDE Applications 16.12.1.) on Arch. However, I saw akonadiserver crashing only once after updating KDE Applications. Currently the maildir ressource only is marked as broken and shown in red. In this respect, the situation has improved a little, as access to IMAP folders now stays possible after an unsuccessful read attempt without restarting KMail/Akonadi. For newly added maildir ressources I suffer from bug 294215, which may be related. |
I am unable to access emails in a local maildir. I've tried to remove the maildir resource via akonadiconsole - it gets re-added again, but still does not work. This blocks me from using kmail alltogether, even for IMAP, because 1) once I try to access the local folders, kmail refuses to work even with messagess in the IMAP account, but 2) even if I try to avoid accessing local folders, I can't use the IMAP account as deleting messages tries to move them into local trash, and sending an email tries to put it into local outgoing ... Reproducible: Always Steps to Reproduce: 1. run kmail 2. access a local folder which is not empty 3. try to select a message 4. run akonadiconsole 5. switch to browser tab 6. choose some local folder Actual Results: 2. you see the list of messages 3. you get "Stahuje se obsah složky" and "Prosím čekejte ..." and it sits there forever ("Downloading folder content" and "Please wait" or something like that) from this point on, the "please wait" message is shown for any folder/message 6. unlike in kmail, you don't even get the list of messages - it just shows the "working/waiting" animated icon next to the folder name forever Expected Results: 3. you see the contents of the email 6. you see the list of messages # rpm -qf /usr/lib64/kde4/akonadi_maildir_resource.so kdepim-runtime-4.10.3-3.fc19.x86_64 ... going to try downgrade