jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.70 was not provided by any .service files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Wanting to access the 'additional drivers' via system settings menu gave me a bug (Bug #831754 ). While getting the information I got this bug. Maybe a result of filing the previous bug or just an independent bug.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-9-generic i686
.var.log.
Architecture: i386
CurrentDmesg: [ 61.752566] init: plymouth-stop pre-start process (1744) terminated with status 1
Date: Thu Aug 25 16:51:45 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
InterpreterPath: /usr/bin/python2.7
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
MachineType: innotek GmbH VirtualBox
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: Upgraded to oneiric on 2011-08-11 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
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 #657829, 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.