Bug 1196226 - Akonadictl start failled
Summary: Akonadictl start failled
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: akonadi
Version: 20
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-25 14:19 UTC by Danilo Marcucci
Modified: 2015-11-02 01:38 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:11:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output from akonadictl start >akonadictl.txt 2>&1 (20.68 KB, text/plain)
2015-02-25 14:19 UTC, Danilo Marcucci
no flags Details
Screenshot from Akonadi server (67.09 KB, image/jpeg)
2015-03-04 16:55 UTC, Danilo Marcucci
no flags Details

Description Danilo Marcucci 2015-02-25 14:19:46 UTC
Created attachment 995222 [details]
Output from akonadictl start >akonadictl.txt 2>&1

Description of problem:
I have installed fedora 20 and used my home from fedora 19. When starting an application that used akonadi as Kmail, Knoted, ... failled stratup

Version-Release number of selected component (if applicable):
$ akonadictl --version
Akonadi 1.13.0


How reproducible:
$ akonadictl start

Steps to Reproduce:
1.$ akonadictl start
2.
3.

Actual results:
I can't using Kamil, Knote, etc.

Expected results:
Using Kamil, Knote, etc.


Additional info:

Comment 1 Rex Dieter 2015-02-25 14:26:35 UTC
This looks like the mysql failure (from the log):

...
Adding new foreign key constraints 
"ALTER TABLE PartTable ADD FOREIGN KEY (pimItemId) REFERENCES PimItemTable(id) ON UPDATE CASCADE ON DELETE CASCADE" 
Updating index failed:  
Sql error: Cannot add or update a child row: a foreign key constraint fails (`akonadi`.`#sql-557_d2`, CONSTRAINT `#sql-557_d2_ibfk_1` FOREIGN KEY (`pimItemId`) REFERENCES `pimitemtable` (`id`) ON DELETE CASCADE ON UPDATE CASCADE) QMYSQL: Unable to execute query
Query: ALTER TABLE PartTable ADD FOREIGN KEY (pimItemId) REFERENCES PimItemTable(id) ON UPDATE CASCADE ON DELETE CASCADE 
""
Unable to initialize database.

Comment 2 Danilo Marcucci 2015-03-04 16:55:52 UTC
Created attachment 997979 [details]
Screenshot from Akonadi server

Sceenshot from Akonadi server

Comment 3 Fedora End Of Life 2015-05-29 13:42:38 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-30 00:11:10 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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