User Management Module doesn't load

[Francis]

Binary package hint: kde-systemsettings

systemsettings -> user management -> the module "user management could not be loaded", with possible diagnostics listed. Above it speaks of Admin permissions required, but that doesn't change things, and once again -- the module fails to load. Terminal output:

----------------------------------
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
adding User Management /usr/share/applications/kde/userconfig.desktop

Pythonize constructor -- pid = 7003
Python interpreter initialized!

Pythonize constructor -- pid = 7003
no user removed
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_userconfig
  File "/var/lib/python-support/python2.4/userconfig.py", line 1694, in create_userconfig
    return UserConfigApp(parent, name)
  File "/var/lib/python-support/python2.4/userconfig.py", line 275, in __init__
    self.__updateGroupList()
  File "/var/lib/python-support/python2.4/userconfig.py", line 515, in __updateGroupList
    self.__selectGroup(self.selectedgroupid)
  File "/var/lib/python-support/python2.4/userconfig.py", line 521, in __selectGroup
    lvi = self.groupidsToListItems[groupid]
KeyError
error: *** runFunction failure
;
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Pythonize constructor -- pid = 7021
Python interpreter initialized!

Pythonize constructor -- pid = 7021
no user removed
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_userconfig
  File "/var/lib/python-support/python2.4/userconfig.py", line 1694, in create_userconfig

return UserConfigApp(parent, name)
  File "/var/lib/python-support/python2.4/userconfig.py", line 275, in __init__

self.__updateGroupList()
  File "/var/lib/python-support/python2.4/userconfig.py", line 515, in __updateGroupList

self.__selectGroup(self.selectedgroupid)
  File "/var/lib/python-support/python2.4/userconfig.py", line 521, in __selectGroup

lvi = self.groupidsToListItems[groupid]
KeyError

error: *** runFunction failure
----------------------------------------

Note: user management module also doesn't load up from kcontrol. Let me know how I can be of more help.
This is on the live (desktop) image of Kubuntu Edgy RC

[Jurjen Oskam (jurjen-stupendous)]

I just installed the released Edgy, and the User Management module doesn't load here, too. Seemingly with the same symptoms.

[Frode M. Døving (frode)]

Does running it from the commandline work?

Kmenu -> System -> Konsole
$ kdesu userconfig

[Peter-Jan Randewijk (pjrandew)]

Same problem.

How can one set the GroupID via the Konsole?

[Richard Lennox (rlx-01)]

I had this problem. May or may not have the same cause:
Last msg issued was :

[Errno 2] No such file or directory: '/etc/shadow'

Adding shadow password support fixed it. My opinion is this should be turned on by default.

You can switch it on by:

        sudo shadowconfig on

See /usr/share/doc/passwd/README.Debian

[DaveQB (david-dward)]

Same problem here. Both with my upgraded from Dapper 64-bit desktop and also running the Live Install CD has the same problem.

Frode's suggestion of running from the CL works though.
Shadow exists on the Live Install CD though

david@ubuntu:~$ ls -l /etc/shadow
-rw-r----- 1 root shadow 827 2007-01-07 03:44 /etc/shadow

[Ariel Faigon (ariel.faigon)]

Same problem here, still on Edgy (6.10)

I actually did have a /etc/shadow and obviously it was functional since it its passwords were required/working all the time. However: running

     sudo shadowconfig on

revealed several inconsistencies, including:

     invalid password file entry (had a comment in the file)
     'xyz' is a member of the 'lp' group in /etc/group but not in /etc/gshadow
     add group 'abc' in /etc/gshadow ?no matching group file entry in /etc/gshadow
     'abc' is a member of the 'dspam' group in /etc/gshadow but not in /etc/group

Fixing all these errors, made shadowconfig happy.

It is possible that shadowconfig simply fails when run in batch and so shadow remains partially disabled even though it seems to work for most tasks. The user management module failing to load in system-settings seems to be the exception rather than the rule.

[DaveQB (david-dward)]

Just checked mine and its working now.

No reason as to why.

[Yuriy Kozlov (yuriy-kozlov)]

Bug 34311 reports the same error as this one.