Ubuntu
jockey package

jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Bug #748999 reported by Shahid Ghafoor on 2011-04-03

This bug report is a duplicate of: Bug #657829: jockey-gtk crashed with DBusException in call_blocking(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	jockey (Ubuntu)	New	Undecided	Unassigned

Bug Description

its not starting at all in Natty.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: jockey-gtk 0.9.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
.var.log.jockey.log: 2011-04-03 15:34:26,589 DEBUG: Updating repository indexes...
Architecture: i386
Date: Sun Apr 3 15:43:39 2011
ExecutablePath: /usr/bin/jockey-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110402)
InterpreterPath: /usr/bin/python2.7
MachineType: ECS 945P-A
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
LANGUAGE=en_US:en
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=6a61110f-46f8-4de3-9e34-6881bbd104c1 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/jockey-gtk']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/24/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080012
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 945P-A
dmi.board.vendor: ECS
dmi.board.version: 1.X
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.X
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd07/24/2006:svnECS:pn945P-A:pvr1.X:rvnECS:rn945P-A:rvr1.X:cvnECS:ct3:cvr1.X:
dmi.product.name: 945P-A
dmi.product.version: 1.X
dmi.sys.vendor: ECS

Tags:

Revision history for this message

Shahid Ghafoor (shahid.ghafoor) wrote on 2011-04-03:

BootDmesg.txt Edit (43.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Devices.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (484 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.7 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (1.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (111.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (225.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-04: This bug is a duplicate

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.