Gwibber stops working after suspending
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Confirmed
|
Undecided
|
Ken VanDine | ||
gwibber (Ubuntu) |
Confirmed
|
Medium
|
Ken VanDine |
Bug Description
After suspending and waking up the computer, starting gwibber (from daily-ppa) only produces the following error:
Updating...
Traceback (most recent call last):
File "/usr/bin/gwibber", line 62, in <module>
client.Client()
File "/usr/lib/
self.w = GwibberClient()
File "/usr/lib/
if len(json.
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
File "/usr/lib/
retval = candidate_
File "/usr/lib/
for account in self.accounts.
File "/usr/lib/
exists = self.view_
File "/usr/lib/
view_container = self.db[
File "/usr/lib/
resp, data = self.resource.
File "/usr/lib/
return self._request(
File "/usr/lib/
resp, data = _make_request()
File "/usr/lib/
body=body, headers=headers)
File "/usr/lib/
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/lib/
(response, content) = self._conn_
File "/usr/lib/
conn.connect()
File "/usr/lib/
raise socket.error, msg
error: [Errno 111] Connection refused
To get it working again I have to manually kill gwibber-service.
This is from 2.29.1~
Changed in gwibber: | |
milestone: | none → 2.30.0 |
Changed in gwibber (Ubuntu): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
importance: | Undecided → Medium |
milestone: | none → ubuntu-10.04-beta-1 |
status: | New → Confirmed |
Changed in gwibber (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in gwibber: | |
status: | Confirmed → Fix Committed |
Changed in gwibber (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in gwibber: | |
status: | Fix Committed → Fix Released |
Changed in gwibber: | |
status: | Fix Released → Confirmed |
I have the exact same issue.