Comment 19 for bug 175909

I have been toying around with the live session of Hardy pre-RC a bit more and I noticed this (steps to reproduce it):

1) I boot live CD
2) ps aux | grep dcopserver leads to: "ubuntu <pid and stuff> dcopserver [kdeinit] --nosid"

Scenario 1 (bug):
3) I go into System Settings, go into Monitor & Display settings, hit the Administrator Mode button.
The red rectangle shows for a short while, than it gets back no non-administrator display.
4) RMB on KNetwork manager in tray and choosing "Manual Config" leads to big error dialog:
DCOP communications error
There was an error setting up inter-process communications for KDE ..cut.. message:
Authentication Rejected, reason: None of the authentication protocols specified are supported and host-based authentication failed ...cut.. (something like make sure dcopserver is running)
5) ps aux | grep dcopserver leads to:
ubuntu <pid and stuff> dcopserver [kdeinit] --nosid
root <pid and stuff> dcopserver [kdeinit] --n

Scenario 2 (ok):
3) RMB on KNetwork manager icon in tray and choosing "Manual Config" -> the network configuration dialog is shown with working Administration rights, so I can change setup.
4) System Settings -> Monitor & Display -> Administrator Mode -> leads to working administrator mode with the "red rectangle" dialog, and I can change settings
5) ps aux | grep dcopserver leads to (same output like in Scenario 1 as far as I can tell, unless my eyes are fooling me):
ubuntu <pid and stuff> dcopserver [kdeinit] --nosid
root <pid and stuff> dcopserver [kdeinit] --n

(all outputs/messages have been written down to paper firstly and than retyped, so of course the 5th step output here is identical, it's C'n'P, but you will have to believe me it was really the same)

So basically the only difference between bug or working is whether the administrator authentication is called from KNetwork (works) or from System Settings (fails). I hope this helps.