gwibber-accounts crashed with TypeError in __init__(): Gtk.Window.set_icon_from_file() argument 1 must be string, not None

Bug #824267 reported by surasit
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

menu account && nothing action!! after click so gwibber useless for now

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber 3.1.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Wed Aug 10 23:18:16 2011
ExecutablePath: /usr/bin/gwibber-accounts
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: python /usr/bin/gwibber-accounts
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-accounts']
SourcePackage: gwibber
Title: gwibber-accounts crashed with TypeError in __init__(): Gtk.Window.set_icon_from_file() argument 1 must be string, not None
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/gwibber-accounts", line 112, in <module>
     accounts.GwibberAccountManager(selected_account=selected_account, condition=condition, message=message)
   File "/usr/lib/python2.7/dist-packages/gwibber/accounts.py", line 58, in __init__
 TypeError: Gtk.Window.set_icon_from_file() argument 1 must be string, not None
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #814259, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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