Hi,
(too) often I get dbus errors, especial when running an application as
root
e.g.
Error getting authority: Error initializing authority: Error calling
StartServiceByName for org.freedesktop.PolicyKit1:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to
execute
On Thu, 11 Jul 2013 08:36:29 +0200, Helmut Jarausch wrote:
Error getting authority: Error initializing authority: Error calling
StartServiceByName for org.freedesktop.PolicyKit1:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to
execute program
On 07/11/2013 10:31:04 AM, Neil Bothwick wrote:
On Thu, 11 Jul 2013 08:36:29 +0200, Helmut Jarausch wrote:
Error getting authority: Error initializing authority: Error calling
StartServiceByName for org.freedesktop.PolicyKit1:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed
On 11/07/13 12:32, Helmut Jarausch wrote:
On 07/11/2013 10:31:04 AM, Neil Bothwick wrote:
On Thu, 11 Jul 2013 08:36:29 +0200, Helmut Jarausch wrote:
Error getting authority: Error initializing authority: Error calling
StartServiceByName for org.freedesktop.PolicyKit1:
On 07/11/2013 11:39:21 AM, Samuli Suominen wrote:
Making it world executable is same as giving root to every user on
your system -- as it makes it possible to escalate to user 'root' or
at least group 'messagebus'
So... Instead, the problem is often solved by simple re-emerge:
# emerge -1
On Thu, 11 Jul 2013 12:39:21 +0300, Samuli Suominen wrote:
I get this on my desktop but not my laptop, yet I have been unable to
find the difference that accounts for it. In the end I gave up and
made /usr/libexec/dbus-daemon-launch-helper world-executable :(
Making it world executable is
On 11 July 2013, at 13:27, Neil Bothwick wrote:
...
So... Instead, the problem is often solved by simple re-emerge:
# emerge -1 glib dbus dbus-glib
Often, maybe - always, definitely not. This machine has suffered from
that issue for some time and none of the suggested solutions,
7 matches
Mail list logo