[MASTER] gwibber-service crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-0ZC7xQ8Eu0: Connection refused

Bug #752061 reported by Anduu on 2011-04-05
206
This bug affects 34 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: gwibber

.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber-service 2.91.93-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.40-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Tue Apr 5 17:34:33 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110322.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-0ZC7xQ8Eu0: Connection refused
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Anduu (anduu) wrote :
tags: removed: need-duplicate-check
Kamus (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.

This will help us to find and resolve the problem.

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
visibility: private → public
Omer Akram (om26er) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Launchpad Janitor (janitor) wrote :

[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.]

Changed in gwibber (Ubuntu):
status: Incomplete → Expired
tags: added: bugpattern-needed
summary: - gwibber-service crashed with DBusException in __new__():
+ [MASTER] gwibber-service crashed with DBusException in __new__():
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp
/dbus-0ZC7xQ8Eu0: Connection refused
tags: removed: bugpattern-needed
tags: added: bugpattern-written
Matthias Schmidt (mschmidt) wrote :

Can confirm this with latest oneiric from today on amd64. Gwibber and gwibber-server are in Version 3.1.90-0ubuntu2

Changed in gwibber (Ubuntu):
status: Expired → Confirmed
Christer (christer-madsen) wrote :

Using Ubuntu 11.10 beta current and Gwibber crashed while not even open...

Paul White (paulw2u) wrote :

Running Precise 12.04 here, rebooted due to kernel updates.

On starting Unity I opened a terminal window and was then greeted by a gwibber-service crash dialog.

tags: added: precise
tags: added: oneiric
Bilal Shahid (s9iper1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better,
 this should be fixed in the upcoming 3.3.4 release.

Changed in gwibber (Ubuntu):
status: Confirmed → Invalid
Bilal Shahid (s9iper1) on 2012-02-10
Changed in gwibber (Ubuntu):
status: Invalid → Incomplete
Adam Niedling (krychek) wrote :

Bilal: why did you change the status first to Invalid then to Incomplete? If the bug is fixed why not change it to Fix commited or released?

Changed in gwibber (Ubuntu):
status: Incomplete → Confirmed
Ken VanDine (ken-vandine) wrote :

There are lots of bug reports that all lead back to dbus timeouts and connection failures. We didn't necessarily address each one, however as of 3.3.4 there shouldn't be any more blocking in the gwibber-service. So in theory we shouldn't see any more of these types of vague issues that are really hard to pin point.

After much debate and many opinions, we agreed to mark all the bug reports that we think should be fixed by this as incomplete with the hope that if the reporter sees it again after 3.3.4 the bug gets re-opened.

Changed in gwibber (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers