abrt version: 1.1.18 architecture: i686 cmdline: /usr/bin/python /usr/bin/gwibber-service component: gwibber executable: /usr/bin/gwibber-service kernel: 2.6.35.13-92.fc14.i686.PAE package: gwibber-1:3.1.0-1.fc14 reason: dispatcher.py:824:__init__:AttributeError: 'ConnectionMonitor' object has no attribute 'nm' release: Fedora release 14 (Laughlin) time: 1309252286 uid: 500 backtrace ----- dispatcher.py:824:__init__:AttributeError: 'ConnectionMonitor' object has no attribute 'nm' Traceback (most recent call last): File "/usr/bin/gwibber-service", line 77, in <module> connection_monitor = dispatcher.ConnectionMonitor() File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 824, in __init__ log.logger.debug("NM Version is %s", str(self.nm.Get(NM_DBUS_INTERFACE, "Version"))) AttributeError: 'ConnectionMonitor' object has no attribute 'nm' Local variables in innermost frame: NM_DBUS_SERVICE: 'org.freedesktop.NetworkManager' NM_DBUS_INTERFACE: 'org.freedesktop.NetworkManager' bus_name: <dbus.service.BusName com.Gwibber.Connection on <dbus._dbus.SessionBus (session) at 0x9404f8c> at 0x941286c> NM_DBUS_OBJECT_PATH: '/org/freedesktop/NetworkManager' self: <gwibber.microblog.dispatcher.ConnectionMonitor at /com/gwibber/Connection at 0x941284c> comment ----- Appears to be fixed in gwibber trunk, but this worked for me: --- dispatcher.py~ 2011-06-14 20:50:09.000000000 +0100 +++ dispatcher.py 2011-06-28 10:27:21.000000000 +0100 @@ -817,7 +817,7 @@ self.nm.connect_to_signal("StateChanged", self.on_connection_changed) self.has_nm = True except: - pass + return self.NM_STATE_UNKNOWN = 0 How to reproduce ----- 1. Don't have NetworkManager installed. 2. Try to run gwibber.
Created attachment 510232 [details] File: backtrace
*** Bug 719963 has been marked as a duplicate of this bug. ***
Package: gwibber-1:3.1.0-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. login to gnome session 2. gwibber crash 3.
Package: gwibber-3.1.0-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Happens every time I start GWibber (along with another (known) crash reported 10 seconds ago by me). THis referrences NetworkManager. I have NM installed but not running (chkconfig NetworkManager off) since it interferes with the bridge network setup I use on this machine.
Pretty similar with previous post. Package: gwibber-3.1.0-2.fc14.noarch Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Happens every time I start GWibber. I have NetworkManager installed but not running (chkconfig NetworkManager off) since it interferes with the bridge network setup I use on this machine.
Gwibber can not start. Looks like it need NetworkManager, but I don't have NetworkManager because it's not friendly enough with my ISCSI configuration. Package: gwibber-3.1.0-3.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.