Bug 703085 - s-c-kickstart doesn't start on VNC display - ImportError: No module named data
s-c-kickstart doesn't start on VNC display - ImportError: No module named data
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-kickstart (Show other bugs)
5.7
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Chris Lumens
Release Test Team
:
Depends On:
Blocks: rhel57rtt
  Show dependency treegraph
 
Reported: 2011-05-09 05:01 EDT by Alexander Todorov
Modified: 2011-05-10 09:11 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-05-10 08:51:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Todorov 2011-05-09 05:01:46 EDT
Description of problem:
s-c-kickstart fails to start on VNC display

Version-Release number of selected component (if applicable):
system-config-kickstart-2.6.19.9-2.el5

How reproducible:
always

Steps to Reproduce:
1. Xvnc -SecurityTypes None :1 &
2. export DISPLAY=:1
3. metacity &
4. # system-config-kickstart (as root)

  
Actual results:
Could not open display because no X server is running.
Try running 'system-config-kickstart --help' for a list of options.


Expected results:
s-c-kickstart starts and shows onto the vnc screen.

Additional info:
applications like virt-manager or gedit start successfully on the same screen.
Comment 1 Chris Lumens 2011-05-09 09:24:46 EDT
I hate that error message so much.  I really should just take it out.  Chances are this has nothing to do with VNC, but it's possible.  Can you apply the following patch to /usr/bin/system-config-kickstart and paste in the real error:

@@ -72,11 +72,11 @@ for (opt, value) in opts:
 if file:
     file = file[0]
 
-try:
-    import kickstartGui
-except:
-    print (_("Could not open display because no X server is running."))
-    print (_("Try running 'system-config-kickstart --help' for a list of options."))
-    sys.exit(0)
-
+#try:
+#    import kickstartGui
+#except:
+#    print (_("Could not open display because no X server is running."))
+#    print (_("Try running 'system-config-kickstart --help' for a list of options."))
+#    sys.exit(0)
+import kickstartGui
 kickstartGui.kickstartGui(file)
Comment 2 Alexander Todorov 2011-05-10 05:02:19 EDT
Hi Chris,
with your patch applied the error message is now:

# system-config-kickstart 
Traceback (most recent call last):
  File "/usr/bin/system-config-kickstart", line 81, in ?
    import kickstartGui
  File "/usr/share/system-config-kickstart/kickstartGui.py", line 33, in ?
    import partition
  File "/usr/share/system-config-kickstart/partition.py", line 27, in ?
    import partWindow
  File "/usr/share/system-config-kickstart/partWindow.py", line 28, in ?
    from pykickstart.data import *
ImportError: No module named data


I have pykickstart-1.68-1.el5 installed on the system.
Comment 3 Chris Lumens 2011-05-10 08:51:31 EDT
Your version of pykickstart must have come from RHEL6 or Fedora and rebuilt, then.  pykickstart versions in RHEL5 have version numbers like 0.43.x (9 is the latest) and have a data module.  pykickstart versions in RHEL6 and Fedora have version numbers like 1.xx and do not.

Note You need to log in before you can comment on or make changes to this bug.