On Saturday 25 August 2012 04:29:19 Daniel Nicoletti wrote: > 2012/8/23 Christoph Feck <christ...@maxiom.de>: > > On Wednesday 22 August 2012 21:39:11 Daniel Nicoletti wrote: > >> two years ago I started print-manager, at that time > >> I was using Debian which is affected by this bug: > >> https://bugs.kde.org/show_bug.cgi?id=271957 > >> because of this (and the fact I'm not a python fan > >> to fix the issue) I started print-manager a C++ > >> implementation that could replace the current > >> solution and fix the bug I had. > > > > Given the fact that the above mentioned bug is about > > authorization, what does printer-manager do to avoid bug 242648, > > and how could its methods be transfered to other modules needing > > KAuth, such as the kdm or clock modules? > > Well CUPS has it's own API for authorization, which is why I > avoided the polkit solution s-c-p-gnome now uses. It wasn't easy > to make it work right since CUPS API blocks, but it works reliable > now that I wrapped it on a thread.
Okey, so what you do in printer-manager is completely unrelated to kauth. What I am interested in is, how we can use your knowledge to avoid the mistake in the kauth design for frameworks. If I understand mentioned bug correctly, it is not possible to fix the crash with the current design of kauth/polkit interaction, because the polkit frameworks expects the password dialog to run in its own processes. If GNOME still uses polkit, how did they solve the out-of-process password dialogs? > kde workspace would be a good place to stay. Hm, kdeadmin is not moved to git yet, but I guess it still would be possible to create a "KDE Admin" project group. Christoph Feck (kdepepo)
