← Back to team overview

desktop-packages team mailing list archive

[Bug 602001] Re: jockey-gtk crashed with GError in show_notification()

 

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/602001

Title:
  jockey-gtk crashed with GError in show_notification()

Status in “jockey” package in Ubuntu:
  New

Bug description:
  This bug is similar or the same as #187529 jockey-gtk crashed with
  GError in show_notification(), but this happened with live cdrom
  version of ubuntu 10.04.  The live cdrom system was booting when this
  error appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: jockey-gtk 0.5.8-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  Architecture: i386
  Date: Mon Jul  5 18:26:30 2010
  ExecutablePath: /usr/bin/jockey-gtk
  InterpreterPath: /usr/bin/python2.6
  LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 002 Device 002: ID 046d:c526 Logitech, Inc. MX Revolution Cordless Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 04b4:1002 Cypress Semiconductor Corp. CY7C63001 R100 FM Radio
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Sony Corporation PCV-RX470DS(UC)
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/ubun/casper/vmlinuz file=/cdrom/ubun/preseed/hostname.seed boot=casper live-media-path=/ubun/casper initrd=/ubun/casper/initrd.lz quiet splash -- maybe-ubiquity
  ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/jockey-gtk', '--check']
  SourcePackage: jockey
  Title: jockey-gtk crashed with GError in show_notification()
  Traceback:
   Traceback (most recent call last):
     File "/usr/bin/jockey-gtk", line 216, in show_notification
       notify.show()
   GError: 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.
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 04/25/2001
  dmi.bios.vendor: Award Software, Inc.
  dmi.bios.version: ACPI BIOS Revision 1004
  dmi.board.name: WMT-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: REV 1.xx
  dmi.chassis.asset.tag: R47000000000400000000000
  dmi.chassis.type: 7
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrACPIBIOSRevision1004:bd04/25/2001:svnSonyCorporation:pnPCV-RX470DS(UC):pvr28400230:rvnASUSTeKComputerINC.:rnWMT-LE:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
  dmi.product.name: PCV-RX470DS(UC)
  dmi.product.version: 28400230
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/602001/+subscriptions