ich habe ein plötzliches akonadi Problem seit dem Upgrade auf KDE 4.13.2.
- Code: Alles auswählen
Starting Akonadi Server...
done.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/usr/local/bin", "/usr/bin", "/usr/games", "/usr/lib64/qt4/bin", "/home/robel/bin", "/usr/lib64/qt5/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
[robel@viper-thinkpad ~]$ akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.servers OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
MySQL version OK (required "5.1" , available "10.0" )
Database "akonadi" opened using driver "QMYSQL"
DbInitializer::run()
checking table "SchemaVersionTable"
checking table "ResourceTable"
checking table "CollectionTable"
checking table "MimeTypeTable"
checking table "PimItemTable"
checking table "FlagTable"
checking table "PartTypeTable"
checking table "PartTable"
checking table "CollectionAttributeTable"
checking table "TagTable"
checking table "TagAttributeTable"
checking table "TagRemoteIdResourceRelationTable"
checking table "PimItemFlagRelation"
checking table "PimItemTagRelation"
checking table "CollectionMimeTypeRelation"
checking table "CollectionPimItemRelation"
DbInitializer::run() done
skipping update 2
skipping update 3
skipping update 4
skipping update 8
skipping update 10
skipping update 12
skipping update 13
skipping update 14
skipping update 15
skipping update 16
skipping update 17
skipping update 18
skipping update 19
skipping update 20
skipping update 21
skipping update 22
skipping update 23
skipping update 24
skipping update 25
skipping update 26
Updating indexes
"CREATE UNIQUE INDEX CollectionTable_parentAndNameIndex ON CollectionTable (parentId,name)"
ein Test mit einem neuen "frischen Benutzer" ergibt das selbe Problem. Es sieht also aus, als ob der Server beim Anlegen der Datenbank spinnt.
Hat hierfür jemand einen Lösungsansatz?
