[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)

2019-07-31 Thread Sid Hymes
https://bugs.kde.org/show_bug.cgi?id=409341

Sid Hymes  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Sid Hymes  ---
All attempts to obtain necessary files thru Fedora were unsuccessful. I
therefore removed the entire kde-pim suite and reinstalled which corrected the
problem. I noticed a few days later that some of the offending files had been
updated (by Fedora) and it is unknown whether this would have resolved the
problem.

I have therefore marked the bug as resolved.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)

2019-06-30 Thread Sid Hymes
https://bugs.kde.org/show_bug.cgi?id=409341

--- Comment #3 from Sid Hymes  ---
"Details" button is non-responsive so cannot generate self-test report and
don't know of another way to generate the self-test results.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)

2019-06-30 Thread Sid Hymes
https://bugs.kde.org/show_bug.cgi?id=409341

Sid Hymes  changed:

   What|Removed |Added

 CC||sidhy...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)

2019-06-30 Thread Sid Hymes
https://bugs.kde.org/show_bug.cgi?id=409341

--- Comment #2 from Sid Hymes  ---
Response to starting Akonadi manually:
akonadictl start (06/30/19 11:40:21)
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[sid@hallie ~]$ org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Failed to use database "akonadi"
org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server
through socket '/tmp/akonadi-sid.T04dCL/mysql.socket' (2) QMYSQL: Unable to
connect"
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.T04dCL/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…

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 409341] Unable to start stable version of akonadi server or file bug report (Fedora 30)

2019-06-30 Thread Sid Hymes
https://bugs.kde.org/show_bug.cgi?id=409341

--- Comment #1 from Sid Hymes  ---
Created attachment 121247
  --> https://bugs.kde.org/attachment.cgi?id=121247=edit
Missing, but not really, files

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 409341] New: Unable to start stable version of akonadi server or file bug report (Fedora 30)

2019-06-30 Thread Sid Hymes
https://bugs.kde.org/show_bug.cgi?id=409341

Bug ID: 409341
   Summary: Unable to start stable version of akonadi server or
file bug report (Fedora 30)
   Product: Akonadi
   Version: 5.11.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sidhy...@gmail.com
  Target Milestone: ---

Created attachment 121246
  --> https://bugs.kde.org/attachment.cgi?id=121246=edit
Crash information from bug reporter

SUMMARY
Kontact, etc., report Akonadi as not being operational. Attempts to start
result in large error messages. Attempts to file bug report result in error
message that required files are not present; presence confirmed in specified
location. Crash information (attached) deemed "not useful". All problems
occurred after recent Fedora update.

STEPS TO REPRODUCE
1. Start Kontact.
2. Kontact/KOrganizer opens with error message that akonadi not operational.
3. Manually starting akonadi results in repeated crash reports.
4. Use of system requires stopping akonadi.
5. See kdepim-users Digest, Vol 187, Issue 10 for additional details.

OBSERVED RESULT
Repeated crashes of akonadi and disabling of reliant apps.

EXPECTED RESULT
No crashes.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 30, most recent versions
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.