Since the update to kmail 4.8.0 kmail constantly switched to offline mode. Everytime I check for mail manually it ask whether I'd like to switch online.

It gets even more annoying when I try to send a mail: It stays in the outbox and I can't even select "send queued mails" from the menu as it is gray. There is a workaround here at least: Open the mail again, hit send, then kmail asks a different question: "The mail dispatcher is offline, mails can not be send. Do you want to make it online ?" I click yes and then I can select "send queued mails" from the menu and it finally sends the mail.

Any idea how to fix this? This should be reported as I bug I guess? Which output is needed? A log file from akonadi I assume, as kmail is pretty quiet when started from the shell.

Thanks!

It seems that Akonadi believes your system is offline. How do you connect to your local network / the internet? It seems that it is recieving false information - possibly from NetworkManager.

I'm using kde Networkmanager... What if the network is not available when akonadi starts? It should get the right information later anyway right? Because that's weird even after a mail check it's immediately offline again...

Is this acceptable?

Code: Select all

"/usr/bin/kmail(15443)" Soprano: "QLocalSocket::connectToServer: Connection refused"
"/usr/bin/kmail(15443)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"
"/usr/bin/kmail(15443)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(15443)" Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"
"/usr/bin/kmail(15443)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(15443)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(15443)" Soprano: "Invalid iterator."

Maybe it's just because I disabled nepomuk option to index all mails and their attachments?

https://bbs.archlinux.org/viewtopic.php?id=135361

These commands do "fix" the issue:

Code: Select all

killall -9 kded4
kded4 & disown


https://bugs.kde.org/show_bug.cgi?id=294441

It should not be necessary to restart kded4. Once the network becomes available, Akonadi should be aware of that and immediately resume network enabled operation.

Please see viewtopic.php?f=18&t=97685&p=207005&hilit=qdbus#p207005 for a possibly more elegant solution, which should cause less disruption to the desktop.