This forum has been archived. All content is frozen. Please use KDE Discuss instead.

KMail2: quo vadis?

Tags: None
(comma "," separated)
dyle
Registered Member
Posts
6
Karma
0

KMail2: quo vadis?

Fri Sep 28, 2012 9:26 am
Hi *,

Sorry to say that, but I got to have to tell at least someone, somewhere about my frustrations on kmail2. :(

See, I've been on KDE since 3.2 AFAIR. And KMail has been the best every EMail Client out there. The featureset is just great! Evolution, Thunderbird? No way.

This was before Akonadi.

Then people decided it was time for the "semantic desktop" thingie. And there it went. I don't want Nepomuk. I don't use it. I simply have no need for it. Now, Akonadi tries to provide a common engine for all personal information messaging data: email, contacts, etc. This comes with indexing and all other goodies.

But as Akonadi is very buggy, it renders KMail2 completely useless.

Just like this:
Code: Select all
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QSqlDatabasePrivate::removeDatabase: connection 'initConnection' is still in use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'initConnection' is still in use, all queries will cease to work.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Nepomuk Query Server not available
search paths:  ("~/bin", "/sbin", "/usr/sbin", "/usr/local/sbin", "~/bin", "/sbin", "/usr/sbin", "/usr/local/sbin", "/usr/local/bin", "/usr/bin", "/bin", "/opt/bin", "/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3", "/opt/android-sdk-update-manager/tools", "/opt/android-sdk-update-manager/platform-tools", "/opt/android-ndk-r4b", "/usr/games/bin")
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
search paths:  ("/usr/lib64/kde4/plugins", "/home/dyle/.kde4/lib64/kde4/plugins/", "/usr/lib64/kde4/plugins/", "/usr/lib64/qt4/plugins", "/usr/bin", "/home/dyle/.kde4/lib64/kde4/", "/usr/lib64/kde4/")
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
"/usr/bin/akonadi_nepomuk_feeder(10272)" Soprano: "Could not connect to server at /tmp/ksocket-dyle/nepomuk-socket (No such file or directory)"
"/usr/bin/akonadi_nepomuk_feeder(10272)" Soprano: "Could not connect to server at /tmp/ksocket-dyle/nepomuk-socket (No such file or directory)"
"/usr/bin/akonadi_nepomuk_feeder(10272)" Soprano: "Could not connect to server at /tmp/ksocket-dyle/nepomuk-socket (No such file or directory)"
"/usr/bin/akonadi_nepomuk_feeder(10272)" Soprano: "Could not connect to server at /tmp/ksocket-dyle/nepomuk-socket (No such file or directory)"
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
ItemRetrieverException :  Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(Though, a WebMail Frontend works very happy with the very same IMAP Server ...)

So, in order to have KMail, I have to have a bloated Akonadi, which in turn got to have a running bloated Nepomuk, which I don't want. In other words: in order to write an email to my wife, I have to allow some totally unrelated application to search through all my harddrive for any documents and items it thinks, would interest me in future, for I'm to much of a moron to structure my folders and files in a reasonable way and to remember this. *sigh*

Other times the akonadi IMAP agent simply crashes. Or it sticks to its own cached data pretending to have them in sync, but they are not (checked the files on the IMAP server: no files, whereas akonadi showed me a plenty bunch of emails there ...).

Worst: KMail2 is somehow decoupled with akonadi. When akonadi has seem unsusal problem, KMail2 seems not to get notified about.

My current setup is this:
- 3 IMAP-Server-Accounts
- 1 Local Mail Account.

* When I start up KMail2 it tries to synchrionize all folders. As I do have 2000 of them in sum on the IMAP-Accounts this takes ages.
* In the meanwhile KMail2 shows me "Retrieving folder content ... please wait"
* Then - on a regular basis - akonadi crashes in the background, leaving KMail2 in the "Retrieving folder content ... please wait" state.
* If I'm lucky (2 out of 5 attempts) I actually _can_ view an email. But this is after some minutes of useless synchronizations.

KMail has been one of the best applications out there. KMail2 is just unsuable. :'(
This is since KMail2 has been introduced into the KDE 4.x mainline. It immediately drove me off and switching to Thunderbird. Once in while I desperately miss the features of KMail and give new versions of Akonadi/KMail2 a chance. To no success this far.

It's a shame. Does anyone know about a KMail1 branch for KDE 4, one without Akonadi?

This is KDE 4.9.1
karthikp
Registered Member
Posts
109
Karma
0
OS

Re: KMail2: quo vadis?

Fri Sep 28, 2012 3:57 pm
Perhaps you may have to clear out some old configurations from your machine. I use kmail everyday and while the transition to akonadi was rocky to say the least, I don't have the sort of issues you're describing.

I particularly want to remark that kmail doesn't freeze up when checking for mail (seems to be a totally different thread/process).

Clearing out your configuration is a bit trickier now with akonadi. First, stop akonadi by typing akonadictl stop into a terminal or into krunner. You may also stop akonadi using its kcm, if you prefer the gui approach. Akonadi stores its configs in ~/.config/akonadi/ and its files in ~/.local/share/akonadi/. kmail may also have some data in ~/.kde/share/apps/kmail or ~/.kde4/share/apps/kmail (depending upon your distribution). You may also do well to clear out kmail configuration files in ~/.kde (or kde4)/share/config/kmailrc or some such file. Clean it all out and if you did it all correctly, you can restart akonadi and add your imap accounts and start fresh.


karthikp, proud to be a member of KDE forums since 2008.
Image
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: KMail2: quo vadis?

Sat Sep 29, 2012 7:14 am
The errors are simply the various bits of KDE PIM trying to connect to Nepomuk (and since you're not running it, it fails, but it doesn't affect the rest of the program). I don't see the issues you experience here for retrieving mails and what not (and I have 5 accounts with about 40K messages).

I would suggest as well to try this under a new user account.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
muesli joe
Registered Member
Posts
1
Karma
0

Re: KMail2: quo vadis?

Sun Feb 10, 2013 3:45 am
hey,
i'm having exactly the same problems with kmail2.
i need neither nepomuk nor akonadi to structure my pc
while both of them run me down all the time.
(i understand why people think, they are usefull. but if you don't need them, they are a big pain in the a**)

i'm aswell interessted, if there's some kind of fork, branch... anything that runs kmail without akonadi/nepomuk
greetings
joe
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: KMail2: quo vadis?

Sun Feb 10, 2013 10:15 am
I'm starting to get annoyed about such threads popping up everywhere in the KDE Community Forums.

Please bear in mind a number of points:

  • This particular area of the forum is for user support, so it's the wrong place for opinions. Use Discussions and Opinions.
  • The KDE Code of Conduct and the forum rules must be abided at all times, hence call something "piece of..." is not allowed at any time ("Be respectful", the first heading in the Code of Conduct).
  • It is perfectly fine to disagree (even developers can disagree on things, as the archives in the KDE mailing list show) and to be dissatisfied, even strongly, but you have to bear in mind the above points when posting.
  • Also, cooling off and presenting the "pain points" in a reasoned, non-ranting perspective is much more apt to get good feedback than this "lecture-like" post.

Locking this thread.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]