[Bug 35581] dapper beta: administrator mode doesn't work in systemsettings

[TuxFan]

I thought today's update fixed my problem, but it actually made it worse...

Does someone have an idea which packet this bug really belongs to? It would help tracking weather this is fixed in some version or not. My current kde-systemsettings seems to be 0.0svn20060413-0ubuntu1.

After updating I tried to add a printer (using CUPS as the print system). I got the red borders after giving the right pw to the administrator mode password prompt. I have two printers, one SMB and  one IPP, but both of their install failed to this message after choosing the right driver (which works well on Breezy):

----8<----
Error - KDE Control Module

Unable to load the requested driver:
                                                                                                                                                            Unable to create the Foomatic driver
[HP-LaserJet_1320,Postscript]. Either that driver does
not exist, or you don't have the required permissions                                                                                                       to perform that operation.
----8<-----

After closing this message and canceling the installation the red borders were gone...

I then tried a wrong password to the prompt... and got the red borders! I really was in administrator mode, since I could remove printers from the list. (By printers I mean the "print to file" etc. that are there by default.)

But adding a printer with a wrong pw didn't work, so I'm also guessing like Pascal above, that there are two separate bugs.

-- 
dapper f5 live: administrator mode doesn't work in systemsettings
https://launchpad.net/bugs/35581