I tried to run some commands as an unpriviledged user (connection to dbus forbidden by policy). The syslog always gives me messages of the form: May 23 18:02:53 pluto [powersave]: ERROR (dbusSendMessageGeneric:209) Error: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "com.novell.powersave.request" member "SchemesGet" error name "(unset)" destination "com.novell.powersave")
But the output from the powersave client is not very good and consistent. no_connect_no_rights_error() seems to be the correct error function in this case but is not used unfortunately. It should be clear to the user that he is lacking the sufficient rights to connect to powersaved. # powersave -U / -u / -m Cannot connect to powersaved. Is the daemon running? (dbus error) # powersave -f / -l / -A / -x An error occured. Make sure that the powersave daemon is running and use -v to increase verbose level and have a look into syslog. # powersave -c / -K / -L Error: 9 - dbus error # powersave -o An error occured. Make sure that the powersave daemon is running and use -v to increase verbose level and have a look into syslog. 4673: arguments to dbus_message_iter_init() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1442. This is normally a bug in some application using the D-BUS library. dbus message iterator looks uninitialized or corrupted 4673: arguments to dbus_message_iter_get_arg_type() were incorrect, assertion "_dbus_message_iter_check (real)" failed in file dbus-message.c line 1561. This is normally a bug in some application using the D-BUS library. # powersave -s unknown reply code to 'BatteryState' request # powersave -C An error occured. Make sure that the powersave daemon is running and use -v to increase verbose level and have a look into syslog. 4681: arguments to dbus_message_iter_init() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1442. This is normally a bug in some application using the D-BUS library. dbus message iterator looks uninitialized or corrupted 4681: arguments to dbus_message_iter_get_arg_type() were incorrect, assertion "_dbus_message_iter_check (real)" failed in file dbus-message.c line 1561. This is normally a bug in some application using the D-BUS library. No clients connected Can someone look into this? Especially -C and -o seem to be valid bugs. Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ powersave-devel mailing list [email protected] http://forge.novell.com/mailman/listinfo/powersave-devel
