-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/11/12 20:05, Frank Griffin wrote: > On 11/24/2012 08:20 AM, Anne Wilson wrote: >>> >> In Cauldron, I'm once again struggling with the inability to make >> configuration changes. I first met it and wrote about it when >> trying to get wifi working. Now I'm trying to change shutdown >> option, and meet the same problem again. >> >> "Administrator authorisation is required to change the Login >> Manager settings" > > Do you have an I-take-everything cauldron or a pick-and-choose > cauldron ? Nobody ever seems to announce policy changes on this > ML, but I gather that the winds of favor have moved from > ConsoleKit to PolicyKit (or maybe it's the other way around), so > if, for example, ConsoleKit is now deprecated but you still have > packages installed that want it, you might be getting the errors > you mention below. > I have a fairly standard setup with the usual sort of apps, most of my time being in using Dolphin, Chrome, Thunderbird with dips into various other apps. I update by using 'urpmi --auto-update'. These problems seem to have arrived very recently.
>> "Unable to authenticate/execute the action: DBus Backend error: >> could not contact the helper. Connection error: The name >> org.freedesktop.ConsoleKit was not provided by any .service >> files. Message error: Did not receive a reply. Possible causes >> include: the remote application did not send a reply, the >> message bus security policy blocked the reply, the reply timeout >> expired, or the network connection was broken (code 7)" >> > >> Caulron was behaving so well until a couple of weeks or so ago. >> It's driving me mad at the moment. Is there any way out of this >> mess? and also, asked in another thread, any way to stop it >> locking my screen if I look away for a couple of minutes. > > This was covered extensively in another thread. KDE Power > Management is AFU at the moment. If you have set PM to not turn > off the display no mattter what, it rolls the dice and chooses > some random value for dpms, which determines when the screen > blanks (thanks, Colin). There's an open KDE bug for it. > Ah - it's power management settings, then. OK, I'll look at that. I have been used to the screen blanking after quite a short time, but this insistence on a password is new behaviour. I don't think it's a good idea for things to change dramatically without any sort of warning. When the behaviour is the result of some other deep change it is hard to understand :-) > At present, about all you can do to stay sane is put "xset -dpms" > in your rc.local and also at the tail end of whatever scripts you > use for "urpmi --auto-update" (as any update to KDE PM will > probably undo the -dpms). > Thanks. That's worth knowing about. Anne - -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCyCX0ACgkQj93fyh4cnBd6LQCfcbg/dhPkAuV9dzx9cVfI5E4n +44AoIeQhtLFFyL9MhZeGNpSYXPzHOy2 =saY0 -----END PGP SIGNATURE-----
