Ubuntu
gwibber package

Gwibber not updating my feeds

Bug #862876 reported by Jono Bacon
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Fix Released
High
Ken VanDine
Ubuntu ubuntu-11.10

Bug Description

A few times now I have loaded Gwibber and it has not refreshed the feed (Twitter / identi.ca) with the latest people I am following and with mentions. I have also noticed that a few times, and this just happened now, when I post something it does actually get posted.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gwibber 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Thu Sep 29 16:31:21 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gwibber
UpgradeStatus: Upgraded to oneiric on 2011-07-13 (78 days ago)

Revision history for this message
Jono Bacon (jonobacon) wrote :
Ken VanDine (ken-vandine)
Changed in gwibber (Ubuntu):
milestone: none → ubuntu-11.10
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Ken VanDine (ken-vandine)
importance: Critical → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gwibber - 3.2.0-0ubuntu2

---------------
gwibber (3.2.0-0ubuntu2) oneiric; urgency=low

  * Reverted the change to dh_python2, it broke loading of the custom.py
    needed for setting the twitter API key (LP: #862876)
 -- Ken VanDine <email address hidden> Thu, 29 Sep 2011 21:32:07 -0400

Changed in gwibber (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Heimen Stoffels (vistaus) wrote :

Nope, the bug is still here after the update :(

Revision history for this message
Heimen Stoffels (vistaus) wrote :

Okay, so it works somewhat now. The Update Status still doesn't work. I don't like how that janitor always set things to Released before it's tested. It happens on more bugs and then after it's set to Fix Released, people find that the bug is still there. Just like here. Partially fixed is NOT Fix Released. You should really work on that Janitor.

Revision history for this message
James Hunt (jamesodhunt) wrote :

Bug definitely remains on 3.2.0-0ubuntu2 (3 days with no new tweets seems fairly suspicious :-).

Looking at my gwibber.log when I restart...

$ tail ~/.cache/gwibber/gwibber.log
2011-10-04 16:59:16,982 - Gwibber Service - INFO - Running from the system path
2011-10-04 16:59:31,387 - Gwibber Dispatcher - ERROR - Cannot parse message data: request
2011-10-04 16:59:31,388 - Gwibber Dispatcher - ERROR - Cannot parse message data: error
2011-10-04 16:59:31,415 - Gwibber Dispatcher - ERROR - Cannot parse message data: request
2011-10-04 16:59:31,416 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2011-10-04 16:59:32,960 - Gwibber Dispatcher - ERROR - Cannot parse message data: request
2011-10-04 16:59:32,960 - Gwibber Dispatcher - ERROR - Cannot parse message data: error
2011-10-04 16:59:34,364 - Gwibber Dispatcher - INFO - Loading complete: 1 - []
$

Revision history for this message
Ken VanDine (ken-vandine) wrote :

@jamesodhunt: that is definitely a different bug, please file a new bug and be sure to attach the gwibber log, preferably after running gwibber-service in debug mode for a little while.

killall -9 gwibber-service; gwibber-service -d

Revision history for this message
James Hunt (jamesodhunt) wrote :

@ken: bug 869838 raised.

Revision history for this message
James Hunt (jamesodhunt) wrote :

After multiple attempts, I eventually got gwibber going again by deleting ~/.cache/gwibber/, ~/.config/gwibber/ and re-adding my accounts.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.