Ubuntu
jockey package

jockey-kde crashed with dbus ServiceUnknown error in call_blocking (KDE PolicyKit agent not available)

Bug #274189 reported by Ben Bethge
38
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Fix Released
High
Martin Pitt
Ubuntu ubuntu-8.10

Bug Description

jockey-kde says "Broadcom B43 wireless driver" is not installed. (This is correct since I assume it is referring to the firmware.) When I click "Activate", the box listing the drivers goes gray and nothing seems to happen. When I click "Close", I get this crash.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/jockey-kde
InterpreterPath: /usr/bin/python2.5
Package: jockey-kde 0.5~alpha1-0ubuntu4
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/jockey-kde']
SourcePackage: jockey
Title: jockey-kde crashed with DBusException in call_blocking()
Uname: Linux 2.6.27-4-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Ben Bethge (brby8b-mst) wrote :
Revision history for this message
Ben Bethge (brby8b-mst) wrote :

I can work around this by starting jockey-kde through sudo, since apparently the crash happens when it is trying to get root privileges.

Martin Pitt (pitti)
Changed in jockey:
assignee: nobody → pitti
importance: Undecided → High
milestone: none → ubuntu-8.10
status: New → In Progress
Revision history for this message
Ben Bethge (brby8b-mst) wrote :

This is fixed by installing policykit-gnome. policykit suggests policykit-gnome, but it looks like either policykit or jockey-kde should depend on it (or depend on a virtual package that is provided by policykit-gnome and the equivalent KDE package which apparently hasn't been created yet).

Revision history for this message
Markus Majer (mpathy) wrote :

here for me it is the standard intel 3945 wireless driver, or some nvidia config stuff - since I did those two things in the moment it occurred.

Martin Pitt (pitti)
Changed in jockey:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.5~beta1-0ubuntu5

---------------
jockey (0.5~beta1-0ubuntu5) intrepid; urgency=low

  * Merge bug fixes from trunk:
    - ui.py: Explicitly set encoding of stdout and stderr to the locale's
      preferred encoding. Thanks to Colin Watson for the approach.
      (LP: #280147)
    - ui.py, set_handler_enabled(): Show SystemErrors in dialog instead of
      crashing. (LP: #274639)
    - jockey-kde: Make --check notifications actually work again.
  * jockey/oslib.py: Clean up error handling on package installation/removal.
  * jockey-kde: Work around the lack of a PolicyKit KDE user agent by starting
    the UI through kdesu when clicking on the notification. Add
    kdebase-runtime dependency for this. (LP: #274189)

 -- Martin Pitt <email address hidden> Mon, 13 Oct 2008 14:40:43 +0200

Changed in jockey:
status: Fix Committed → Fix Released
Revision history for this message
TWO (two) wrote :

This is fixed by installing policykit-gnome. policykit suggests policykit-gnome, but it looks like either policykit or jockey-kde should depend on it (or depend on a virtual package that is provided by policykit-gnome and the equivalent KDE package which apparently hasn't been created yet).
--------------------------------------------

The problem remains even after installing the package policykit-gnome Ben Bethge.

My system is trying to install the Broadcom B43 wireless driver. This was installed without a problem in KDE 3.5.9 but having just returned from trying the Kubuntu Intrepid Ibex beta, the error message that it does not have root privileges keeps appearing.

How do I get hold of the package: jockey - 0.5~beta1-0ubuntu5

If it was released in the repositories- I even have 'unsupported' updates enabled, the problem hasn't gone yet.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.