On my everyday computer, Akonadiserver did not work, other users same problem. In Myrlyn, I downgraded mariadb from version 11.8.6.160000.1.1-x86_64 to the previous version 11.8.5.160000.3.1-x86_64 and now Kontact and KMail is working again. Now I still have to block possible updates - which I am used to because of nvidia troubles … To whom it may concern …
But that is only a temporary by-pass, not a solution!.
You should file a bug report, because this should be repaired. Or do you want to stick to that old version into the far future?
With pleasure. How do I file such a bug report?
Information: https://en.opensuse.org/openSUSE:Submitting_bug_reports
Login with the same username/password as here: https://bugzilla.opensuse.org/index.cgi
And it is a good habit to post a link to your report here in the thread so that others can follow it and maybe add information to it.
I have filed bug report in https://bugzilla.opensuse.org/show_bug.cgi?id=1263659
1 Like
This is a bug in Akonadi that is incompatible with this version of MariaDB.
It has already been reported for Debian.
MariaDB isn’t THE problem…
the bug is solved in mariadb when I read the debian bugreport.
mariadb 11.8.6 was published before the bugreport was published…
Please don’t spread false reports. Nothing has been fixed in SUSE yet. The bug has merely been confirmed!
2 Likes
I also confirm this is the case on my setup. Akonadi is not working.
Hi all
My Leap [16.0] Akonadi has also decided to suddenly permanently die as of today.
The Akonadi Server crashes anytime that Kmail etc. is trying to load.
I have updates set to happen daily.
Sounds like the same problem as above?
Unfortunately I am not getting any luck with getting a debug trace to confirm this…
According to the above: I see the MariaDB needs to be downgraded.
However I cannot find MariaDB in Discover in order to do this.
Any help would be appreciated as email is very useful!
Thanks,
Andrew
I do not quite understand you. Of course everybody, including you, has he same problem when they updated to that version. There is no use for everybody to confirm they experience the same as all others and which is confirmed in the bug description and will be solved.
Also the by-pass is mentioned above, thus better follow that so you can work and wait for the patch.
Use Myrlyn not Discover for this. Assuming you have only standard repos search in Myrlyn for mariadb then select in the Versions tab the version 11.8.5-160000.3.1, accept the downgrade in the conflict resolution and install the older version. After that search for mariadb in Myrlyn and set “Protect - Do not modify” for it.
1 Like
Thanks Henk
Sorry. I wasn’t very clear…
I was trying to get the debug packages in place & working so that any future bugs experienced could be checked to see if they had been reported.
The problem with mariadb has now been resolved temporarily as per instructions given in the next message.
I presume the notice for a working patch will arrive in this message list when it happens!
Andrew
Thanks very much rawar
I have followed your concise instructions and Kmail is now back on deck!
Most appreciated.
Andrew
Update has solved it:
rpm -qa mariadb
mariadb-11.8.6-160000.2.1.x86_64
Maybe the TO @PolderPenguin can now mark this topic as Solved by the above post.
1 Like
The problem is now SOLVED officially! New update with version 11.8.6.160000.2.1-x86_64 can be installed and is working fine.
But not here. And only you, as Topic Owner, can do this. Thus please click in the Solved button in the post that did it.
1 Like
Thanks. I clicked on the “Solution” button below the last message and it turned green. I hope this was the right way to do it.