[opensuse-kde] substitute mariadb with something working, to restore the functionality of kmail
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters..... So, I do not care much about "loosing data" when changing, as I have archives with the mail that can be re-imported. Somebody did write some mail I think on this list on how to do it, but I lost them (due to kmail/akonadi dataloss) about how to migrate, and now I asked myself if it is easy to accomplish and if there is a blog with a howto from somebody who did it. Help is welcomed as the current situation is not acceptable or functional any more. Thank you -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Il 24/09/2017 10:47, stakanov ha scritto:
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters..... So, I do not care much about "loosing data" when changing, as I have archives with the mail that can be re-imported. Somebody did write some mail I think on this list on how to do it, but I lost them (due to kmail/akonadi dataloss) about how to migrate, and now I asked myself if it is easy to accomplish and if there is a blog with a howto from somebody who did it. Help is welcomed as the current situation is not acceptable or functional any more. Thank you
Hi, you can surf all opensuse ML with a browser: https://lists.opensuse.org/ *IMHO*, the only good fix for kmail/akonadi is to get rid of them and move to thunderbird :( Bye, Daniele. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 24. September 2017, 14:22:14 CEST schrieb Daniele:
Il 24/09/2017 10:47, stakanov ha scritto:
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters..... So, I do not care much about "loosing data" when changing, as I have archives with the mail that can be re-imported. Somebody did write some mail I think on this list on how to do it, but I lost them (due to kmail/akonadi dataloss) about how to migrate, and now I asked myself if it is easy to accomplish and if there is a blog with a howto from somebody who did it. Help is welcomed as the current situation is not acceptable or functional any more. Thank you
Hi, you can surf all opensuse ML with a browser: https://lists.opensuse.org/
*IMHO*, the only good fix for kmail/akonadi is to get rid of them and move to thunderbird :(
not in all cases... For me the main source of trouble comes from the fact that ~ is on NFS for me. Both mariadb/mysql AND sqlite do NOT like that at all. But in case of akonadi I can just point it at my central database server, for thunderbird (and firefox) I had to kludge something together that rsyncs my profile into /dev/ shm and back to nfs at login/logout. therefor, YMMV indeed. cheers Mathias -- Mathias Homann Senior Systems Engineer, IT Consultant. IT Trainer Mathias.Homann@openSUSE.org http://www.tuxonline.tech gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
In data domenica 24 settembre 2017 10:47:58 CEST, stakanov ha scritto:
The combination of mariadb and kmail is (in my case, ymmv) totally non
YMMV indeed. I haven't seen a single issue with MariaDB + Akonadi in the last 3-4 years. That said, giving more details about your problems may help finding a fix for them. -- Luca Beltrame - KDE Forums Team GPG key ID: A29D259B -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data domenica 24 settembre 2017 14:33:59 CEST, Luca Beltrame ha scritto:
In data domenica 24 settembre 2017 10:47:58 CEST, stakanov ha scritto:
The combination of mariadb and kmail is (in my case, ymmv) totally non
YMMV indeed. I haven't seen a single issue with MariaDB + Akonadi in the last 3-4 years. That said, giving more details about your problems may help finding a fix for them. I have one substantial issue that, when hitting more then one local folder, get really troublesome. a) when the system was suspended, at wake-up, in a mixed set-up with pop and imap (form mailinglists) the messages will not displayed and a message below is shown: unable to fetch item (collection -1): unable to retrive item from resource: Multiple merge candidates, aborting.
You have then: exit kmail, open terminal, open akonadiconsole, clear the cache for the respective local subfolder. If more then one subfolder is hit, you need to do it for every f.... subfolder at a time, as multiple selection of subfolder has no effect, clear cache seems to work only folder per folder. You have then to close aconadiconsole (do not try to restart akonadi from it, as it is broken and will exit with a segfaul (already bug filed do bugzilla kde). When you now restart akonadi via console (akonadictl restart) then kmail, you will now have the messages in the folders, but about 20-50% in duplicates. Do not try "cartella" and then "rimovi duplicati". This just gives an error message, even if there are no subfolder. Use the second with mention of "subfolders". In about 50% of cases this will NOT clear the duplicates and you will have to eliminate them "by hand". If you do so, always take the first message of the duplicates. When eliminating the second duplicate in the row, both may go to the trash. But you do this because you want to get of the duplicates. Once you have done all this, you just have to wait for a few minutes. While writing a mail, the program will crash, the desktop will crash, all users open on that machine will crash, you are left with a black screen with a shimmering yellow stripe on the left side of the screen. That will vanish after a few (about 10) seconds. The machine will now switch off. (Bug reported as Bug 1053525 - System crashes to black screen and switchoff silently after coredump of kded, drkonqi and akonadi hanging?) to the opensuse bugzilla. When this happens you loose the last 10 lines of the mail you are writing. The rest opens as if the session would have been subject to snapshot, although the setting of plasma is "open an empty session, probably that means that the programm senses that it crashed. I have not managed to get any backtrace because this crash brings the house down. It is like glyposate, nothing survives, not even the user.... :-p When you have only pop and no(!) imap or mailing lists (my "post" user) then you will not experience this crash, but it will present multiple merge candidates when you leave the machine for long time in standby. It is also true that, when starting this user and checking mail too early when login in, the messages comming in will not be filtered. In order to enjoy filtering, you will have to close kontakt/kmail and log off and log in. Or (not really faster, you have to close the application, stop and restart akonadi, that will however not always grant the filter function. In this kind of setup the old regression that a pop up tells you that kmail does not know what to do with a certain filter (always an other, never the same) comes back on. Sometimes filter do work as follows: take as example a message from a vendor that you did whitelist. It will come in, will appear in inbox, then will be filtered to the subfolder, but the original will stay. If you click now on the subfolder you have 50% the message is readable, it signs read and the original in arrivals is now a unread duplicate. in 30% you click on the subfolder filtered message and it vanishes and the only one left is the one that is in arrival/arrivi). Now. in 20% you get multiple merge candidates and you cannot get any of the messages, or you can read one but it stays unread. Sometimes, if you do not read them, and you exit and then enter kmail, the message will appear correctly filtered without duplicate. Sometimes the following happens: you go to bed and switch off, the next morning you restart and find out you had mail.....albeit invisible. I call that function the "eastern egg function". During the writing of this mail I had two complete system crashes. If you say now: that is an old account... both user accounts where not migrated, the mails were achived in one case and reimported after a fresh user was set up. In the second case (the pop/imap) a new user was created and no messages was backported. As we speak I have data-loss, double messages, multiple merge candidates, and screwed up order of messages. You may now understand why I have a problem with this. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Op zondag 24 september 2017 10:47:58 CEST schreef stakanov:
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters..... So, I do not care much about "loosing data" when changing, as I have archives with the mail that can be re-imported. Somebody did write some mail I think on this list on how to do it, but I lost them (due to kmail/akonadi dataloss) about how to migrate, and now I asked myself if it is easy to accomplish and if there is a blog with a howto from somebody who did it. Help is welcomed as the current situation is not acceptable or functional any more. Thank you
I am using this combination already from the start. Occasionally, earlier, I sometimes needed to delete the database and had to reconfigure a few things, but the last half year I did not have any problem. I have about 14,000 messages in 5 imap servers. So, issues are solvable. -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 24. September 2017, 10:47:58 schrieb stakanov:
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters.....
I doubt that any of these problems are related to mariadb though, or that switching to mysql would help. Your main problem seems to be the "Multiple Merge Candidates" problem, which will prevent Akonadi to sync the affected folder at all. Dropping the cache will "fix" a "broken" folder as you know, but it will not prevent the problem from happening in the first place. Upstream bug reports would suggest that the main reason for this problem is mail filtering, see e.g. https://bugs.kde.org/show_bug.cgi?id=376808. It is a long standing problem that moving mails via filters can cause duplicates (e.g. https://bugs.kde.org/show_bug.cgi?id=283682), and I suspect these may be the cause of this (duplicates in the database may lead to this "Multiple Merge Candidates" error I think, if the duplicates have the same RID). So I'd say, try to disable automatic filering and see if it helps. There have been a few fixes in this regard in 17.08 to make it less likely to happen (AFAIK it's still not fixed completely), so maybe you could try uprading to the latest version too. I might be able to create testing packages based on the Leap 42.3 version with some fixes added if you prefer that. E.g. this 17.08 commit should improve filtering: https://phabricator.kde.org/D5667 And this would apparently prevent one reason for "Muliple Merge Candidates" to appear: https://cgit.kde.org/akonadi.git/commit/?id=0c0c2824374c45785b3d3754fc0b2647... (although I'm not sure at the moment if the latter one would apply to 17.04 or fixed a problem with later changes) The "data losses" you mentioned might be caused by deleting the caches, this will of course delete data that hasn't been synced back to the actual storage yet. Complete system crashes should not be able to be triggered by a user space application anyway, and rather point to problems at a lower level (kernel, graphics driver). Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 24. September 2017, 10:47:58 schrieb stakanov:
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters.....
I doubt that any of these problems are related to mariadb though, or that switching to mysql would help.
Your main problem seems to be the "Multiple Merge Candidates" problem, which will prevent Akonadi to sync the affected folder at all.
Dropping the cache will "fix" a "broken" folder as you know, but it will not prevent the problem from happening in the first place.
Upstream bug reports would suggest that the main reason for this problem is mail filtering, see e.g. https://bugs.kde.org/show_bug.cgi?id=376808. It is a long standing problem that moving mails via filters can cause duplicates (e.g. https://bugs.kde.org/show_bug.cgi?id=283682), and I suspect these may be the cause of this (duplicates in the database may lead to this "Multiple Merge Candidates" error I think, if the duplicates have the same RID).
So I'd say, try to disable automatic filering and see if it helps.
There have been a few fixes in this regard in 17.08 to make it less likely to happen (AFAIK it's still not fixed completely), so maybe you could try uprading to the latest version too. I might be able to create testing packages based on the Leap 42.3 version with some fixes added if you prefer that. E.g. this 17.08 commit should improve filtering: https://phabricator.kde.org/D5667 And this would apparently prevent one reason for "Muliple Merge Candidates" to appear: https://cgit.kde.org/akonadi.git/commit/?id=0c0c2824374c45785b3d3754fc0b2647 f691185d (although I'm not sure at the moment if the latter one would apply to 17.04 or fixed a problem with later changes) Nothing is worse than using an oss software that is even distributed with no cost and not contributing to its success. Be it my opportunity cost to try. As I would prefer to stick as close to the leap "base" as possible (which is the reason that this time I am using the standard kernel (and not kernel stable), I would agree to the testing package and maybe this might at the end help the everage leap user that encounters the problem. Please feel free to send me the
In data lunedì 25 settembre 2017 08:45:21 CEST, Wolfgang Bauer ha scritto: link to bug 1053525, I suggest this, since I mention the problem there. If this "fixes" is or not, it avoids duplication and once I see that the crashes are kernel related I will change the title accordingly. Of course if you agree, ymmv.
The "data losses" you mentioned might be caused by deleting the caches, this will of course delete data that hasn't been synced back to the actual storage yet. Possible, more possible that the data is lost when the system crashes violently. And still I have EXT4 and an SSD so quite conservative compared to other solutions. Complete system crashes should not be able to be triggered by a user space application anyway, and rather point to problems at a lower level (kernel, graphics driver). As I did write here I had another crash. And I have them only when writing in kmail/kontakt. So let us see if with the testpackages there is something getting better. And if not, then I will be the next best PITA when it comes to find out why the current kernel still crashes on Intel Ironlake. Thanks for letting me know.
Kind Regards, Wolfgang
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
In data lunedì 25 settembre 2017 09:36:49 CEST, stakanov ha scritto:
As I did write here I had another crash. And I have them only when writing in kmail/kontakt. So let us see if with the testpackages there is something
Be aware that the use of Qt Web Engine in kmail (basically a copy of Chromium's Blink rendering engine) may expose bugs in drivers (Noveau used to crash kmail all the time with it). I'm however not sure it's truly related. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: A29D259B
In data lunedì 25 settembre 2017 09:36:49 CEST, stakanov ha scritto:
As I did write here I had another crash. And I have them only when writing in kmail/kontakt. So let us see if with the testpackages there is something
Be aware that the use of Qt Web Engine in kmail (basically a copy of Chromium's Blink rendering engine) may expose bugs in drivers (Noveau used to crash kmail all the time with it).
I'm however not sure it's truly related. This could be related as the intel graphics driver I am using right now is surely not well maintained and the drm-kms package is not compatible at all. What else is comming to my mind, I have for that user, when I use sysguard up to 8 instances of QT webkit open. Could be that it crashes until it encounters
In data lunedì 25 settembre 2017 09:45:14 CEST, Luca Beltrame ha scritto: the "right" bug in the Intel driver. That would explain why it crashes practically exclusively during kmail use, especially when I have a full screen window open and (this is what I noticed) in the moment I press "space". Is there anything I could do to help to find the issue if this should be the case? P.S. while I am writing, I notice from time to time, black "blinks" (screen goes black for a fraction of second). Generally a sign that sooner or later the system will go down again. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 25. September 2017, 09:36:49 schrieb stakanov:
As I would prefer to stick as close to the leap "base" as possible (which is the reason that this time I am using the standard kernel (and not kernel stable), I would agree to the testing package and maybe this might at the end help the everage leap user that encounters the problem.
Well, trying the latest versions would show if your problems are already fixed upstream. If not, trying to backport patches would just be a waste of time anyway... But ok, let's try the kmail patch first, related to filtering. Please install the kmail package from here and report back whether it helps: https://download.opensuse.org/repositories/home:/wolfi323:/branches:/OBS_Mai... But just to be clear: if you already have a "Multiple Merge Candidate" problem, it will not be fixed by this. (according to the developers this cannot even be fixed afterwards without possible data loss, as Akonadi cannot determine which one of the multiple candidates would be the correct one) So, in that case, you'd need to wipe out the cache once more. AIUI, this patch should prevent duplicates caused by filtering though, or at least make them less likely. Also, as mentioned, I'd suggest to disable filters for some time to see if it is indeed related to that... (though if the above package fixes it, that's not necessary any more of course) Btw, may I mention that your mails/bugreports are really hard to read at times? I'd suggest to use more new lines/paragraphs, and/or leave out unrelated comments/rants... Thanks. ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday, 25 September 2017 07:45:21 BST Wolfgang Bauer wrote:
Am Sonntag, 24. September 2017, 10:47:58 schrieb stakanov:
The combination of mariadb and kmail is (in my case, ymmv) totally non functional and a disaster. Data loss, crashes (up to system crashes), multiple merge candidates, blocked filters.....
I doubt that any of these problems are related to mariadb though, or that switching to mysql would help.
Your main problem seems to be the "Multiple Merge Candidates" problem, which will prevent Akonadi to sync the affected folder at all.
Dropping the cache will "fix" a "broken" folder as you know, but it will not prevent the problem from happening in the first place.
Upstream bug reports would suggest that the main reason for this problem is mail filtering, see e.g. https://bugs.kde.org/show_bug.cgi?id=376808. It is a long standing problem that moving mails via filters can cause duplicates (e.g. https://bugs.kde.org/show_bug.cgi?id=283682), and I suspect these may be the cause of this (duplicates in the database may lead to this "Multiple Merge Candidates" error I think, if the duplicates have the same RID).
So I'd say, try to disable automatic filering and see if it helps.
This definitely helps, populate the inbox first then applying the filters afterwards has saved me a lot of duplication issues. But i still get the odd days where the inbox already contains duplicates before i apply filters.
There have been a few fixes in this regard in 17.08 to make it less likely to happen (AFAIK it's still not fixed completely), so maybe you could try uprading to the latest version too. I might be able to create testing packages based on the Leap 42.3 version with some fixes added if you prefer that. E.g. this 17.08 commit should improve filtering: https://phabricator.kde.org/D5667 And this would apparently prevent one reason for "Muliple Merge Candidates" to appear: https://cgit.kde.org/akonadi.git/commit/?id=0c0c2824374c45785b3d3754fc0b2647... (although I'm not sure at the moment if the latter one would apply to 17.04 or fixed a problem with later changes)
The "data losses" you mentioned might be caused by deleting the caches, this will of course delete data that hasn't been synced back to the actual storage yet.
Complete system crashes should not be able to be triggered by a user space application anyway, and rather point to problems at a lower level (kernel, graphics driver).
Kind Regards, Wolfgang
-- opensuse:tumbleweed:20170913 Qt: 5.9.1 KDE Frameworks: 5.37.0 KDE Plasma: 5.10.5 kwin 5.10.5 kmail2 5.6.1 akonadiserver 5.6.1 Kernel: 4.13.1-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (7)
-
Daniele
-
Freek de Kruijf
-
ianseeks
-
Luca Beltrame
-
Mathias Homann
-
stakanov
-
Wolfgang Bauer