| Summary: | sys-auth/policykit error prevents auto mount and gnome-power-manager to function properly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mehmet Giritli <mehmet> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | rose |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mehmet Giritli
2010-05-06 18:03:57 UTC
I don't think: (polkit-gnome-authentication-agent-1:6650): GLib-GObject-WARNING **: cannot register existing type `_PolkitError' (polkit-gnome-authentication-agent-1:6650): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed they seem to affect to other distributions (https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/449378) and doesn't cause any failure like you are seeing on my systems :-/ Do you have a fully updated system? Are you read elog messages (usually in /var/log/portage/elog/summary.log)? Maybe you have an older polkit process still running in your system and causing you these problems... maybe a reboot (or careful revision of "ps axu | less" output could help ;-) Please also provide "emerge -pv polkit polkit-gnome" output Also be sure to, at least, have restarted consolekit to use new version (as elog info suggests) (In reply to comment #3) > Also be sure to, at least, have restarted consolekit to use new version (as > elog info suggests) > Hello Pacho, Sorry for late reply. I was just testing to see the theory I had in mind, which was that all this weirdness might be caused from the parallel startup of the init system that I had... I was having inconsistent behaviour with the above without making any changes to my computer and then I realised that I have my system to start in parallel running of the init scripts, which could explain the randomness in the results. So far, it is working ok, so you might wanna look into that or an extra notice in your elogs.. I have one last question, even though this might not be the right place for it: I want user x, and only user x, to be able to auto mount (mount without auth) the partitions. Isn't it enough in the policykit to grant an explicit right for user x to mount internal drives, while keeping implicit auths at default? Currently, I could not manage this by granting explicit rights to user x but only by modifying implicit rights 'active console' to 'yes' , which enables all the users to mount without auth... (In reply to comment #2) > Do you have a fully updated system? Are you read elog messages (usually in > /var/log/portage/elog/summary.log)? Maybe you have an older polkit process > still running in your system and causing you these problems... maybe a reboot > (or careful revision of "ps axu | less" output could help ;-) > > Please also provide "emerge -pv polkit polkit-gnome" output > [ebuild R ] sys-auth/polkit-0.96-r1 USE="nls pam -debug -doc -examples -expat" 0 kB [ebuild R ] gnome-extra/polkit-gnome-0.96 USE="-debug -doc -examples" 0 kB (In reply to comment #4) > I have one last question, even though this might not be the right place for it: > I want user x, and only user x, to be able to auto mount (mount without auth) > the partitions. Isn't it enough in the policykit to grant an explicit right for > user x to mount internal drives, while keeping implicit auths at default? > > Currently, I could not manage this by granting explicit rights to user x but > only by modifying implicit rights 'active console' to 'yes' , which enables all > the users to mount without auth... > Sadly, I don't know hot to deal with that :-/, maybe some other gnome team members knows but I would suggest you to ask in http://forums.gentoo.org for help Good luck! Please reopen the bug, I have a similar error. If I close the lid my laptop goes seldom to the power save state. Even if it is working the first time after booting, it fails usually if I try it a second time and in .xsession-errors I find similar messages as Mehmet Giritli:
** (gnome-power-preferences:25559): WARNING **: ERROR: Cannot determine if caller is privileged
A new main_window has been created
Traceback (most recent call last):
File "/usr/bin/avahi-discover", line 274, in <module>
main()
File "/usr/bin/avahi-discover", line 269, in main
main_window = Main_window()
File "/usr/bin/avahi-discover", line 63, in __init__
SimpleGladeApp.__init__(self, path, root, domain, **kwargs)
File "/usr/lib64/python2.6/site-packages/avahi_discover/SimpleGladeApp.py", line 108, in __init__
self.new()
File "/usr/bin/avahi-discover", line 254, in new
self.server = dbus.Interface(self.bus.get_object(avahi.DBUS_NAME, avahi.DBUS_PATH_SERVER), avahi.DBUS_INTERFACE_SERVER)
File "/usr/lib64/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib64/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib64/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib64/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib64/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files
** (gnome-power-preferences:26122): WARNING **: ERROR: Cannot determine if caller is privileged
(gnome-power-manager:1682): devkit-power-gobject-DEBUG: DBUS timed out, but recovering
(gnome-power-manager:1682): devkit-power-gobject-WARNING **: Error invoking GetAll() to get properties: 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.
** (gnome-power-manager:1682): WARNING **: ERROR: Cannot determine if caller is privileged
** (gnome-power-manager:1682): WARNING **: ERROR: Cannot determine if caller is privileged
** (gnome-power-manager:1682): WARNING **: ERROR: Cannot determine if caller is privileged
** (gnome-power-manager:1682): WARNING **: ERROR: Cannot determine if caller is privileged
|
