oneconf-query crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.122 was not provided by any .service files
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oneconf (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
To reproudce install the 0316 dialy iso amd64 to my ssd with manual pration and ext4 partion.
I have not heard of this package before but it said it crashed.
Descriptiopn Ubuntu Vivid Vervet (development branch )
Release : 15.04
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: oneconf 0.3.7
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 16 21:22:36 2015
DbusErrorAnalysis: no service file providing :1.122
ExecutablePath: /usr/share/
InstallationDate: Installed on 2015-03-17 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150316)
InterpreterPath: /usr/bin/python3.4
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: oneconf
Title: oneconf-query crashed with dbus.exceptions
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Lyn Perrine (walterorlin) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| Changed in oneconf (Ubuntu): | |
| importance: | Undecided → Medium |
| information type: | Private → Public |
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 #1106232, 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.