| Summary: | app-office/akonadi-server-1.12.0: Unable to initialize database. "Column 'name' cannot be null QMYSQL3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Viacheslav Gagara <viacheslavg> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | optimusgd, randy-andy-, stephan.menzel |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugs.kde.org/show_bug.cgi?id=331867 | ||
| Whiteboard: | fixed in 1.12.2 | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
akonadiserver.error
mysql error mysql.conf |
||
|
Description
Viacheslav Gagara
2014-04-02 22:05:23 UTC
Created attachment 374120 [details]
akonadiserver.error
Created attachment 374122 [details]
mysql error
Created attachment 374124 [details]
mysql.conf
MySQL error observed in akonadiserver.error is: DATABASE ERROR: Error code: 1048 DB error: "Column 'name' cannot be null" Error text: "Column 'name' cannot be null QMYSQL3: Unable to execute statement" Query: "INSERT INTO PartTypeTable (ns, name) VALUES (:0, :1)" "Column 'name' cannot be null QMYSQL3: Unable to execute statement" Update failed Failed to commit transaction for database update Unable to initialize database. Possible workaround is to remove ~/.local/share/akonadi dir and restart akonadi service. Works fine for me. Please report this upstream and link back here. Respective bug from upstream: https://bugs.kde.org/show_bug.cgi?id=331867 IRC talk with an upstream maintainer. Just for the record... <johu> dvratil: is bug 331867 fixed in 1.12.1? <bugbot> KDE bug 331867 in Akonadi (server) "mysql: column 'name' can not be null when migrating PartTable" [Grave,Confirmed: ] http://bugs.kde.org/331867 <dvratil> johu, no, migration will still fail if there are invalid data in the database <johu> :/ <dvratil> johu, it would otherwise require inspecting every single record, which means that migration would take ages <johu> dvratil: so users on kde-4.13 will end up with broken akonadi if they dont know the workaround? <dvratil> yes. However their database is alraedy broken so there can be unexpected sideffects anyway Thanks for reporting. This is fixed in cvs now. Please sync in some hours to get the changes. + + 22 Apr 2014; Johannes Huber <johu@gentoo.org> + +akonadi-server-1.12.1-r1.ebuild, + +files/akonadi-server-1.12.1-db-initialize.patch, + -akonadi-server-1.12.1.ebuild: + Revision bump adds upstream patch which fixes db initialization error, bug + #506608. Remove old. + *** Bug 508442 has been marked as a duplicate of this bug. *** |
