Comment 7 for bug 1040554

I also have the problem that every other day Lightread reaches that limit even though I’ve already set very low limits in the settings. Then it won’t update anymore, and I can also often observe the extreme hard drive activity. What also happens is that entries that I mark read with gReader on my phone remain unread in Lightread. To solve the issue I have to delete everything under databases/, otherwise I usually (but not always) get the white screen issue.

For now I temporarily worked around it by deleting everything and setting it up anew, then closing Lightread, creating a git repo inside databases/, committing the content, and always starting Lightread with this script:

$ cat /usr/local/bin/lightread
#!/bin/bash
cd ~/.local/share/webkit/databases/ && git reset --hard && cd -
/opt/extras.ubuntu.com/lightread/bin/lightread

As long as Lightread is the only application using this local storage, that shouldn’t have any nasty side effects. Whenever it behaves weirdly or I suspect that someone else might already have read a number of ostensibly unread entries, I just restart it.

But I hope it’ll be fixed soon anyway. :-)