The module Display could not be loaded

Bug #33259 reported by Pekka Jääskeläinen
14
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
Fix Released
Medium
Kubuntu Bugs

Bug Description

I get an error screen with the text:

The module Display could not be loaded.

The diagnostics is:

Possible reasons:

o An error occured during your last KDE upgrade leaving an oprhaned control module
o You have old thrid party modules lying around

Check this points carefully and try to remove the module mentioned in the error message. If this fails, consider contacting your distributor or packager.

--

I'm using the binary Nvidia driver installed with apt-get.

Revision history for this message
Luka Renko (lure) wrote :

Know problem (reported several times). Just to confirm if same as bug 32915 and bug 32945, can you run "kcmshell displayconfig" form shell and provide output?

Revision history for this message
Pekka Jääskeläinen (pekka-jaaskelainen) wrote :

I entered my admin password and got the error screen. It produces the following output:

visit0r@r0ck:~$ kcmshell displayconfig

Pythonize constructor -- pid = 19582
Python interpreter initialized!

Pythonize constructor -- pid = 19582
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1624, in create_displayconfig
    return DisplayApp(parent, name)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 432, in __init__
    self._buildGUI()
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 698, in _buildGUI
    self.dpmspage = DpmsPage(tabcontrol)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1535, in __init__
    self.readDpms()
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1574, in readDpms
    self.dpms_min = last_time
UnboundLocalError: local variable 'last_time' referenced before assignment
error: *** runFunction failure
;

Pythonize constructor -- pid = 20522
Python interpreter initialized!

Pythonize constructor -- pid = 20522
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1624, in create_displayconfig
    return DisplayApp(parent, name)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 432, in __init__
    self._buildGUI()
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 698, in _buildGUI
    self.dpmspage = DpmsPage(tabcontrol)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1535, in __init__
    self.readDpms()
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1574, in readDpms
    self.dpms_min = last_time
UnboundLocalError: local variable 'last_time' referenced before assignment
error: *** runFunction failure
;
kcmshell: Fatal IO error: client killed
X Error: BadValue (integer parameter out of range for operation) 2
  Major opcode: 113
  Minor opcode: 0
  Resource id: 0x4200007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 10
  Minor opcode: 0
  Resource id: 0x4200007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 7
  Minor opcode: 0
  Resource id: 0x4200007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 6
  Minor opcode: 0
  Resource id: 0x4200007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 25
  Minor opcode: 0
  Resource id: 0x4200007
visit0r@r0ck:~$

Revision history for this message
Luka Renko (lure) wrote :

Looks different stack trace than other. Changed package to kde-guidance.

Kenny Duffus (kduffus)
Changed in kde-guidance:
assignee: nobody → kubuntu-team
Revision history for this message
Rocco Stanzione (trappist) wrote :

This looks to have been fixed. Can someone confirm and close this?

Revision history for this message
Pekka Jääskeläinen (pekka-jaaskelainen) wrote :

Yes, it's fixed.

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

Hey all!

I'm still experiencing this bug with the latest dapper drake. How was it fixed?

tarek : )

Revision history for this message
Pekka Jääskeläinen (pekka-jaaskelainen) wrote :

Yes, it was fixed, now it's broken again.

Revision history for this message
Luka Renko (lure) wrote :

Does "kcmshell displayconfig" display exactly the same as reported before? If not, please attach the output.

Revision history for this message
Pekka Jääskeläinen (pekka-jaaskelainen) wrote :

Pythonize constructor -- pid = 23656
Python interpreter initialized!

Pythonize constructor -- pid = 23656
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1677, in create_displayconfig
    return DisplayApp(parent, name)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 443, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 368, in __init__
    self._finalizeInit()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 373, in _finalizeInit
    gfxcard._finalizeInit()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 1082, in _finalizeInit
    screen._finalizeInit()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 1632, in _finalizeInit
    self.original_size = self.getAvailableResolutions()[self.currentsizeindex]
IndexError: list index out of range
error: *** runFunction failure
;

Revision history for this message
Jason Voegele (jason-jvoegele) wrote :

I still have this problem on Dapper Drake, updated via Synaptic at 3:00 EDT on 2006-06-06. The output from "kcmshell displayconfig" is as follows:

$ kcmshell displayconfig
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Pythonize constructor -- pid = 6770
Python interpreter initialized!

Pythonize constructor -- pid = 6770
open /dev/mem: Permission denied
VESA BIOS Extensions not detected.
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1677, in create_displayconfig
    return DisplayApp(parent, name)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 443, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 368, in __init__
    self._finalizeInit()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 387, in _finalizeInit
    self.setLayout(gfxcard._getDetectedLayout())
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 935, in setLayout
    gfxcard.setLayout(XSetup.LAYOUT_CLONE)
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 1143, in setLayout
    screen._resyncResolution()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 1782, in _resyncResolution
    self.gfx_card.setup.getPrimaryScreen()._resyncResolution()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 1738, in _resyncResolution
    (preferred_width,preferred_height) = self.getAvailableResolutions()[self.getResolutionIndex()]
IndexError: list index out of range
error: *** runFunction failure

Revision history for this message
SirMasterboy (sirmasterboy) wrote :

I have the latest nvidia drivers running.

I still have this problem and this is my kcmshell displayconfig output:

nick@nick-desktop:~$ kcmshell displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Pythonize constructor -- pid = 5857
Python interpreter initialized!

Pythonize constructor -- pid = 5857
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 1677, in create_displayconfig
    return DisplayApp(parent, name)
  File "/usr/lib/python2.4/site-packages/displayconfig.py", line 443, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 302, in __init__
    if bus_id == self._canonicalPCIBusID(device_section.busid):
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 508, in _canonicalPCIBusID
    parts = bus_id.split(":")
AttributeError: 'NoneType' object has no attribute 'split'
error: *** runFunction failure
;
nick@nick-desktop:~$

Revision history for this message
Cliff Wade (hawkwind) wrote :

hawkwind@Britannia:~$ kcmshell displayconfig

Pythonize constructor -- pid = 4708
Python interpreter initialized!

Pythonize constructor -- pid = 4708
KCrash: Application 'kcmshell' crashing...

Definitely confirmed that this bug still exists today in Dapper with all the current updates.

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

It has definitely been fixed in edgy. Possibly 'fix-released' is meant to refer to new packages released by kubuntu.org (kde 3.5.4 for dapper)?

Revision history for this message
SirMasterboy (sirmasterboy) wrote :

sooo what should i do to get it working heh

Revision history for this message
Rich Johnson (nixternal) wrote :

https://launchpad.net/distros/ubuntu/+source/kde-guidance/+bug/62223

Issue is in Edgy as well. I think there is an issue when updating that may cause this. If you look, check and see if "User Management" and "Disk & File Management" work. More than likely, you get the same module error.

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

That is a different issue. Actually, all the error messages posted after the bug was marked "fix released" are different than the one originally reported, making them different bugs. And of those, two separate bugs are represented (two very different error messages). This bug was correctly marked "fix released". It's adviseable to file new bug reports for these other errors (if they haven't already been reported).

With python traces, it's generally sufficient to compare only the last 2 or 3 lines of output. For example,

IndexError: list index out of range

is a problem with an array, while:

AttributeError: 'NoneType' object has no attribute 'split'

means we were trying to break up a string that didn't exist, so those are two distinct problems, each of which is distinct from the original bug, which said:

UnboundLocalError: local variable 'last_time' referenced before assignment

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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