I just started seeing a similar problem, but my output of "$ kcmshell
displayconfig" is a bit different:
$ kcmshell displayconfig
Pythonize constructor -- pid = 11128
Python interpreter initialized!
Pythonize constructor -- pid = 11128
open /dev/mem: Permission denied
VESA BIOS Extensions not detected.
Xlib: extension "XFree86-VidModeExtension" missing on display ":1.0".
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
1599, in _finalizeInit
(self.redgamma, self.greengamma, self.bluegamma) =
self.x_live_screen.getGamma()
File "/usr/lib/python2.4/site-packages/xf86misc.py", line 50, in getGamma
return ixf86misc.GetGamma(self.display,self.screenid)
SystemError: error return without exception set
error: *** runFunction failure
;
The problem is the same whether or not I run as root. The line about
"VidModeExtension" may be important, although my Xorg.0.log file
indicates that the extenstion _was_ loaded. Whetever the cause of the
problem, the actual bug seems to be in DisplayApp(parent, name), which
is probably just returning a null pointer when it's not supposed to..
--
systemsettings doesn't load Display, Disk and Filesystems control module
https://launchpad.net/bugs/38692
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
