Ubuntu
oneconf package

oneconf-query crashed with DBusException in new(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-drsAvbIJac: Connection refused

Bug #834321 reported by Anders Feder on 2011-08-26

This bug report is a duplicate of: Bug #832029: oneconf-query crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-K1WLhe4GXe: Connection refused. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	oneconf (Ubuntu)	New	Undecided	Unassigned

Bug Description

Crashed (twice) at login.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: oneconf 0.2.5
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Fri Aug 26 04:41:23 2011
ExecutablePath: /usr/share/oneconf/oneconf-query
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/oneconf-query --update
ProcEnviron:
LANGUAGE=da:en
PATH=(custom, no user)
LANG=da_DK.UTF-8
LC_MESSAGES=da_DK.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/oneconf-query', '--update']
SourcePackage: oneconf
Title: oneconf-query crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-drsAvbIJac: Connection refused
UpgradeStatus: Upgraded to oneiric on 2011-08-26 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Anders Feder (afeder) wrote on 2011-08-26:

Traceback.txt Edit (734 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-26: 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 #832029, 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.