> Martin Kho wrote: > > (1) errors during the start of akonadi > > Actual errors or just warnings? And are you still seeing them or was it > just a one-time instance? Errors, but they only showed up once, after I rebooted my system. I have: 1) mysql.err: (after KDE update and second reboot) 100224 12:09:39 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 2) mysql.err.old: (after KDE update and first reboot) 100224 11:19:57 [Note] Plugin 'ndbcluster' is disabled. InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 100224 11:19:57 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 100224 11:19:59 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 8 MB InnoDB: Database physically writes the file full: wait... 100224 11:19:59 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 8 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 100224 11:20:03 InnoDB: Started; log sequence number 0 0 100224 11:20:03 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 100224 11:20:03 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 100224 11:20:03 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.42-log' socket: '/home/martin/.local/share/akonadi/db_misc/mysql.socket' port: 0 Source distribution 100224 12:07:48 [Note] /usr/libexec/mysqld: Normal shutdown 100224 12:07:48 InnoDB: Starting shutdown... 100224 12:07:49 InnoDB: Shutdown completed; log sequence number 0 162468 100224 12:07:49 [Note] /usr/libexec/mysqld: Shutdown complete 4) akonadiserver.error.old: (after KDE update and first reboot) Control process died, committing suicide! > > > and (2) a messagebox that was telling me that nepumuk is disabled. > > See my reply to Timothy Murphy in the other thread for an explanation of > that one. (It's just a message intended to be informative (and not being > very successful at that, sadly), not an actual error.) Yes, saw that, but starting Nepomuk for the first time - after KDE update and reboot- it crashed. I filed a bug, see my previous post. Hope this helps. Martin Kho > > Kevin Kofler > > _______________________________________________ > kde mailing list > kde at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/kde > New to KDE4? - get help from http://userbase.kde.org
