gwibber-bugs team mailing list archive

[Sam Williams <sam-williams@xxxxxxxxxxx>]

I have encountered this problem on three separate computers. They are
running Ubuntu 10.04 or 10.10. This morning on a whim I tested a posting
again. Originally I thought the problem might be due to a message that
is too long and the character counter was simply incorrect. After closer
examination this was found not to be the case.

I finally started looking into the database itself. I ultimately decided
to perform a vacuum function on the file gwibber.sqlite located in
~/.config/gwibber. The command format used is as follows:

sqlite3 gwibber.sqlite Vacuum;

The current database increased in size by 18.432K after the vacuum
operation. So far everything I've posted since the vacuum has been
posted correctly to Twitter and Identi.ca. I will try this again if I
encounter posting problems with no other explanation.

Haven't really looked into the Gwibber code regarding this issue, but
you might want to think  about using the auto_vacuum pragma depending on
the nature of the problem.  http://goo.gl/1lqMF

Good Luck!

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/730244

Title:
  Gwibber 2.91.3 has stopped posting to Twitter

Status in Gwibber:
  New

Bug description:
  the development release of gwibber has stopped allowing me to post to
  Twitter. No errors have been seen, but the behavior is consistent
  across three different computers.