jockey-kde in II fails to start

[Belisarivs]

Running jockey-kde in console in intrepid results in this message:

$ jockey-kde
Traceback (most recent call last):
  File "/usr/bin/jockey-kde", line 393, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 322, in run
    self.ui_init()
  File "/usr/bin/jockey-kde", line 67, in ui_init
    self.ui_load_translations()
  File "/usr/bin/jockey-kde", line 154, in ui_load_translations
    (heading, subtext) = self.main_window_text()
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 139, in main_window_text
    for h_id in self.backend().available(self.argv_options.mode):
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 72, in backend
    self._dbus_iface = Backend.create_dbus_client()
  File "/usr/lib/python2.5/site-packages/jockey/backend.py", line 533, in create_dbus_client
    obj = bus.get_object(DBUS_BUS_NAME, '/DeviceDriver')
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

[Markus Korn (thekorn)]

I can confirm this same issue for jockey-gtk

jockey-gtk version 0.4.1+r360-0ubuntu1

[michael (mikahgiacchetti)]

I dont know if your experiencing the same issue I did, I upgraded blah blah blah, noticed new nvidia in there, didnt think of anything till i restarted.

my settings were lost.

Well.
I fixed the problem by going into hardware drivers, and re-installing, and re-enabling NVIDIA graphix driver 173

I think the problem is when you upgrade/update it rewrites your configs, setting the drivers to default, then when you restart, you get low graphics mode.

ALthough i am not a dev, so I have no clue, i upgraded to see if the new kernel would break usb on hibernate (when hibernate dont even work lol)

[michael (mikahgiacchetti)]

unsubscribe