We have worked to improve preventing this from happening since 1.3.x, however, an existing corrupt database could keep generating that error, and not all forms of uninstallation remove the old database. Quit Growl, then go to ~/Library/Containers/com.Growl.GrowlHelperApp/ Data/Library/Application Support/Growl/ in finder and remove or back up Notifications.history, and relaunch Growl. let us know if you continue having issues after letting it start fresh. Unfortunately we don't have any database repair functions in place to help fix an already corrupted database, but like I said, we have been working in 1.4 and 2.0 to improve reliability of the history database (which generally had issues due to not being able to save when the CPU spike/ hang occurred, which has been resolved)
On Feb 19, 6:48 pm, Ashwin Panchapakesan <[email protected]> wrote: > I had the same issue with 1.3.2. > I upgraded to 2.0.1, hoping that a fresh install would fix it, but alas, I > have had no such luck. > > Waiting anxiously for an answer > > > > > > > > On Saturday, May 5, 2012 12:44:02 PM UTC-4, BobMc wrote: > > > When growl starts I get the following error. The file > > "notifications.history" couldn't be opened because it isn't in the > > correct format. The file might be corrupt, truncated, or in an > > unexpected form. I am running growl 1.3.3. on Mac OS 10.7.3. Any help > > on how to correct this problem would be greatly appreciated. I have > > tried to find it with spotlight but nothing turns up in the search. > > > Thanks > > > Bob -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/growldiscuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
