Version: (using Devel) OS: Linux Installed from: Compiled sources To date, I've been able to use a fully functional KDE desktop without the need for the kit-of-the-week. Since 4.4, I've lost even MORE functionality for not using polkit. This integration needs to be rethought. It sucks! Does KDE expect me, a user, to integrate polkit into my system? Do you know how challenging that is, to redo the entire auth. framework? It would be great if the polkit backend would be optional. Let kauth handle this stuff, which has worked GREAT for years and years. Jumping onto the polkit bandwagon does nothing but discourage users. Please do not take away functionality on my desktop, because supporting a framework that has been used for years is "too much work." Kindly reconsider this requirement, as it's really not the simplest of tools to integrate. Users would greatly appreciate the lack of this requirement, as I think alot of KDE users remain on KDE, for their lack of incorporating this stuff by nature.
Thanks for the bug report. Any new technology needs some time to mature until it is fully usable without any hindrance. Remember that Plasma needed more than a year after the initial release to get into a state where people accepted it. PolicyKit already is optional, as long as you offer another KAuth backend. So if the problems clearly are related to PolicyKit itself, a different backend could be developed. But for now we have to use what is available. To further improve KAuth/PolicyKit framework and integration into KDE, we need more specific tasks to work on. If you can describe problems, bugs, or missing functionality in the current KDE SC 4.4 release, we would be glad to hear them from you. Thanks in advance.
> To further improve KAuth/PolicyKit framework and integration into KDE, we need > more specific tasks to work on. If you can describe problems, bugs, or missing > functionality in the current KDE SC 4.4 release, we would be glad to hear them > from you. > > Thanks in advance. Of course! In 4.3.x, I can, for example, use the font installation tool in system settings. In 4.4.x, this feature is no longer available. After digging into the sources, sure enough, polkit is required. Can I install fonts on my own, outside of KDE? Sure. To me, I've LOST functionality in my KDE desktop. Distributions are now forced to adapt to policykit (polkit? polkit-qt? ) in order to have a feature-complete desktop. This is not like depending on a new library - it's completely changing the auth. framework on a system-wide level. I'm not sure what to do. Install polkit on my own? That would be recompiling critical components like hal, writing my own policies, changing the way permissions are handled system-wide. Should I quit using KDE? I've been a happy slackware user for about 7 years - should I change distros? To me, requiring a distribution to adopt to polkit policies JUST to have something like font installation (which definitely is capable of functioning without it - see 4.3!) is something from the gnome book.
From what I understood the policykit backend enables kde applications to run certain tasks with a higher capability, not quite the same but close enough to "run as root". The simplest tools that are available on almost all systems for that task are sudo and su. So maybe a new, very basic backend could be added that just uses those tools? The only thing I would be afraid of here is a Vista like confirmation dialog mess.
Or we could even get back using stick and stones and screw everything. Why not? It seems reasonable to me, I don't expect modern civilization to force me into using a fridge!! Now seriously, either live with the fact that technology is evolving and you don't need to have polkit installed to compile KDE (the component you specified is NOT using KAuth, but polkit directly, which is discouraged, and you probably want to file a bug against it if you want this situation getting fixed), or go ahead and write another backend for KAuth which does not use polkit, even if there is no proper equivalent around these days. You can simply write something that asks for your password, checks it, and bang. But I'm definitely marking this bug as invalid.
this should not be closed as we are out applications that did work and still should . PAM should not be forced on us any more than you saying we should use a certain security firm that we don't want to use. So right now all I see is kde only supporting a fully working desktop etc on linux/Unix platforms that only use PAM. It was KDE that desided to use a know way that depends on PAM. f this is to work on all of those platforms then it abviuoly need to be FIXED. This Kath sounds good that it will work with modules . But again why did kde use it and not provide the module. So far again it looks like tis because kde isn't willing to work with all the platforms. All i care about is if KDe resides to use something like this than they think more first about making it work for all the PLATFORMS. Platforms is plural == ALL==100%. . This crap of stick and stones and screw everything , is just crap. Can these things work with out pam YES. This crap of everything new is not true . Just like the main menu all the peopel finally got back the better one , setting menu etc . I do like some new things because they do work better but it's completely idiotic to think all new is going to be liked . Among KDE's products are a modern desktop system for Linux and UNIX platforms, this statement should be changed to Among KDE's products are a modern desktop system for our favorite Linux and UNIX platforms that use PAM, cause it sure aint holding true any more . KDE made this a problem but wants to pass the buck to some one else. Plus shows no sign of owning up to it . Yes we know this "don't need to have polkit" but as we say it means these thongs don't work . What is wrong with all you people that answer these bugs telling us to live with out what we know should work still but is blatantly broken with no remorse to want to fix it. Being told wontfix, to bad get modern, PAM is the best security firm for linux when it isn't . The fact is I don't believe the developer never knew that not all the platforms use or want to use Pam. But chose to use it with out making the work around to use both. Amyway Althou maybe but I'm still in great doubt this might get it fixed "and you probably want to file a bug against it if you want this situation getting fixed" but where what bug do we put it under etc . So far I've been lead down the garden path to no where . Even thou not kde who should have a fix already I got a patch its still doesn't work and the module one sounds like the better way . workspace as far as I know is working on porting over to kath and kde bindings need to be too. But where do we go to start a bug fix thanks . also date/time doesn't work even with the polkit-1 patch and Kath should be using that . ugh
We had almost a one hour conversation on IRC and I'm not going to add anything else. Repeating everything over and over won't help, and you keep failing in understanding, so I'm just giving up.
And one last time: I don't give a big, huge crap about PAM and never did, and you people are just paranoid about that. Face this fact. Don't like this -> go and use a system without polkit, which to date is Mac OS or Windows, if you want a decent desktop. Have fun.