jockey-gtk crashed with DBusException in call_blocking()

Bug #489682 reported by Mario Limonciello on 2009-11-28
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Undecided
Unassigned

Bug Description

Just booting into the live session on the media.

ProblemType: Crash
.var.log.jockey.log:

Architecture: i386
CurrentDmesg: [ 44.801856] eth0: no IPv6 routers present
Date: Sat Nov 28 19:01:18 2009
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Mythbuntu 10.04 "Lucid Lynx" - Alpha i386 (20091128)
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
MachineType: innotek GmbH VirtualBox
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/mythbuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-5.6-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-5-generic i686
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:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Mario Limonciello (superm1) wrote :

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 #403955, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers