gwibber-service crashed with IOError in get_avatar_path()

Bug #626068 reported by Rodolfo Augusto Manzoli
66
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Medium
Ken VanDine
gwibber (Ubuntu)
Fix Released
Medium
Ken VanDine

Bug Description

Binary package hint: gwibber

gwibber-service crashed with IOError in get_avatar_path()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
Date: Sat Aug 28 20:36:11 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia:

InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with IOError in get_avatar_path()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
Rodolfo Augusto Manzoli (rmanzoli88) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Victor Vargas (kamus) wrote :

@Rodolfo, Please could you run under latest version of gwibber: gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!

visibility: private → public
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Rodolfo Augusto Manzoli (rmanzoli88) wrote :

Hey!
Basically that's it!
Thanks :D

Revision history for this message
Rodolfo Augusto Manzoli (rmanzoli88) wrote :

now when i opened the gwibber client,

Gwibber Dispatcher: ERROR Loading failed: - Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 231, in run
    pool.map_async(self.func, self.iterable, callback=self.callback).get(timeout=self.timeout)
  File "/usr/lib/python2.6/multiprocessing/pool.py", line 418, in get
    raise TimeoutError
TimeoutError

Revision history for this message
Rodolfo Augusto Manzoli (rmanzoli88) wrote :
Download full text (42.6 KiB)

And after a long time...

Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <STATS> facebook:responses account:facebook-rodolfoaugustomanzoli since:2010-09-04 19:26:58.00 size:778
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <facebook:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: INFO Loading complete: 25 - []
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Finished operation
Gwibber Dispatcher: DEBUG <twitter:user_messages> Performing operation
Gwibber Dispatcher: ERROR Twitter failure - Rate limit exceeded. Clients may not make more than 350 requests per hour.
Gwibber Dispatcher: DEBUG <twitter:user_messages> Fini...

Changed in gwibber:
assignee: nobody → Ken VanDine (ken-vandine)
importance: Undecided → Medium
milestone: none → 2.31.92
status: New → Fix Committed
Changed in gwibber (Ubuntu):
status: Incomplete → Triaged
assignee: nobody → Ken VanDine (ken-vandine)
milestone: none → ubuntu-10.10
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gwibber - 2.31.92-0ubuntu1

---------------
gwibber (2.31.92-0ubuntu1) maverick; urgency=low

  * New upstream release
    - Don't crash if there are streams configured for accounts that no longer
      exist (LP: #631263)
    - Delete associated streams when an account is deleted
    - Reuse worker pool of threads (LP: #624918)
    - Ensure the timer is reset on each refresh, prevents multiple timers
      created to perform the refresh operations causing crashes (LP: #600010)
    - Clicking on the message indicator should focus replies (LP: #549817)
    - When focusing replies stream from the indicator, clear the
      indicators (LP: #629623)
    - gwibber-service crashed with IOError in get_avatar_path() (LP: #626068)
    - gwibber-service crashed with GError in notify() (LP: #622812)
  * debian/gwibber-service.py
    - Added apport package-hook to attach the gwibber.log (LP: #384552)
 -- Ken VanDine <email address hidden> Fri, 03 Sep 2010 15:06:17 -0400

Changed in gwibber (Ubuntu):
status: Triaged → Fix Released
Changed in gwibber:
status: Fix Committed → Fix Released
Revision history for this message
jamie ellis (novaserve) wrote :

same error, but occurs once on login - only.

/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
  import gobject._gobject

Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

Revision history for this message
Luiz Augusto (luizaugustopc) wrote :

the bug has happend few seconds after logon under Ubuntu 12.10 b2 updated

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.