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
crash!
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelMo
.var.log.
Architecture: i386
CurrentDmesg:
[ 24.466606] Bluetooth: RFCOMM socket layer initialized
[ 24.466608] Bluetooth: RFCOMM ver 1.11
[ 24.472243] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 24.472246] Bluetooth: BNEP filters: protocol multicast
[ 28.016003] eth0: no IPv6 routers present
Date: Fri Aug 26 17:12:57 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
MachineType: BIOSTAR Group TA770E
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
PATH=(custom, no user)
LANG=ru_RU.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-26 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.
dmi.board.name: TA770E
dmi.board.vendor: BIOSTAR Group
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: dmi:bvnAmerican
dmi.product.name: TA770E
dmi.sys.vendor: BIOSTAR Group
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.