systemsettings doesn't load Display, Disk and Filesystems control module

No need for a second task.

Can you run "kcmshell displayconfig" and "kcmshell mountconfig" from terminal/shell and provide the output?

user@computer:~ $ kcmshell displayconfig
Pythonize constructor -- pid = 21073
Python interpreter initialized!
Pythonize constructor -- pid = 21073
ScimInputContextPlugin()
~ScimInputContextPlugin()

user@computer:~ $ kcmshell mountconfig
Pythonize constructor -- pid = 21234
Python interpreter initialized!
Pythonize constructor -- pid = 21234
ScimInputContextPlugin()
~ScimInputContextPlugin()

Both of the modules work when launched this way, but don't work when launched from system settings.

Dapper beta.

I get the same error.

I tried to load "kcmshell displayconfig" after some misc text and errors, I get the "KDE Control Module". After entering "Administrator Mode" I get the same error message in the body of the control module window.

Here is the konsole text:

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

Pythonize constructor -- pid = 5589
Python interpreter initialized!

Pythonize constructor -- pid = 5589
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 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 1555, in _finalizeInit
    self._computeSizesFromMonitor()
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 1660, in _computeSizesFromMonitor
    self.mode_list = GetMonitorModeDB().getAvailableModes(monitor_model,self.monitor_aspect)
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 2978, in getAvailableModes
    hsync_list = self._list_from_string(monitor.getHorizontalSync())
  File "/usr/lib/python2.4/site-packages/displayconfigabstraction.py", line 3002, in _list_from_string
    l.append( (float(tmp[0]), float(tmp[1])) )
ValueError: empty string for float()
error: *** runFunction failure
;
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Pythonize constructor -- pid = 5606
Python interpreter initialized!

Pythonize constructor -- pid = 5606
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)...

Ok Paul. Can you please go to a shell and run:

    /usr/sbin/ddcprobe

and report the output back here. Also can you upload your /etc/xorg.conf file here and describe what screen and graphics card you are using, (or laptop). thanks.

I should point out that I'm running Dapper beta on an x86 machine, if that makes any difference.

Here's the output of /usr/sbin/ddcprobe:

paul@ubuntu:~$ sudo /usr/sbin/ddcprobe
Password:
vbe: VESA 2.0 detected.
oem: ATI RADEON 9200
memory: 16384kb
mode: 800x600x16
mode: 1024x768x16
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
edid:
edid: 1 1
id: d569
eisa: AOCd569
serial: 04cd2c99
manufacture: 5 1998
input: sync on green, analog signal.
screensize: 28 21
gamma: 2.600000
dpms: RGB, active off, suspend, standby
timing: 640x480@60 Hz (VGA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
ctiming: 640x480@85
ctiming: 800x600@85
ctiming: 1024x768@85
dtiming: 640x480@85
dtiming: 800x600@85
dtiming: 1280x1024@70
dtiming: 800x600@85

Here's the /etc/xorg.conf file:

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
 Identifier "Default Layout"
 Screen 0 "aticonfig Screen 0" 0 0
 InputDevice "Generic Keyboard"
 InputDevice "Configured Mouse"
 InputDevice "stylus" "SendCoreEvents"
 InputDevice "cursor" "SendCoreEvents"
 InputDevice "eraser" "SendCoreEvents"
EndSection

Section "Files"

 # path to defoma fonts
 FontPath "/usr/share/X11/fonts/misc"
 FontPath "/usr/share/X11/fonts/cyrillic"
 FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
 FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
 FontPath "/usr/share/X11/fonts/Type1"
 FontPath "/usr/share/X11/fonts/100dpi"
 FontPath "/usr/share/X11/fonts/75dpi"
 FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

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

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc104"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configu...

Hello,

I have got exactly the same problem. Has anybody got the solution since it is a bit problematic...

Thanks a lot,

Aymeric

This bug has reappeared after updating Edgy on Sept. 30, 2006. The beta was fine, but after updating, these modules no longer work, either from kde-systemsettings or from kcontrol. I haven't tried "kcmshell displayconfig" from the command line, but will do so tonight when I am at home.

I could confirm this bug before. However, the modules all seem to be loading fine for me now...

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..

Confirming due to a number of duplicates as well as I had this issue previously as well and thought it had been fixed.

The problem has apparently been resolved for me after a recent update.
Thanks!

On 2/16/07, Richard Johnson <email address hidden> wrote:
>
> Confirming due to a number of duplicates as well as I had this issue
> previously as well and thought it had been fixed.
>
> ** Changed in: kde-systemsettings (Ubuntu)
> Importance: Medium => High
> Status: Needs Info => Confirmed
>
> --
> systemsettings doesn't load Display, Disk and Filesystems control module
> https://launchpad.net/bugs/38692
>

Can anyone else confirm the fix?

With Edgy/Kubuntu the original load did not have this problem.
It appeared on all 4 of my systems after an update in the middle of January.
The problem appeared "universal" so I did not attempt reporting a problem, assuming a fix would be forthcoming.
I update my systems at least once a week and the problem persists.
There is not debate in my mind the problem is not as yet solved.
I have 4 systems still showing the problem.

I still have the same problem.
Is there any workaround here?
There is settings window snapshot in attachment.

$ 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
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably crashed.

Pythonize constructor -- pid = 8607
Python interpreter initialized!

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

@prokher: Your problem is a different issue. Use "kdesu kcmshell displayconfig" or "kdesu displayconfig", either should work.

$ kdesu displayconfig
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
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
  Resourc
e 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
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
Reusing existing ksycoca
kio (KService*): WARNING: Invalid Service : basket_config_features.desktop
kio (KService*): WARNING: Invalid Service : basket_config_notes.desktop
kio (KService*): WARNING: Invalid Service : /usr/share/applications/kde/kbarcode-label.desktop
kio (KSycoca): ERROR: No database available!
Traceback (most recent call last):
  File "/usr/bin/displayconfig", line 1720, in <module>

displayapp = DisplayApp()
  File "/usr/bin/displayconfig", line 441, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/usr/share/python-support/kde-guidance/displayconfigabstraction.py", line 72, in __init__
    self.xorg_config = xorgconfig
.readConfig(xorg_config_filename)
  File "/usr/share/python-support/kde-guidance/xorgconfig.py", line 657, in readConfig
    raise ParseException,"Unknown line type '%s' on line %i" % (first,line)
xorgconfig.ParseException: Unknown line type 'section' on
line 61
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]))
IndexError
:
list index out of range

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/displayconfig", line 1720, in <module>

displayapp = DisplayApp()
  File "/usr/bin/displayconfig", line 441, in __init__

self.xsetup = XSetup(self.xconfigpath)
  File "/usr/share/python-support/kde-guidance/displayconfigabstraction.py", line 72, in __init__

self.xorg_config = xorgconfig.readConfig(xorg_config_filename)
  File "/usr/share/python-support/kde-guidance/xorgconfig.py", line 657, in readConfig

raise ParseException,"Unknown line type '%s' on line %i" % (first,line)
xorgconfig
.
ParseException
:
Unknown line type 'section' on line 61

$
And program terminated w/o any GUI window.

$kdesu kcmshell displayconfig
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
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 145
  Minor opcode: 3
  Resour...

I have had this bug in Feisty and still have it in Gutsy.

OUTPUT--------------------------
ed@summit:~$ kcmshell displayconfig

Pythonize constructor -- pid = 5315
Python interpreter initialized!

Pythonize constructor -- pid = 5315
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 "/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 397, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1116, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1603, in _finalizeInit
    (cw,ch) = self.available_sizes[0]
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 397, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1116, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1603, in _finalizeInit
    (cw,ch) = self.available_sizes[0]
IndexError: list index out of range
error: *** runFunction failure
;
ed@summit:~$ kdesu /usr/sbin/ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: nv41 Board - e275h0 Chip Rev
memory: 262144kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 3
id: e009
eisa: DELe009
serial: 3034384c
manufacture: 1 2005
input: separate sync, composite sync, sync on green, analog signal.
screensize: 43 27
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640...

I've found the workaround which works for me.
I run "sudo dpkg-reconfigure -phigh xserver-xorg", it completely rewrite xorg.cong with default one.
After that configuration dialog works OK.
Probably it will help.

Has anyone observed the problem on Hardy?

Yes, I'm experiencing this in hardy
I tried displayconfig and kcmshell displayconfig but this didn't work

(using radeonhd, if it matters)

This bug happened to me soon after installing Kubuntu 7.10 on what was previously a Windows only box. System is dual monitor. The module stopped working a few steps after after I had successfully enabled the second monitor. The monitor first came up as a generic with only 640x480 available, so I reactivated the module to first specify the secondary monitor's type so I could up it to decent resolution. Type was on the supported list. I made multiple changes, __including adjusting gamma on secondary monitor__, before i closed the module this time. Then I went through log-off and re-log-in which was what the program said was necessary to apply some of the changes..On re-log-in, the two monitor's respective gammas didn't seem to change much if at all, so I activated the module again, and changed just gamma on the secondary monitor, by a bigger step. Again, system indicated a log out was necessary to apply the settings. I logged out and back in, saw no apparent change, so I went through actual shut down and reboot. On reboot, secondary monitor gamma was very high, like both changes I made were applied sequentially, and the module stopped working.

   I am of the opinion that the system should direct the user to go through an actual reboot and not just a re-log in to apply these setting changes. I also suspect that inadvertently adjusting a gamma setting outside the normal limits is one of the ways to cause the module to fail, and worse, it looks like the kind of failure that could theoretically damage hardware, or at least leave the user glare blinded!.

Has happened to me with Disk and Filesystems on Hardy RC. I had rebooted after doing the update from Gutsy to Hardy RC and was opening all the System settings one by one to look at any new features and the Disk and Filesystems module failed to load. However after i closed and reopened System settings, the Disk and Filesystems module worked fine.
I will be updating couple of more computers after the release on the 24th, will try reproducing the bug and post the results.

With Hardy Release: happens for "Disk and Filesystems" and "User management" modules if they are opened after opening "Printers" module

Steps to reproduce:
1) open "System Settings" or run systemsettings in konsole
2) open "Printers" and press the back button to go back
3) open "Disk and Filesystems" or "User management"

---Package Information---
$apt-cache policy kde-systemsettings
kde-systemsettings:
  Installed: 0.0svn20070312-0ubuntu5
  Candidate: 0.0svn20070312-0ubuntu5
  Version table:
 *** 0.0svn20070312-0ubuntu5 0
        500 cdrom://Kubuntu 8.04 _Hardy Heron_ - Release i386 (20080422.1) hardy/main Packages
        500 http://in.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

---Terminal output when opening Disk and Filesystems---
$systemsettings
adding Printers /usr/share/applications/kde/printers.desktop
QObject::connect: No such slot KMMainView::slotServerAccessConfigure()
QObject::connect: (sender name: 'server_access_configure')
QObject::connect: (receiver name: 'MainView')
adding Disk & Filesystems /usr/share/applications/kde/mountconfig.desktop

Pythonize constructor -- pid = 12938
Python interpreter initialized!

Pythonize constructor -- pid = 12938
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_mountconfig
  File "/var/lib/python-support/python2.5/mountconfig.py", line 3285, in create_mountconfig
    return MountConfigApp(parent, name)
  File "/var/lib/python-support/python2.5/mountconfig.py", line 2878, in __init__
    self.mounttable = MountTable('/etc/fstab','/etc/mtab')
  File "/var/lib/python-support/python2.5/mountconfig.py", line 1237, in __init__
    fhandle = codecs.open(self.fstab_filename,'r',locale.getpreferredencoding())
  File "/usr/lib/python2.5/locale.py", line 514, in getpreferredencoding
    setlocale(LC_CTYPE, "")
  File "/usr/lib/python2.5/locale.py", line 478, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/apport_python_hook.py", line 71, in apport_excepthook
    pr['PythonArgs'] = '%r' % sys.argv
AttributeError: 'module' object has no attribute 'argv'

Original exception was:
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_mountconfig
  File "/var/lib/python-support/python2.5/mountconfig.py", line 3285, in create_mountconfig
    return MountConfigApp(parent, name)
  File "/var/lib/python-support/python2.5/mountconfig.py", line 2878, in __init__
    self.mounttable = MountTable('/etc/fstab','/etc/mtab')
  File "/var/lib/python-support/python2.5/mountconfig.py", line 1237, in __init__
    fhandle = codecs.open(self.fstab_filename,'r',locale.getpreferredencoding())
  File "/usr/lib/python2.5/locale.py", line 514, in getpreferredencoding
    setlocale(LC_CTYPE, "")
  File "/usr/lib/python2.5/locale.py", line 478, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting
error: *** runFunction failure
;

---Terminal output when opening User management---
$ systemsettings
adding Printers /usr/share/applications/k...

confirming

Displayconfig is no longer maintained, and will not be receiving any more bugfixes.