On Sunday 22 February 2009 17:16:57 Rex Dieter wrote: > Kevin Kofler wrote: > > Clive Messer wrote: > >> Akonadi wouldn't start for me after updating f10 from > >> kde-redhat-unstable. I think this was due to the change to its mysql db > >> size. > > > > Well, then unfortunately this looks like we have to revert this change > > and stay with the original default size forever. Having to delete all > > your PIM data is not an acceptable solution. > > the change as introduced should only affect *new* akonadi db's, old ones > should be unaffected. > Rex, today I decided it was time I took a look at this. Akonadi has not been used before, so should be one of your "new" dbs. I get the same error as others have reported, I think - log file .ib_logfile0 is of different size 0 67108664 than specified in the .cnf file 0 8388608 Anne -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : http://lists.fedoraproject.org/pipermail/kde/attachments/20090223/4ce69085/attachment.bin
