Gwibber-service use 100% of my 2 CPU and can't refresh facebook activity

Bug #652988 reported by Hadrien Dussuel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gwibber

I use Maverick 10.10, updated from Lucid 10.04. Gwibber never worked with my facebook account on this computer (i didn't tried so much to fix the problem on lucid). Now, when i try to launch it from the indicator-applet, gwibber-service use 100% of my dual core cpu, and don't manage to do anything.
---
Architecture: i386
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
NonfreeKernelModules: fglrx
Package: gwibber 2.32.0-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Tags: maverick
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

Please could you run in a terminal: "apport-collect -p gwibber 652988" for included more information, Thanks.

Changed in gwibber (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Hadrien Dussuel (dbkblk) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Omer Akram (om26er) wrote :

for gwibber not updating please see bug 614742 and read comment#37 in the duplicate bug and do the procedure. while the workaround it for adding the facebook account but I think it might work for the updating problem. (delete facebook account in gwibber first)

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

Hadrien, any news about it? have you checked Omer recomendations for get a workaround?

Revision history for this message
Hadrien Dussuel (dbkblk) wrote :

I'm sorry Kamus, i removed Ubuntu to move on Debian, because it is more stable and polished. I cannot test theses instructions anymore on an installation. However, i'll try to burn a livecd and to test the workaround in the coming days.

Revision history for this message
Hadrien Dussuel (dbkblk) wrote :

OK, i've tested the workaround n°37 at https://bugs.launchpad.net/bugs/614742. It don't apply to my problem.

I used a 10.10 i386 Live CD to test: I first updated gwibber and gwibber-service with the lastest update then added my facebook account as explained on the other thread. The fact is gwibber was already OK to add my account, but it does not show any element.

Moreover, gwibber-service shows 3 processes launched, and two of them take my each CPU to full load.

Here's the small log i can obtain by launching gwibber from console:
** (gwibber:7770): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:7770): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:7770): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
/usr/lib/python2.6/dist-packages/gwibber/gwui.py:726: GtkWarning: IA__gtk_range_set_range: assertion `min < max' failed
  self.scrollbar.set_range(0, len(self.messages) - 1)
Exception AttributeError: "'NoneType' object has no attribute 'px_proxy_factory_free'" in <bound method ProxyFactory.__del__ of <libproxy.ProxyFactory object at 0x9e252ac>> ignored

Any idea ?

Revision history for this message
Omer Akram (om26er) wrote :

the facebook-no-updating issue have been fixed to quite an extent for many users and the issue will be fully fixed with time since facebook was stopping our traffic. there are a few bug reports for the high CPU usage and its preferable that a bug report should report a single issue. I am closing this bug and if you happen to use ubuntu again and any bug affects you then feel free to report :-)

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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