SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I tried to run KMail today, and it doesn't run, stating that the Akonadi server is not running. Manually starting Akonadi with
Code:
akonadictl start
yields the following output:
Code:
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl: done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
~ $ org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial connection!
org.kde.pim.akonadiserver: executable: "/usr/libexec/mysqld"
org.kde.pim.akonadiserver: arguments: ("--defaults-file=/home/ltlnx/.local/share/akonadi/mysql.conf", "--datadir=/home/ltlnx/.local/share/akonadi/db_data/", "--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: ""
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
I tried starting /etc/rc.mysqld manually, and it started successfully, but Akonadi still throws the same error. Has anyone encountered this problem? TIA.
you can try enabling the sql server connection on kde startup and see if it behaves better this way.
Edit the file "$HOME/.config/akonadi/akondiserverrc" and put/modify the line in the end like this:
Code:
StartServer=true
I keep it set to false so the server doesn't start, since i do not use kde PIM applications, but i remember when i installed slackware last time that it was starting fine and i had functional pim applications (functional in the sense that they were starting fine and not complaining about akonadi not running etc.). This was some months ago though, don't know if something else broke in the meantime.
@giomat: I just checked the file and StartServer is set to true. It also worked for me a few weeks ago; wonder if an akonadi downgrade would help.
Edit: No it didn't, but more searching indicates that downgrading mariadb might help (and mariadb was last updated on March 9, which matches my monthly upgrade schedule)
Last edited by litelinux; 04-05-2023 at 03:14 AM.
Reason: add info
I downgraded mariadb with mariadb-10.6.12-x86_64-2.txz (from the trusty slackware.uk/cumulative/ archive), and akonadi worked. Maybe there's some regressions with akonadi?
Can you check the contents of cat /home/<your username>/.local/share/akonadi/db_data/mysql.err ?
It could contain the exact error that is preventing mysql from starting.
If that is the case, you can try to start with a clean config:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.