← Back to team overview

desktop-packages team mailing list archive

[Bug 826992] Re: 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.

 

*** This bug is a duplicate of bug 734376 ***
    https://bugs.launchpad.net/bugs/734376

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 #734376, 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

** Attachment removed: "Dependencies.txt"
   https://bugs.launchpad.net/bugs/826992/+attachment/2281200/+files/Dependencies.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/826992/+attachment/2281206/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/826992/+attachment/2281208/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 734376
   jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply in shutdown()

** 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/826992

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.

Status in “jockey” package in Ubuntu:
  New

Bug description:
  Description:	Ubuntu oneiric (development branch)
  Release:	11.10

  jockey-gtk:
    Installed: 0.9.3-0ubuntu1
    Candidate: 0.9.3-0ubuntu1

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: jockey-gtk 0.9.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Mon Aug 15 23:30:53 2011
  ExecutablePath: /usr/bin/jockey-gtk
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  InterpreterPath: /usr/bin/python2.7
  MachineType: LENOVO 01976GG
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
  ProcEnviron:
   PATH=(custom, user)
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic root=UUID=2c0a3ceb-037a-473b-b9f1-db586c79a6fe 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: Upgraded to oneiric on 2011-08-15 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6ZET33WW (1.20 )
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr6ZET33WW(1.20):bd09/10/2010:svnLENOVO:pn01976GG:pvrThinkPadEdge:rvnLENOVO:rnINVALID:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 01976GG
  dmi.product.version: ThinkPad Edge
  dmi.sys.vendor: LENOVO

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