gwibber-service (version 2.29.92) crashed with ServerError in _request()

Bug #547050 reported by GaryW
58
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

Gwibber crash. I am aware that there are other bug reports (see end of this comment) about Gwibber crashes but having looked that the traceback, it is not the same. May be because I am running version 2.29.92.1-0ubuntu1 of Gwibber.

Here is some supporting information:
   Thu Mar 25 16:11:07 GMT 2010
   : #gnubyexample@amd754n(/) ;cat /etc/*elease*;date;dpkg -l | grep gwibber;date;file /sbin/init;date;uname -a
   DISTRIB_ID=Ubuntu
   DISTRIB_RELEASE=10.04
   DISTRIB_CODENAME=lucid
   DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"
  Thu Mar 25 16:12:16 GMT 2010
   ii gwibber 2.29.92.1-0ubuntu1 Open source social networking client for GNO
   ii gwibber-service 2.29.92.1-0ubuntu1 Open source social networking client for GNO
   Thu Mar 25 16:12:16 GMT 2010
   /sbin/init: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
   Thu Mar 25 16:12:17 GMT 2010
   Linux amd754n 2.6.32-17-generic #26-Ubuntu SMP Fri Mar 19 23:58:53 UTC 2010 i686 GNU/Linux

The development version of Lucid I am running is, I think, perhaps beta1 (installed from repositories 24th March) and apt-cache shows Gwibber is most recent version available right now:

: #gnubyexample@amd754n(/) ;apt-cache policy gwibber
gwibber:
  Installed: 2.29.92.1-0ubuntu1
  Candidate: 2.29.92.1-0ubuntu1
  Version table:
 *** 2.29.92.1-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Here is a simple grep that will show if a similar bug report looks to be the same as what I am reporting here.

: #gnubyexample@amd754n(/) ;egrep '(client\.py|microblog|in module|create=True|ctx=ctx)' /var/crash/*gwibber*.* | wc -l
8
: #gnubyexample@amd754n(/) ;date;egrep '(client\.py|microblog|in module|create=True|ctx=ctx)' /var/crash/*gwibber*.*;date
Thu Mar 25 16:11:07 GMT 2010
     from gwibber.microblog import dispatcher
   File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 41, in <module>
   File "/usr/lib/python2.6/dist-packages/gwibber/microblog/util/couch.py", line 64, in __init__
     self.database = CouchDatabase(dbname, create=True)
     server_class=server_class, oauth_tokens=oauth_tokens, ctx=ctx)
   File "/usr/lib/pymodules/python2.6/couchdb/client.py", line 124, in __contains__
   File "/usr/lib/pymodules/python2.6/couchdb/client.py", line 981, in head
   File "/usr/lib/pymodules/python2.6/couchdb/client.py", line 1035, in _request
Thu Mar 25 16:11:07 GMT 2010

If you get a result other than 8 from running...
      egrep '(client\.py|microblog|in module|create=True|ctx=ctx)' /var/crash/*gwibber*.* | wc -l
then your bug is probably not the same as this one or you are running a different version of Gwibber.

Other bug reports which might have some relevance, but might have been encountered at Lucid alpha stage or seem to
have a different traceback:
  https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/523829
  https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/528286
  https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/537111

ProblemType: Crash
Architecture: i386
Date: Thu Mar 25 15:36:15 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InterpreterPath: /usr/bin/python2.6
Package: gwibber-service 2.29.92.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.utf8
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with ServerError in _request()
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare staff

Revision history for this message
GaryW (gnubyexample) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Revision history for this message
Victor Vargas (kamus) wrote :

@GaryW, Please could you test under latest version of gwibber (2.29.94) if this problem is still affecting you? Thanks in advance!

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
GaryW (gnubyexample) wrote :

Running a fully updated Lucid Beta today 6th April, and I am not seeing this error now that the
gwibber versions are 2.29.94

Tue Apr 6 15:46:07 BST 2010
Linux amd754n 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux
gwibber:
  Installed: 2.29.94-0ubuntu1
  Candidate: 2.29.94-0ubuntu1
  Version table:
 *** 2.29.94-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
gwibber-service:
  Installed: 2.29.94-0ubuntu1
  Candidate: 2.29.94-0ubuntu1
  Version table:
 *** 2.29.94-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Feels like Gwibber is really getting there and I think it will be a big hit when the final Ubuntu Lucid
is released at end of April :)

Gwibber does take quite a chunk of memory (70 meg) on my machine so might be a consideration for
anyone attempting to run Lucid on a very memory limited netbook, but I think the functionality is really rich,
and most users will be running on desktops and laptops where 70MB for one program is negligible.

I did experience an separate (and very minor) issue with Gwibber today (#556553) but on the whole it seems to
work really well for my twitter.

Revision history for this message
Victor Vargas (kamus) wrote :

Please keep an eye on your report and if you encounter this issue reappears please don't hesitate and reopen this report again, for now I will mark such Fixed Released. Thanks!

Changed in gwibber (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
mikbini (mikbini) wrote :

I'm reopening this as this morning when I logged in after a reboot I got a crash with the same backtrace (except for really slight changes due to different versions, I'm using 2.30.0.1-0ubuntu1). I also got bug #563554 and bug #583685, all at once.

Changed in gwibber (Ubuntu):
status: Fix Released → In Progress
status: In Progress → Confirmed
Revision history for this message
Omer Akram (om26er) wrote :

Please report a new bug if you face the crash again. the title does not mean you are facing the same crash

Changed in gwibber (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
mikbini (mikbini) wrote :

Ok, I filed bug #583737.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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