jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.65 was not provided by any .service files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I cannot get the nvidia drivers to work, so I had typed apt-get purge nvidia-current, then restarted my system. Once it had rebooted, I typed apt-get install nvidia-current into the terminal. The drivers started to install, then as the installation finished, errors started popping up on the screen.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-9-generic x86_64
.var.log.
Architecture: amd64
Date: Fri Aug 26 20:39:47 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
InterpreterPath: /usr/bin/python2.7
MachineType: System manufacturer System Product Name
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcCwd: /
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_GB:en
LANG=en_GB
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.
dmi.board.name: M4A87TD EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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.