Command-line interface doesn't work without X

Bug #394688 reported by Jukka Merinen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

The command line interface in jockey-gtk for enabling and disabling drivers doesn't really work. It requires an X display to be present, so it can't be used in scripts.

For example, trying to change the display driver with --enable without an X display results in a segfault:

test:~# jockey-gtk --enable xorg:nvidia-180
/var/lib/python-support/python2.6/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
/usr/bin/jockey-gtk:51: Warning: invalid (NULL) pointer instance
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: GtkWarning: gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: PangoWarning: pango_context_set_font_description: assertion `context != NULL' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: PangoWarning: pango_context_set_base_dir: assertion `context != NULL' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: PangoWarning: pango_context_set_language: assertion `context != NULL' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: GtkWarning: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
/usr/bin/jockey-gtk:51: GtkWarning: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
  self.glade = gtk.glade.XML('/usr/share/jockey/main.glade')
Segmentation fault

Occurs in Ubuntu 9.04 with jockey-common version 0.5-0ubuntu10 and jockey-gtk version 0.5-0ubuntu10.

Revision history for this message
Martin Pitt (pitti) wrote :

Jockey recently grew a "jockey-text" frontend, will be uploaded soon.

Changed in jockey (Ubuntu):
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.5.3-0ubuntu1

---------------
jockey (0.5.3-0ubuntu1) karmic; urgency=low

  * New upstream release:
    - Add a text frontend, 'jockey-text'. Although the GTK and KDE frontends
      can be launched and scripted command line, they are dependent upon
      DISPLAY being set. This text frontend has the ability to run in a true
      text only environment. (By Mario Limonciello) (LP: #394688)
    - Ported to polkit-1.
  * debian/control: Update policykit dependencies to policykit-1. Drop
    policykit-kde, since it does not exist so far.
  * Merge bug fix from trunk: Move X-KDE-autostart-phase: field from menu to
    autostart .desktop.
  * kde/jockey-kde, kde/jockey-kde.desktop.in: Reintroduce code to run
    frontend as root, since there is no KDE frontend for polkit-1 yet.
  * data/handlers/broadcom_wl.py: rmmod b43 and friends before enabling wl, so
    that it will work on the fly. (LP: #393689)

 -- Martin Pitt <email address hidden> Tue, 14 Jul 2009 17:27:14 +0200

Changed in jockey (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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