Kmail: moving posts occasionally results in spontaneous copies

JZL240I-U · 03-17-2015, 04:54 AM

This is on SUSE 13.2, all software updated to the current versions.

I fetch my mails with POP3 to remove them from the provider's grasp. Thus they come to rest in my inbox where I read them and subsequently move them by drag and drop to appropriate subdirectories.

In doing so, kmail requires one to press <shift> (copying would be <ctrl>). Alternatively, after the initial drag and drop (without pressing <shift>) a context menu appears, where one can chose "move" out of three choices.

Any way moving is executed, occasionally(!) a copy will re-appear in the inbox after some seconds of delay. What causes this and how can I stop it?

unSpawn · 04-12-2015, 05:02 AM

No idea. Try purging the original mail from the source folder with SHIFT+DEL or restarting kmail or clearing the akonadi cache using 'akonadiconsole'. Else search for related akonadi / kmail(2) bugs and file report at bugs.kde.org?

//NTLB

JZL240I-U · 04-13-2015, 01:13 AM

Sure I can move the original and then delete the copy. I might as well copy the original to its final destination and delete the original itself

. It's still a hassle. I'll try aconadiconsole next. There are bug reports on this but it was also reported fixed...

P.S.: What is //NTLB standing for? http://acronyms.thefreedictionary.com/NTLB doesn't really help here...

JZL240I-U · 04-13-2015, 01:10 PM

There is no akonadicontrol in the SUSE repositories. I tried akonadi_console which resulted in

Code:

Unable to register service as "org.freedesktop.Akonadi.Control.lock" Maybe it's already running?
"[
0: akonadi_control(_Z11akBacktracev+0x37) [0x43d347]
1: akonadi_control() [0x43d5a2]
2: /lib64/libc.so.6(+0x35200) [0x7fad86f02200]
3: /lib64/libc.so.6(gsignal+0x37) [0x7fad86f02187]
4: /lib64/libc.so.6(abort+0x118) [0x7fad86f03538]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7fad87f362b4]
6: akonadi_control(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x43f75d]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7fad87fd05b0]
8: /usr/lib64/libQtCore.so.4(+0x120bdd) [0x7fad87fdfbdd]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7fad87fe87c1]
10: akonadi_control(_ZN6QDebugD1Ev+0x39) [0x41c379]
11: akonadi_control(main+0x36d) [0x41870d]
12: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fad86eeeb05]
13: akonadi_control() [0x4188af]
]
"

That of any help?

unSpawn · 04-13-2015, 04:39 PM

Could be called akonadi_control ?

JZL240I-U · 04-14-2015, 11:54 AM

Quote:

Originally Posted by unSpawn

Could be called akonadi_control ?

Yeah, sorry, that's what I used, it's spelled wrong in my earlier post.
"akonadi_control" gives the messages I already posted ("akonadi_console" just produces cnf / command not found).

unSpawn · 04-15-2015, 03:29 PM

Sorry. Then I don't know. Check the KDE bug tracker for fixes or else file a bug report?