Bug 865589
| Summary: | kmail reports that akonadi cannot be start (after a software upgrade) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Enrique <cquike> | ||||
| Component: | kdepim | Assignee: | Than Ngo <than> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-01 12:05:53 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
yum install akonadi-mysql How did you upgrade? Normally, the new subpackage should have been dragged in automatically by the upgrade (through Obsoletes). Hi, sorry for the late reply. I just did a yum upgrade, but the akonadi-mysql package wasn't pulled in. I now have installed F18 and I had a similar issue: I installed kdepim (yum install kdepim) in a F18 which didn't have any KDE software so far (I am using XFCE as my desktop) and it didn't install akonadi-mysql, I had to install it manually. Regards, Enrique Right, manually installing stuff is the one use case that won't get akonadi-mysql pulled in by default. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 625689 [details] Akonadi report Description of problem: After a software upgrade which included mysql-server, kdepim and several kde libraries, I cannot start kmail any more because akonadi failed to start. I have attached the report from the error window. Version-Release number of selected component (if applicable): mysql-libs-5.5.28-1.fc17.i686 mysql-server-5.5.28-1.fc17.i686 mysql-embedded-5.5.28-1.fc17.i686 mysql-5.5.28-1.fc17.i686 kdepimlibs-4.9.2-1.fc17.i686 kdepim-runtime-4.9.2-1.fc17.i686 kdepim-libs-4.9.2-1.fc17.i686 kdepimlibs-akonadi-4.9.2-1.fc17.i686 kdepim-runtime-libs-4.9.2-1.fc17.i686 kdepim-4.9.2-1.fc17.i686 How reproducible: Always, after the upgrade. However, I guess that it is reproducible only if using my "old" configuration. Maybe I can try to reproduce the error on a pristine account copying the relevant configuration files. Do you know which file should I include? Regards