I'm getting a different error than you say was fixed in 0.6.4:
$ kcmshell displayconfig
Pythonize constructor -- pid = 6393 Python interpreter initialized!
Pythonize constructor -- pid = 6393 Traceback (most recent call last): File "<string>", line 8, in kcontrol_bridge_create_displayconfig File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1668, in create_displayconfig return DisplayApp(parent, name) File "/usr/lib/python2.4/site-packages/displayconfig.py", line 440, in __init__ self.xsetup = XSetup(self.xconfigpath) File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 175, in __init__ if pci_device_tuple[1].getDriver()==driver_name \ AttributeError: 'PCIDevice' object has no attribute 'getDriver' error: *** runFunction failure ;
I'm getting a different error than you say was fixed in 0.6.4:
$ kcmshell displayconfig
Pythonize constructor -- pid = 6393
Python interpreter initialized!
Pythonize constructor -- pid = 6393 bridge_ create_ displayconfig python2. 4/site- packages/ displayconfig. py", line 1668, in create_ displayconfig python2. 4/site- packages/ displayconfig. py", line 440, in __init__ self.xconfigpat h) python2. 4/site- packages/ displayconfigab straction. py", line 175, in __init__ tuple[1] .getDriver( )==driver_ name \
Traceback (most recent call last):
File "<string>", line 8, in kcontrol_
File "/usr/lib/
return DisplayApp(parent, name)
File "/usr/lib/
self.xsetup = XSetup(
File "/usr/lib/
if pci_device_
AttributeError: 'PCIDevice' object has no attribute 'getDriver'
error: *** runFunction failure
;