Summary: | Can not start Akonadi | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | Patrice Grundmann <patrice.grundmann> |
Component: | Packages User Edition | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | critical | CC: | dvratil, jr, neon-bugs, rikmills, sitter, sknauss, tonal.promsoft |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Akonadi selftest report |
Description
Patrice Grundmann
2018-10-03 17:24:36 UTC
I can reproduce this on Neon 18.04 user edition on a fresh install, and using Kubuntu CI builds of apps/akonadi stable 18.08 branch. (1) I am not sure it was intentional for Neon to switch to mariadb. This may be a result of the packaging for the mysql backend having: Depends: libqt5sql5-mysql, mysql-client-core-5.6 | virtual-mysql-client-core, mysql-server-core-5.6 | virtual-mysql-server-core, whereas mysql 5.6 package do not exist in Bionic (5.7 is there) so mariadb gets pulled in instead. (2) This looks very similar to https://bugs.kde.org/show_bug.cgi?id=392948 which was supposedly fixed. I would note that the same result and workaround mkdir -p ~/.local/share/akonadi/db_data/ before starting akonadi for the 1st time, works with both mariadb on Neon and mysql on Kubuntu. Testing with Kubuntu 18.01 daily iso with akonadi 18.04.3, and all starts ok. (In reply to Rik Mills from comment #2) > Testing with Kubuntu 18.01 daily iso with akonadi 18.04.3, and all starts ok. Should read Cosmic 18.10. Correction. Akonadi 18.04.3 on Cosmic 18.10 fails to start also, using mysql 5.7 https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1797643 18.08.1 also fails to start on debian unstable with mariadb in a similar manner. Now also reported in Debian (Cheers Ian) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910902 Can you please test with Akonadi 18.08? The issue should be fixed there. https://cgit.kde.org/akonadi.git/commit/src/server/storage/dbconfigmysql.cpp?id=a3d9f7647bf36a35deb996516ebd84f88976f013 A working workaround is to install mariadb-server than my_print_defaults gets installed. But this doesn't feel like a good solution, we should better make sure that my_print_defaults gets to mariadb-server-core. Additionally I needed to replace: rm /usr/sbin/mysqld-akonadi ln -s /usr/sbin/mysqld /usr/sbin/mysqld-akonadi still an issue for 18.08.1. @dvratil so you check does not help here, because we need my_print_defaults in both cases. I can recreate this using KDE neon user edition ISO from today, the ISO image must be installed (not live) to get the problem For now I've added in this more permissive change to apparmour permissions from kubuntu which seems to stop the first-run error https://launchpadlibrarian.net/393075010/akonadi_4%3A18.04.3-0ubuntu1_4%3A18.04.3-0ubuntu2.diff.gz Switching to a symlink as suggested by Sandro may make more sense. I'm unclear what this stuff about mariadb is about. the apparmour update has now been deployed and testing on virtualbox and docker with new installs kontact runs fine Can this closed? Let's mark this as fixed, as now Debian has fixed it with 4:18.08.3-2: https://salsa.debian.org/qt-kde-team/kde/akonadi/commit/1f280c0dc23cae507ccf1ffd306123c6330700af and KDE Neon with: https://launchpadlibrarian.net/393075010/akonadi_4%3A18.04.3-0ubuntu1_4%3A18.04.3-0ubuntu2.diff.gz |