Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Unfortunately, this bug report is about a DBus client
failing to connect with the DBus backend and to really understand the
issue we need the crash from the DBus backend not from the client.
Client crashes are prevented from being report by apport in Precise and
in the event that the backend crashes apport should report those ass
separate.  Because of the previously stated reasons I am setting this
bug report to Invalid.

** Changed in: jockey (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: jockey (Ubuntu)
   Importance: Medium => Low

-- 
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/752892

Title:
  jockey-text crashed with DBusException in call_blocking():
  org.freedesktop.DBus.Error.NoReply in handler_info()

Status in “jockey” package in Ubuntu:
  Invalid

Bug description:
  I tried to search for an application shortly after I rebooted.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: jockey-common 0.9.2-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Wed Apr  6 22:05:04 2011
  ExecutablePath: /usr/bin/jockey-text
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
  InterpreterPath: /usr/bin/python2.7
  MachineType: Dell Computer Corporation Dimension 2400
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/jockey-text -l
  ProcEnviron:
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
   LANGUAGE=nl_NL:en
   PATH=(custom, no user)
   LC_MESSAGES=C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=ecf3e064-a7c4-4891-b0fd-97ba77286830 ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/bin/jockey-text', '-l']
  SourcePackage: jockey
  Title: jockey-text 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: 12/02/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A05
  dmi.board.name: 0F5949
  dmi.board.vendor: Dell Computer Corp.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA05:bd12/02/2003:svnDellComputerCorporation:pnDimension2400:pvr:rvnDellComputerCorp.:rn0F5949:rvrA01:cvnDellComputerCorporation:ct15:cvr:
  dmi.product.name: Dimension 2400
  dmi.sys.vendor: Dell Computer Corporation

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to