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

[Robert Ross]

Private bug reported:

1) $ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2) $ apt-cache policy oneconf
oneconf:
  Installed: 0.2.6.9
  Candidate: 0.2.6.9
  Version table:
 *** 0.2.6.9 0
        500 http://ca.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

3), 4) Apport brought me here. I am unaware of the exact nature of the
issue. I noticed no difference in the operation of the machine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: oneconf 0.2.6.9
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Thu Apr 5 16:27:21 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/share/oneconf/oneconf-query
ExecutableTimestamp: 1329723997
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/oneconf-query --async-update
ProcCwd: /
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.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.763 was not provided by any .service files
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #974700, 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.