| 1 |
On 11/07/13 12:32, Helmut Jarausch wrote: |
| 2 |
> On 07/11/2013 10:31:04 AM, Neil Bothwick wrote: |
| 3 |
>> On Thu, 11 Jul 2013 08:36:29 +0200, Helmut Jarausch wrote: |
| 4 |
>> |
| 5 |
>> > Error getting authority: Error initializing authority: Error calling |
| 6 |
>> > StartServiceByName for org.freedesktop.PolicyKit1: |
| 7 |
>> > GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to |
| 8 |
>> > execute program /usr/libexec/dbus-daemon-launch-helper: Success |
| 9 |
>> |
| 10 |
>> I get this on my desktop but not my laptop, yet I have been unable to |
| 11 |
>> find the difference that accounts for it. In the end I gave up and made |
| 12 |
>> /usr/libexec/dbus-daemon-launch-helper world-executable :( |
| 13 |
>> |
| 14 |
>> |
| 15 |
> |
| 16 |
> Thanks, that fixed it. It looks as if a process switches its UID to a |
| 17 |
> non-root UID. |
| 18 |
> Perhaps the ebuild should be fixed to install sys-apps/dbus with these |
| 19 |
> permissions. |
| 20 |
|
| 21 |
Making it world executable is same as giving root to every user on your |
| 22 |
system -- as it makes it possible to escalate to user 'root' or at least |
| 23 |
group 'messagebus' |
| 24 |
|
| 25 |
So... Instead, the problem is often solved by simple re-emerge: |
| 26 |
|
| 27 |
# emerge -1 glib dbus dbus-glib |
| 28 |
|
| 29 |
Often caused by glib's upgrade (or downgrade) or dbus's upgrade (or |
| 30 |
downgrade) where dbus-glib hasn't been rebuilt with it |
| 31 |
|
| 32 |
- Samuli |
Archives