Comment 20 for bug 32915

Revision history for this message
Andreas Ntaflos (daff) wrote :

I think I found another incarnation of this error. Running Kubuntu Edgy, with kde-guidance 0.7.0-0ubuntu4 on my Thinkpad T41p with a Radeon M10 (FireGL T2) and the open source drivers from Xorg.

I don't think it has to do with numbers getting i18n'd wrongly as I set my system's language to English.

print self.availabletargetgammas outputs: [u'1.4', u'1.6', u'1.8', u'2.0', u'2.2', u'2.4'] which seems correct. Nonetheless I applied the fix described by vidak, but I get the following error message:

Pythonize constructor -- pid = 5118
Python interpreter initialized!

Pythonize constructor -- pid = 5118

Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.4/displayconfig.py", line 1686, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.4/displayconfig.py", line 442, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 387, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 406, in _finalizeInit
    self.setLayout(gfxcard._getDetectedLayout())
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 954, in setLayout
    gfxcard.setLayout(XSetup.LAYOUT_CLONE)
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1162, in setLayout
    screen._resyncResolution()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1801, in _resyncResolution
    self.gfx_card.setup.getPrimaryScreen()._resyncResolution()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1757, in _resyncResolution
    (preferred_width,preferred_height) = self.getAvailableResolutions()[self.getResolutionIndex()]
IndexError: list index out of range
error: *** runFunction failure
;

Unfortunately I'm not so good with Python backtraces to know where to look for further possible errors.