Ubuntu
oneconf package

oneconf-query crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.137 was not provided by any .service files

Bug #842348 reported by justin curtis mathews on 2011-09-06

This bug report is a duplicate of: Bug #839286: oneconf-query crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.75 was not provided by any .service files. Edit Remove

This bug affects 1 person

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

Bug Description

crashed upon update/upgrade.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: oneconf 0.2.6.1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Mon Sep 5 22:52:11 2011
ExecutablePath: /usr/share/oneconf/oneconf-query
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/oneconf-query --async-update
ProcCwd: /
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/oneconf-query', '--async-update']
SourcePackage: oneconf
Title: oneconf-query crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.137 was not provided by any .service files
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

justin curtis mathews (jmate31) wrote on 2011-09-06:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-06: 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 #839286, 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.