Bug 1729705 - Akonadi fails to use database "akonadi" and KDE PIM components unusable
Summary: Akonadi fails to use database "akonadi" and KDE PIM components unusable
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-plasma-akonadi-calendars
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-13 19:28 UTC by Sid Hymes
Modified: 2019-07-13 19:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Sid Hymes 2019-07-13 19:28:08 UTC
Description of problem:
On akonadictl start
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)akonadiserver reports starting up, then fails to use akonadi database, reporting 
Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-sid.L25wuG/mysql.socket' (2) QMYSQL: Unable to connect", then 
org.kde.pim.akonadiserver: Failed to connect to database!
org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-sid.L25wuG/mysql.socket' (2) QMYSQL: Unable to connect"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...

Version-Release number of selected component (if applicable):

akonadi-1.13.0-113.fc30.x86_64

How reproducible:
initiating akonadi server after KDE Pim components fail to start.

Steps to Reproduce:
1. akonadictl start
2. (see above for error messages)

Actual results:

KDE PIM inoperable

Expected results:

Access to KDE PIM components Korganizer, KAlarm, etc.

Additional info: Reinstalled KDEPIM, akonadi, kf5-akonadi-server-mysql, mariadb, mariadb-server, rebooted, all to no effect.


Note You need to log in before you can comment on or make changes to this bug.