Administrator button fails to work in kde-settings and kcontrol
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kde-systemsettings (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This bug is identical to:
Bug #15001, first reported on 2005-04-05 by Aric Wilisch
Administrator mode not working
and solved that year. It has re-surfaced and has also been reported again by Rohan Dhruva on 30 Nov 07. I can confirm what he has siad at:
https:/
but am reporting it as new because the older bug is closed.
It happened out of teh blue on a fresk Kubuntu Gutsy installation. Action taken included completely re-installing Kubuntu and also
sudo apt-get install --reinstall kcontrol kde-systemsettings
neither of which has helped.
Running either systemsettings or kcontrol from the konsole and clicking "Administrator Mode" for "Network Setings" does nothing but the console error messages are:
*******
-------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /root/.
and start dcopserver again.
-------
WARNING: Waiting for already running klauncher to exit.
WARNING: Waiting for already running klauncher to exit.
WARNING: Another instance of klauncher is already running!
kdeinit: Communication error with launcher. Exiting!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kcmshell (kdelibs): WARNING: Could not find module 'kcm_knetworkco
*******
Could this bug be treated as serious and a workaround suggested please?
Removing /var/tmp/
Thank you.
Related branches
Changed in kde-systemsettings: | |
status: | Fix Committed → Fix Released |
Typing
sudo kcontrol
from the console enables administrator tasks to be accomplished. This is a workaround. There are error messages about uid being 1000 when it should be 0, but it works.
kdesu kcontrol
fails with error messages.
This means that the system is usable now.