jockey-gtk crashed with ImportError in <module>()

running jockey-ftk from command line:

$ jockey-gtk
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 25, in <module>
    import jockey.ui
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 31, in <module>
    from backend import UnknownHandlerException, PermissionDeniedByPolicy, BackendCrashError, polkit_auth_wrapper, dbus_sync_call_signal_wrapper, Backend, DBUS_BUS_NAME
  File "/usr/lib/python2.6/dist-packages/jockey/backend.py", line 32, in <module>
    import detection, xorg_driver
  File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 32, in <module>
    import handlers, xorg_driver
  File "/usr/lib/python2.6/dist-packages/jockey/xorg_driver.py", line 21, in <module>
    import XKit.xutils
ImportError: No module named XKit.xutils
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/apport_python_hook.py", line 85, in apport_excepthook
    os.O_WRONLY|os.O_CREAT|os.O_EXCL), 'w')
OSError: [Errno 17] File exists: '/var/crash/_usr_bin_jockey-gtk.1000.crash'

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 25, in <module>
    import jockey.ui
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 31, in <module>
    from backend import UnknownHandlerException, PermissionDeniedByPolicy, BackendCrashError, polkit_auth_wrapper, dbus_sync_call_signal_wrapper, Backend, DBUS_BUS_NAME
  File "/usr/lib/python2.6/dist-packages/jockey/backend.py", line 32, in <module>
    import detection, xorg_driver
  File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 32, in <module>
    import handlers, xorg_driver
  File "/usr/lib/python2.6/dist-packages/jockey/xorg_driver.py", line 21, in <module>
    import XKit.xutils
ImportError: No module named XKit.xutils

$ sudo apt-get install python-xkit
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-xkit is already the newest version.
The following packages were automatically installed and are no longer required:
  sane-utils linux-headers-2.6.28-6-generic fakeroot linux-headers-2.6.28-6 nvidia-settings dkms patch nvidia-180-libvdpau
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I can confirm this, I am having the same issue.

jockey-common:
  Installed: 0.5-0ubuntu2

jockey-gtk:
  Installed: 0.5-0ubuntu2

Description: Ubuntu jaunty (development branch)
Release: 9.04

I also confirm this: I am having the same error message, both with jockey-gtk and jockey-kde (unsurprisingly).

Architecture: x86-64

jockey-common:
   Installed: 0.5-0ubuntu2
jockey-gtk:
   Installed: 0.5-0ubuntu2
jockey-kde:
   Installed: 0.5-0ubuntu2
Description: Kubuntu jaunty (development branch)
 Release: 9.04

I can provide more details if needed, but I guess the OP is clear enough.

I am also having this issue. After installing Jaunty, I could not install the mobo card that I have, which is nvidia 8200. This is the output I got from doing sudo jockey-gtk:

Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 25, in <module>
    import jockey.ui
  File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 31, in <module>
    from backend import UnknownHandlerException, PermissionDeniedByPolicy, BackendCrashError, polkit_auth_wrapper, dbus_sync_call_signal_wrapper, Backend, DBUS_BUS_NAME
  File "/usr/lib/python2.6/dist-packages/jockey/backend.py", line 32, in <module>
    import detection, xorg_driver
  File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 32, in <module>
    import handlers, xorg_driver
  File "/usr/lib/python2.6/dist-packages/jockey/xorg_driver.py", line 21, in <module>
    import XKit.xutils
ImportError: No module named XKit.xutils

I have tried to use the command given here, by Malenfant [$ sudo apt-get install python-xkit]. This is the following output.

Reading package lists... Done
Building dependency tree
Reading state information... Done
python-xkit is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

This is my info here.
Achitecture: x86_64
jockey-common, jockey-gtk, and jockey-kde are installed. Like Barthelemy, I also run Kubuntu Jaunty, development branch. Can't find a solution yet :(

I found a "workaround" that I should have tried earlier: reinstall xkit:

sudo apt-get --reinstall install python-xkit

You might also reinstall jockey if it does not work. This problem happened when I upgraded from alpha4 to alpha5: I had a fresh install of alpha 4 and then updated everything one day after alpha5 was released.

After reinstalling xkit and restarting the x server, I can confirm that the correct driver was activated and now everything works well (nvidia XServer Settings could configure TwinView and correct resolution).

One last thing: I got a notification that the jockey-backend crashed after I activated the driver. The jockey UI was still working and like I said, after the xserver restart, everything worked well.

Wow, thanks Bathelemy.

That really did work. The sudo command reinstalled the xkit and the drivers
window finally opened. However, here is where my issues begin again. If you
don't mind me asking for your assistance once more, I'd appreciate it.

I have a separate card, nvidia 9500 gt - which is the one I want working.
When I open up the drivers window, it actually gives me two choices. Driver
173 and driver 180. Now, I'm not sure if I'll have this problem again
because I installed kubuntu, but last time I tried to install driver, it
gave me an error [forgot to write it down] after I downloaded the nvidia
driver 180 [which opens my mobo integrated 8200] and then used the sh
~/NVIDIA* command. In the end, it didn't do a successful install and I was
still stuck with the 8200.

When I reinstalled AGAIN, i used driver 173, to my avail, that gave me an
error too. Hopefully, being Kubuntu now, I won't have that problem but I
just wanted to ask. I'm sorry if this is a bother. I would appreciate it
even if you just pinpoint me elsewhere. I relied on my friend too much, now
I can't do anything ^_^;; Thanks again.

I'm just in the process right now of doing the re-install.

sudo apt-get --reinstall install python-xkit

This did in fact re-load Xkit correctly, and now running 'jockey-gtk' acutally works.

I need to use driver 173, so I picked it, and it's working correctly after a reboot, no crash.

Luuka,

I'm in no way an expert regarding this issue, but here are some thoughts:

1- Unless there is a bug related to your specific video card in NVIDIA driver 180, you should go with the 180.
2- Usually, when you have two devices, one integrated with the motherboard and one plugged in a port, and they do not play well together (e.g., two soundcards, two video cards), you must disable one of them in the BIOS (when you boot your computer, it should tell you press DEL or F_something to enter BIOS). You might need to: disable driver, reboot, disable video card on motherboard in BIOS, reboot, reenable the driver.
3- If you have other questions regarding this issue, you should post on ubuntuforums (http://ubuntuforums.org/) or even better, on NVIDIA Linux forum (http://www.nvnews.net/vbulletin/forumdisplay.php?s&forumid=14) since your issue does not seem related to jockey.

Personally, I found very good information on the NVIDIA forum in the past (my card was not supported, the fan was at 100% because of the latest driver, etc.).

Good luck

did the trick for me too.

so what to do with this bug?

mark as solved?

thx

That did it for me. Actually, once the xutils thing was fixed, I was
able to install the driver for the 9500 that I have. The only thing
now is to fix the meta mode, but other than that, the bug has been
fixed on my end. Thanks guys!

On 3/10/09, DieB <email address hidden> wrote:
> did the trick for me too.
>
> so what to do with this bug?
>
> mark as solved?
>
> thx
>
> --
> jockey-gtk crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/335543
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “jockey” source package in Ubuntu: New
>
> Bug description:
> -
>
> ProblemType: Crash
> Architecture: i386
> CurrentDmesg:
> [ 23.271287] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> [ 34.000020] eth0: no IPv6 routers present
> [ 47.336150] warning: `pulseaudio' uses 32-bit capabilities (legacy
> support in use)
> DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module
> is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/bin/jockey-gtk
> InterpreterPath: /usr/bin/python2.6
> MachineType: Dell Inc. Precision WorkStation 370
> Package: jockey-gtk 0.5-0ubuntu2
> PackageArchitecture: all
> ProcCmdLine: root=UUID=4c132c72-3110-4e96-a2a4-05890de963b4 ro quiet splash
> ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> ProcEnviron:
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
> PythonArgs: ['/usr/bin/jockey-gtk']
> SourcePackage: jockey
> Title: jockey-gtk crashed with ImportError in <module>()
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

Could you please attach your /var/log/apt/term.log if you had this issue? It may contain information that help us diagnose the problem. The current suspect is python-central not doing the symlinking correctly.

Re-installing the library package is not needed, re-running the post-install script is enough:

sudo /var/lib/dpkg/info/python-xkit.postinst

So on a system upgrade the installation of Python 2.6 should re-run the post-install scripts of all Python libraries.

Looks like a problem in with the transition to Python 2.6 in python-central, according to IRC discussion with mvo and DktrKramz.

IRC discussion with mvo and DktrKranz:

<tkamppeter> Any Python expert here? It is about bugs like bug 335543, a Python app does not find a certain Python library (saying "ImportError in <module>()") but the library is installed. Reinstalling the library helps. This does not only happen to Jockey but also to hal_lpadmin, the system-config-printer tray applet, ... What is the problem here?
<ubottu> Launchpad bug 335543 in jockey "jockey-gtk crashed with ImportError in <module>()" [Undecided,New] https://launchpad.net/bugs/335543
<DktrKranz> tkamppeter: it's probably not transitioned for Python 2.6, a rebuild could fix it.
<DktrKranz> tkamppeter: I mean x-kit
<tkamppeter> DktrKranz: In the mentioned case a reinstall of the existing library package even helps (no rebuild of the package). Can it be that the postinstall scripts of all Python libraries need to get re-run after Python 2.6 installation? This should be automated in the update process.
<seb128> mvo is looking to similar issues
<mvo> tkamppeter: it looks like bug(s) in python-central
<mvo> tkamppeter: seb128 has a similar issue with bzrtools

The same crash on amd64 system

I can confirm that simply running:

sudo /var/lib/dpkg/info/python-xkit.postinst

fixed this problem. I looked into why the module couldn't be found and xkit did not seem to be set up for python 2.6, only 2.5 - this would suggest it is indeed the problem in python-central mentioned above.

Thank you, now it works!

It works after I run sudo /var/lib/dpkg/info/python-xkit.postinst, thanks!

this fixed it for me:
sudo apt-get --reinstall install python-xkit

thanks Barthelemy D. (posted above ^^^)

I install Ubuntu 9.04 Alpha6 (fresh) and problem fixes.

Bruce Miller - is there any additional information you can provide on how to recreate this or why you have reopened it? Thanks in advance.

Brian Murray,
Thanks for taking a look at this.

I have recreated the problem to the extent that I ran into it at least twice on successive installs to the same machine, first immediately after installing Kubuntu Lucid alternate CD, as described in Bug #548572 (about March 27, 2010) and second, Bug #550905 (on April 5, 2010). Please read also my comments on Bug #558758 in which I question the behaviour of Apport.

As those comments will show, I am bothered that configuration failures of new development versions get marked as duplicates of old bugs from previous development cycles; bugs which have been studied, fixed and the fix released.

It is perfectly possible for an entirely new bug in a new development version to show remarkably similar symptoms to a bug in a previous development version. That alone does not make it a duplicate of the previous bug.

Marking it as a duplicate significantly increases the risk that it will pass unnoticed during the QA process before final release. If a reviewer runs afoul of it after release, the risk for more anti-Ubuntu FUD is high.

This is the risk that I am trying to flag --- while trying to avoid whinging and whining on the ubuntu-devel-discuss mailing list.

I see two priorities:
1. In the short term, look at this and other configuration bugs which could harm the reputation of Lucid as an LTS release (#4511005, #548510, #338095);
2. Rewrite Apport so that it handles better new configuration bugs with strikingly similar symptoms to older, fixed ones

I hope this helps to explain why I reopened this old bug.

no longer a problem

> Date: Mon, 12 Apr 2010 21:35:15 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 335543] Re: jockey-gtk crashed with ImportError in <module>()
>
> Bruce Miller - is there any additional information you can provide on
> how to recreate this or why you have reopened it? Thanks in advance.
>
> ** Changed in: python-central (Ubuntu)
> Status: New => Incomplete
>
> --
> jockey-gtk crashed with ImportError in <module>()
> https://bugs.launchpad.net/bugs/335543
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “python-central” package in Ubuntu: Incomplete
>
> Bug description:
> -
>
> ProblemType: Crash
> Architecture: i386
> CurrentDmesg:
> [ 23.271287] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> [ 34.000020] eth0: no IPv6 routers present
> [ 47.336150] warning: `pulseaudio' uses 32-bit capabilities (legacy support in use)
> DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/bin/jockey-gtk
> InterpreterPath: /usr/bin/python2.6
> MachineType: Dell Inc. Precision WorkStation 370
> Package: jockey-gtk 0.5-0ubuntu2
> PackageArchitecture: all
> ProcCmdLine: root=UUID=4c132c72-3110-4e96-a2a4-05890de963b4 ro quiet splash
> ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
> ProcEnviron:
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
> PythonArgs: ['/usr/bin/jockey-gtk']
> SourcePackage: jockey
> Title: jockey-gtk crashed with ImportError in <module>()
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/python-central/+bug/335543/+subscribe

_________________________________________________________________
New, Used, Demo, Dealer or Private? Find it at CarPoint.com.au
http://clk.atdmt.com/NMN/go/206222968/direct/01/

Marking back to Fix Released, removing regression-* tag.

@Bruce: while I agree with some of your points, I see nothing relating to this bug. For the apport changes, the best would be to either:

* email the devel-discuss with a proposal/reasoning;
* open a bug against apport itself, doignt he same above;
* open a new idea on brainstorm.