gwibber-bugs team mailing list archive

[Ken VanDine <ken.vandine@xxxxxxxxxxxxx>]

I am reasonably sure this was fixed.  Please re-open if you experience
it again.

** Changed in: gwibber
       Status: Confirmed => Fix Released

** Changed in: gwibber
     Assignee: Gwibber Team (gwibber-team) => (unassigned)

** Changed in: gwibber
       Status: Fix Released => Incomplete

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

Title:
  UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0:
  unexpected end of data

Status in Gwibber:
  Incomplete
Status in “gwibber” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gwibber

  According to bug 530195 the problems in Gwibber should have been fixed
  in 2.30.1, but no such luck. Both the Facebook and Twitter support are
  broken, rendering Gwibber useless for me.

  I just upgraded from Karmic to Lucid. I now have Gwibber 2.30.1
  running on my system, and things have gone from bad to worse. Whereas
  previously it was just Facebook that was working only sporadically,
  Twitter has now stopped working for me as well.

  I had a Flickr account, a Facebook account and a Twitter account
  configured in Gwibber, yet the Message screen remains completely
  empty. No Twitter or Facebook messages are displayed, even after
  manually selecting Refresh. On the Home screen the only things that
  are displayed are Flickr photos, and Twitter messages that are
  @directed at me.

  I've attached a log file of a gwibber -d run. As you can see it
  complains that the com.Gwibber.Accounts and com.Gwibber.Streams
  services are not not provided by any service files. That sounds bad.

  I have already tried deleting every Gwibber-related settings directory
  and cache directory I could find, but none of it made any difference.
  I also tried removing and re-adding my accounts (during which I
  discovered that it is actually impossible to add a Facebook account
  anymore! I'll file a separate bug for that), but that made no
  difference either.