Bug 222200 - cannot import drivers from rhpxl.videocard
cannot import drivers from rhpxl.videocard
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-display (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Jackson
Depends On:
  Show dependency treegraph
Reported: 2007-01-10 15:49 EST by Dave Maley
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-24 14:45:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Maley 2007-01-10 15:49:48 EST
Description of problem: Freah install of RHEL-5-Client (RC-Snapshot-2).  I'm
getting the following traceback when attempting to run system-config-display:

[dave@kodos ~]$ system-config-display 
Traceback (most recent call last):
  File "/usr/share/system-config-display/xconf.py", line 376, in ?
    import xConfigDialog
  File "/usr/share/system-config-display/xConfigDialog.py", line 24, in ?
    import videocardDialog
  File "/usr/share/system-config-display/videocardDialog.py", line 21, in ?
    from rhpxl.videocard import drivers
ImportError: cannot import name drivers
[dave@kodos ~]$ 

reverting to rhpxl-0.39-2.i386 from the RC-Snapshot-1 tree resolves the issue.

Version-Release number of selected component (if applicable): rhpxl-0.41-1.el5.i386

How reproducible: every time

Steps to Reproduce:
1. run system-config-display
Actual results: above traceback

Expected results: system-config-display runs w/out error

Additional info:
Comment 1 Chris Lumens 2007-01-11 10:08:26 EST
system-config-display shouldn't be using drivers anymore since it doesn't exist.
 I believe Adam is already aware of this problem and probably already has a fix
for it.
Comment 2 Adam Jackson 2007-01-24 14:45:46 EST
Yeah, fixed in s-c-d 1.0.48

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