kcontrol's display module has unhandled Python exception

Bug #37275 reported by John Dong
48
Affects Status Importance Assigned to Milestone
guidance-power-manager (Ubuntu)
Fix Released
Medium
Mac Guba

Bug Description

Reproduction:

(1) Start kcontrol or System Settings.

(2) Hit Peripherals/Display.

(3) The module does not show up. Terminal shows:
Pythonize constructor -- pid = 13258
Python interpreter initialized!

Pythonize constructor -- pid = 13258
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
;

Revision history for this message
Rocco Stanzione (trappist) wrote :

I can confirm this bug exactly as described

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
Rocco Stanzione (trappist) wrote : Fixes kde-guidance failure described

This patch fixes this bug

Revision history for this message
Simon Edwards (simon-simonzone) wrote :

Good work on the fix. It will be including the next guidance release. (0.6.4)

Revision history for this message
John Dong (jdong) wrote :

When will this be? It's kind of an irritating problem...

Revision history for this message
Rocco Stanzione (trappist) wrote :

Kubuntu folks, could we get this merged until then?

Revision history for this message
John Dong (jdong) wrote : Re: [Bug 37275] Re: kcontrol's display module has unhandled Python exception

looks fixed!

On 4/3/06, Rocco Stanzione <email address hidden> wrote:
>
> ** Bug 33227 has been marked a duplicate of this bug
>
> ** Bug 32915 has been marked a duplicate of this bug
> --
> kcontrol's display module has unhandled Python exception
> https://launchpad.net/malone/bugs/37275
>

Revision history for this message
Rocco Stanzione (trappist) wrote :

Thanks jriddell!

Changed in kde-guidance:
status: Confirmed → Fix Released
Revision history for this message
Tarek Loubani (tareko) wrote :

Doh. apologies for already posting this on the duplicates:

I am having the same problem. Here is my lspci result:

0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 01df (rev a1)

and with -n:

$ lspci -n | grep 01:00

0000:01:00.0 0300: 10de:01df (rev a1)

The card is a 7300 to the best of my knowledge. It is using the ubuntu package of the restricted driver set.

tarek : )

Revision history for this message
Tarek Loubani (tareko) wrote :

reopen bug?

Changed in kde-guidance:
status: Fix Released → Unconfirmed
Revision history for this message
Rocco Stanzione (trappist) wrote :

Fix has been released. There seems to have been a misunderstanding after that. Please reopen if this is not the case.

Changed in kde-guidance:
status: Unconfirmed → Fix Released
Revision history for this message
Ryan Campbell (rcampbell) wrote :

Still doesn't work in Edgy with guidance-0.7.0-0ubuntu4 with nvidia binary drivers. (it did work previously in the edgy RC)

'kcmshell displayconfig' gives the following output:

Pythonize constructor -- pid = 7782
Python interpreter initialized!

Pythonize constructor -- pid = 7782
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.4/displayconfig.py", line 1685, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.4/displayconfig.py", line 441, 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 392, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1101, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.4/displayconfigabstraction.py", line 1651, in _finalizeInit
    self.original_size = self.getAvailableResolutions()[self.currentsizeindex]
IndexError: list index out of range
error: *** runFunction failure
;

Revision history for this message
lcampagn (luke-campagnola) wrote :

I have a similar problem in feisty, slightly different error. The problem is essentially the same as above, though--getAvailableResolutions() returns an empty array.

Pythonize constructor -- pid = 17601
[]
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1685, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 441, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 387, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 406, in _finalizeInit
    self.setLayout(gfxcard._getDetectedLayout())
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 958, in setLayout
    gfxcard.setLayout(XSetup.LAYOUT_SINGLE_XINERAMA)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1162, in setLayout
    screen._resyncResolution()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1811, in _resyncResolution
    self.gfx_card.setup.getPrimaryScreen()._resyncResolution()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1767, in _resyncResolution
    (preferred_width,preferred_height) = self.getAvailableResolutions()[-1]
IndexError: list index out of range
error: *** runFunction failure
;

Revision history for this message
Mac Guba (macguba17047) wrote :

Please help me fix this problem

Changed in kde-guidance (Ubuntu):
assignee: nobody → Mac Guba (macguba17047)
steve (atkinssteve)
affects: kde-guidance (Ubuntu) → guidance-power-manager (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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