'Monitor & Display' module in System Settings is not working.

[Tom Inglis]

On my Kubuntu Feisty (Latest) installation with nvidia-glx, the 'Monitor & Display' module in System Settings stopped working after I installed the nvidia-glx driver.

It says:

The module Monitor & Display could not be loaded.

Possible reasons:

- An error occurred during your last KDE upgrade leaving an orphaned control module.

- You have old third party modules lying around.

[aracon (drogen)]

Same probleme here on kubuntu edgy after installing and running the latest nvidia driver (9755). The problem appears just with GLX extension, without the module behaves quite normal.

[Tom Inglis (tominglis)]

Hi,

What does the GLX extension do, some kind of OpenGL stuff? If you turn it off
in xorg.conf can you then not do exciting Beryl things / play games?

T.

On Tuesday 20 March 2007 21:42:14 aracon wrote:
> Same probleme here on kubuntu edgy after installing and running the
> latest nvidia driver (9755). The problem appears just with GLX
> extension, without the module behaves quite normal.

[Yuriy Kozlov (yuriy-kozlov)]

Thank you for filing this bug.

Could you post the output you get when running it from the command line with "kcmshell displayconfig"?

[Tom Inglis (tominglis)]

Hey Yuriy,

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 = 8622
Python interpreter initialized!

*

sudo 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
No protocol specified
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
No protocol specified
kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-8643' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.

Pythonize constructor -- pid = 8633
Python interpreter initialized!

Pythonize constructor -- pid = 8633
No protocol specified
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in
creat
e_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 437, in
__init
__
    self.xf86server = xf86misc.XF86Server()
  File "/var/lib/python-support/python2.5/xf86misc.py", line 133, in __init__
    raise XF86Error, "Couldn't connect to X server."
xf86misc.XF86Error: Couldn't connect to X server.
error: *** runFunction failure
;

*

systemsettings
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
adding Monitor & Display /usr/share/applications/kde/displayconfig.desktop

Pythonize constructor -- pid = 8645
Python interpreter initialized!

Pythonize constructor -- pid = 8645
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
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 = 8673
Python interpreter initialized!

Pythonize constructor -- pid = 8673
kcmshell: Fatal IO error: client killed
kcmshell: Fatal IO error: client killed
QPaintDevice: Cannot destroy paint device that is being painted
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 10
  Minor opcode: 0
  Resource id: 0x4400007
X Error: BadWindow (invalid Window parameter) 3
  Major...

[Yuriy Kozlov (yuriy-kozlov)]

A new version of guidance (0.8.0) was just released into Feisty. Could you upgrade and try again?

[Tom Inglis (tominglis)]

Yuriy,

I have all of the latest updates as of 02:24 GMT, from the UK server. I had
guidance 0.8.0 ubuntu2 before my last update, and so the situation is the
same?

It does load the dialog now when you don't sudo it, but the xorg.conf settings
within it are incorrect (640x480 & VESA etc). The power settings are correct,
but then they are saved to a different configuration file.

Tom

On Sunday 1 April 2007 20:29:58 Yuriy Kozlov wrote:
> A new version of guidance (0.8.0) was just released into Feisty. Could
> you upgrade and try again?

[Tom Inglis (tominglis)]

Oops, that might be slightly confusing. Basically, I meant that nothing had
changed since this morning. i.e. it was showing the dialog where before it
wasn't at all, but it doesn't reflect what is actually happening in the
system, and it still refuses to load if you sudo it.

T.

On Monday 2 April 2007 02:27:16 Tom Inglis wrote:
> Yuriy,
>
> I have all of the latest updates as of 02:24 GMT, from the UK server. I had
> guidance 0.8.0 ubuntu2 before my last update, and so the situation is the
> same?
>
> It does load the dialog now when you don't sudo it, but the xorg.conf
> settings within it are incorrect (640x480 & VESA etc). The power settings
> are correct, but then they are saved to a different configuration file.
>
> Tom
>
> On Sunday 1 April 2007 20:29:58 Yuriy Kozlov wrote:
> > A new version of guidance (0.8.0) was just released into Feisty. Could
> > you upgrade and try again?

[Yuriy Kozlov (yuriy-kozlov)]

aracon, do you get the same output as Tom?

[Bernhard Gehl (bernhard-gehl-gmail)]

Hi there,

I get a similar error here but with a slightly different configuration: Kubuntu Feisty (current) but with the fglrx ati driver from the 2.6.20-14 restricted package. The error messages on my system are in German but they would translate roughly to what was stated here in the discussion.

Can I help in any way?

Bernhard

[newtux (newtux)]

Hello,

Im also getting the same error running Feisty with nvidia-glx

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
DCOPClient::attachInternal. Attach failed Could not open network socket
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0
DCOP aborting call from 'anonymous-5749' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.

Pythonize constructor -- pid = 5737
Python interpreter initialized!

Pythonize constructor -- pid = 5737
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
NameError: global name 'create_displayconfig' is not defined
error: *** runFunction failure
;

[Nathan Sprangers (farruinn)]

I don't think this bug is specific to kde-guidance as I get similar output when trying to run Quanta plus in Edgy. I may be completely off base on that though.

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

[Yuriy Kozlov (yuriy-kozlov)]

Nathan: that output is normal when running KDE programs from a terminal. Don't know why it happens, but it's not a sign of breakage. The problem is the errors that come after that.

newtux: your error does not looks the same as Tom's, please file a separate bug.

[newtux (newtux)]

Okay, will do. Sorry about that.

Good luck with this one!

[Tom Inglis (tominglis)]

Hi Guys,

I am still not seeing the correct data in the Monitor & Display tool. Only the Power Saving settings are correct, the rest bear no relation to the reality. It says 640x480 and vesa driver, when it is 1680x1050 nvidia-glx. Could this be a problem with the SLI? My media PC works fine with nvidia-glx.

Bestest,

Tom

[Niels Egberts (nielsegberts)]

I have got this bug too.

I have installed ubuntu feisty final, and then the kubuntu-desktop. I played for a while with gnome and compiz and then started kde. Now I cant change my resolution to 1280x1024.

[Stephan Rave (info-stephanrave)]

Same Problem here. (I have a Geforce Ti 4200) It seems, displayconfig cannot get any sensible information from the system: I can choose every resolution I want to, but the refresh rates are messed up. For example, at 1280x1024 it offers 50Hz, 51Hz, 56Hz, while the monitor runs at 75Hz and should run at 85Hz. When I change the monitor settings, everything looks fine, but only until I restart displayconfig. The nv driver works. Fresh upgrade from edgy to feisty.

[Stephan Rave (info-stephanrave)]

By the way, this is really annoying! I can set up xorg.conf so that everything works fine. But as soon as I start a kde-session, everything is messed up again.

[Sebastian Kügler (sebasje)]

On Friday 20 April 2007 14:13:39 Stephan Rave wrote:
> By the way, this is really annoying! I can set up xorg.conf so that
> everything works fine. But as soon as I start a kde-session, everything
> is messed up again.

You can delete ~/.kde/share/config/displayconfigrc as a temporary workaround.
--
sebas

 http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
So many beautiful women and so little time. - John Barrymore

[Stephan Rave (info-stephanrave)]

Thanks sebas, that worked!

[Keith Jones (keithjones)]

I too have this problem. I noticed it after the upgrade to feisty, but it may have existed in edgy. I had never had any need to muck with my monitor settings until after the upgrade though.

[WaKkO (veugelenw)]

I have the same problem

- I did a fresh Kubuntu Feisty install
- I installed nvidia-glx drivers for my Geforce ti 4200
- When I open "System Settings" and click "Monitor & Display", it crashes.
- This is the output of "kcmshell displayconfig":

veugelenw@veugelenw-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 = 6279
Python interpreter initialized!

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

Backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233119536 (LWP 6279)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 _XRRGetScreenInfo (dpy=0x82ca880, info=0x8163d20, window=490)
    at ../../src/XrrConfig.c:226
#7 0xb68ba58a in XRRGetScreenInfo (dpy=0x82ca880, window=490)
    at ../../src/XrrConfig.c:351
#8 0xb639a74a in ?? () from /var/lib/python-support/python2.5/ixf86misc.so
#9 0x082ca880 in ?? ()
#10 0x000001ea in ?? ()
#11 0xbfbe323c in ?? ()
#12 0xbfbe3238 in ?? ()
#13 0x082387d4 in ?? ()
#14 0x0811d954 in ?? ()
#15 0x000001ea in ?? ()
#16 0xb621b848 in ?? ()
#17 0xb6367df4 in ?? () from /usr/lib/libpython2.5.so.1.0
#18 0xb61f9eac in ?? ()
#19 0xbfbe3278 in ?? ()
#20 0xb62b748d in PyCFunction_Call () from /usr/lib/libpython2.5.so.1.0
Backtrace stopped: frame did not save the PC

regards,

Wouter Veugelen

[Dexi (dexii)]

Hi, I am getting the same thing and been searching all over tonight trying to find a fix. It is affecting my 'Monitor & Display' and 'Windows Applications' links in the 'System Settings'. I installed Kubunutu 7.04 two nights ago. Have all current updates that it would let me get.

Here are my results:
jnmyers@ljnmyers43:~$ sudo kcmshell displayconfig
Password:
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably crashed.

Pythonize constructor -- pid = 5939
Python interpreter initialized!

Pythonize constructor -- pid = 5939
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 437, in __init__
    self.xf86server = xf86misc.XF86Server()
  File "/var/lib/python-support/python2.5/xf86misc.py", line 133, in __init__
    raise XF86Error, "Couldn't connect to X server."
xf86misc.XF86Error: Couldn't connect to X server.
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 44, in apport_excepthook
    binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))
AttributeError: 'module' object has no attribute 'argv'

Original exception was:
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 437, in __init__
    self.xf86server = xf86misc.XF86Server()
  File "/var/lib/python-support/python2.5/xf86misc.py", line 133, in __init__
    raise XF86Error, "Couldn't connect to X server."
xf86misc.XF86Error: Couldn't connect to X server.
error: *** runFunction failure

Thanks - JN
;

[Yuriy Kozlov (yuriy-kozlov)]

zakanozz: Could you also attach the output of "kcmshell wineconfig"? I find it unlikely that you are experiencing the same bug with wineconfig as with displayconfig.

[Dexi (dexii)]

Its kinda long.....

X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-5715' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.

Pythonize constructor -- pid = 5703
Python interpreter initialized!

Pythonize constructor -- pid = 5703
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

knotify: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-5719' to 'knotify'
ERROR: Communication problem with knotify, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:imagelist:ImageList_Re...

[Yuriy Kozlov (yuriy-kozlov)]

zakanozz: In the future, please add long output as an attachment. Also, if you are having a problem with wineconfig (you just said it works) please file a separate bug.

[T. S. Ferreira (tsferreira)]

I get a similar problem with several applications. For instance, if I run xpdf, I get sometimes, after I quit:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x1e0007e

and at other occasions:

Warning: Attempt to remove nonexistent passive grab

-- tsf

[Dhaos (jmathena0)]

There seem to be two separate issues here. I've managed to find a fix in some of the ubuntu forums for the first issue, and while I don't have the links, I can share them here as I've just put them into practice this morning:

TO THOSE WITH THE "BadDevice" ERROR:

I fixed this error by removing a few lines from my xorg.conf file. Apparently the default file contains lines that handle input from tablet devices. If you don't have a tablet device, X will complain.

You want to find all unused input devices and comment them out, like this:

#Section "InputDevice"
# Driver "wacom"
# Identifier "stylus"
# Option "Device" "/dev/input/wacom"
# Option "Type" "stylus"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection

#.. comment out any other unused device

And also comment out the corresponding entries in your ServerLayout:

Section "ServerLayout"
 Identifier "Xinerama"
 Screen 0 "Screen0" 0 0
 Screen 1 "Screen1" LeftOf "Screen0"
 Screen 2 "Screen2" RightOf "Screen0"
 InputDevice "Generic Keyboard"
 InputDevice "Configured Mouse"
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
 Option "Xinerama" "on"
EndSection

[Andreas Wenning (andreas-wenning)]

The problem witch is originally described in the bug description is still present in kubuntu gutsy tribe 5. However installing python2.5-dev fixes the problem on gutsy (installs a missing libpython2.5.so file).

[noisymime (josh-noisymime)]

@awen

I'm on Gutsy Tribe 5 and experiencing this problem however I already had python2.5-dev installed so something else is causing the issue here

[Andreas Wenning (andreas-wenning)]

@noisymime

Running displayconfig from terminal sometimes gives some helpful information about the problems origin.

[JW (arch0njw)]

I was having a very similar problem. If I had *only* the GLX module loaded, my screensaver would not work, and the "Monitor & Display" module would not load. I now have this in my modules section and all is well:

Section "Module"
 Load "i2c"
 Load "bitmap"
 Load "ddc"
 Load "extmod"
 Load "freetype"
 Load "glx"
 Load "int10"
 Load "type1"
 Load "vbe"
EndSection

I'll play the role of dumb hack and declare that I don't know what part of that fixed it.

[Joseph Augustin (joseph-augustin)]

I got the same problem with Gutsy alpha daily-release from 2007-09-21.
I tested the live CD. Since it did not give me the right resolution I tried to change it.
But the module Monitor & Display could not be loaded. Same error as in the bugreport.

[Yuriy Kozlov (yuriy-kozlov)]

Josef, do you have the same error in the terminal (please post, as an attachment), or just in the GUI?
There are a couple different bugs posted in the comments here, and the error in the GUI provides no useful information. Developers need the python trace from the console output both to tell apart the different bugs and to diagnose them.

[Joseph Augustin (joseph-augustin)]

Yuriy, I did not get the same error messages.
I attached the output of the commands:
:~$ kcmshell displayconfig
:~$ sudo kcmshell displayconfig

For :~$ systemconfig
I didn't get anny errors.

Hope I could help the project.

Note: I'm still using the daily release from 3 days ago (09-21) since it was not able to do an "apt-get update".
[Warning: Offtopic]
It said "apt-get update
Reading package lists... Error!
E: Unable to write mmap - msync (2 No such file or directory)
E: The package lists or status file could not be parsed or opened."

But this is another bug and will look now if there is already a bugreport for that.

[Joseph Augustin (joseph-augustin)]

On Kubuntu Gutsy Beta it seems to be fixed. I did not have these problems anymore with the live version.
Shall we mark it as fixed?

[Amit Kucheria (amitk)]

I upgraded from Feisty (with the problem) to Gutsy Beta. The problem is still present.

[Nikolai (imaginee)]

I have the same problem and was able to locate the cause I think.

I'm using two monitors and have the following device section in the xorg.conf.

Section "Device"
        Identifier "nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300]"
        Driver "nvidia"
        BusID "PCI:1:0:0"
        Option "TwinView" "on"
        Option "TwinViewOrientation" "Clone"
        Option "MetaModes" "1280x1024, 1280x800"
        Option "TVOutFormat" "COMPOSITE"
        #Option "ConnectedMonitor" "TV"
EndSection

With TwinView "On" the module fails to load and I think it is because it does not
recognize the meta modes correctly. (See python failing with a list error below).

Error output:

Pythonize constructor -- pid = 8503
[]
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, 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 392, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 411, in _finalizeInit
    self.setLayout(gfxcard._getDetectedLayout())
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 965, in setLayout
    gfxcard.setLayout(XSetup.LAYOUT_CLONE)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1177, in setLayout
    screen._resyncResolution()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1854, in _resyncResolution
    self.gfx_card.setup.getPrimaryScreen()._resyncResolution()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1810, in _resyncResolution
    (preferred_width,preferred_height) = self.getAvailableResolutions()[-1]
IndexError: list index out of range
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 42, in apport_excepthook
    binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))
AttributeError: 'module' object has no attribute 'argv'

Original exception was:
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, 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 392, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 411, in _finalizeInit
    self.setLayout(gfxcard._getDetectedLayout())
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 965, in setLayout
    gfxcard.setLayout(XSetup.LAYOUT_CLONE)
  File "/var/lib/python-support/python2.5/displa...

[Pouletic (pouletic)]

I was trying to output to a second display and discovered that there is no way to click "Accept" when changing settings in Monitor & Display. When i run kcontrol from the konsole i get these error messages when clicking on the checkbox to enable dual displays:

Original exception was:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1474, in slotSecondMonitorToggled
    self.xsetup.setLayout(self.secondary_options[pressed_id])
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 965, in setLayout
    gfxcard.setLayout(XSetup.LAYOUT_CLONE)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1177, in setLayout
    screen._resyncResolution()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1854, in _resyncResolution
    self.gfx_card.setup.getPrimaryScreen()._resyncResolution()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1810, in _resyncResolution
    (preferred_width,preferred_height) = self.getAvailableResolutions()[-1]
IndexError: list index out of range

Look familiar?

My video card is an Nvidia Geforce 4 Ti.

[Niels tijssen (tijssenn)]

During the a fresh install of the Hardy heron alpha 3 this bug surfaces again on my system.

CPU AMD athlon 64 3200 +
ATI X800 pro.
2 GB RAM.

Error message supplied by "display properties" in Kubuntu.

The module monitor and display could not be loaded.
The diagnostics is:

Library files for libpython2.5.so not found in paths

Possible reasons:
- An error occurred during your last KDE upgrade leaving an orphaned control module.
- You have old third party modules lying around.

Output of kcmshell diaplayconfig

tijssenn@tijssenpenguin:~$ kcmshell displayconfig

Pythonize constructor -- pid = 7492
Python interpreter initialized!

Pythonize constructor -- pid = 7492
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/displayconfig.py", line 19, in <module>
    from qt import *
ImportError: /usr/lib/python2.5/site-packages/qt.so: undefined symbol: PyUnicode_Type
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 36, in apport_excepthook
    from cStringIO import StringIO
ImportError: /usr/lib/python2.5/lib-dynload/cStringIO.so: undefined symbol: _Py_ZeroStruct

Original exception was:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/displayconfig.py", line 19, in <module>
    from qt import *
ImportError: /usr/lib/python2.5/site-packages/qt.so: undefined symbol: PyUnicode_Type
error: ***failed to import module

kdecore (KProcess): WARNING: _attachPty() 12
X Error: BadValue (integer parameter out of range for operation) 2
  Major opcode: 113
  Minor opcode: 0
  Resource id: 0x3c00007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 10
  Minor opcode: 0
  Resource id: 0x3c00007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 7
  Minor opcode: 0
  Resource id: 0x3c00007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 6
  Minor opcode: 0
  Resource id: 0x3c00007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 25
  Minor opcode: 0
  Resource id: 0x3c00007

[Igor Tarasov (tarasov-igor)]

Kubuntu Hardy alpha 4 live session - most of kcontrol wont work due to missing libpython2.5.so problem. sudo ln -s /usr/lib/libpython2.5.so.1.0 /usr/lib/libpython2.5.so solves it.

After that most of kcontrol work pretty well, except of monitor & display applet due to this bug:

https://bugs.launchpad.net/ubuntu/+source/kde-guidance/+bug/173768

[sun-wukong (sun-wukong)]

This bug is NOT the one currently in Hardy Heron alphas, even if it seems the same.

Hardy comes with a new version of Xorg that uses a different structure for /etc/X11/org.conf. Here's the problem.
If you want to follow the Hardy bug, please register to bug #173768

[Scott Kitterman (kitterman)]

From what I can determine, this is all either fixed or covered in another bug I'm working on.