[gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Helmut Jarausch]

Hi,

hopefully someone can help.

I have a system where KDE 4.12.0 / 4.11.5 is very slow.

The log contains many message like

dbus[1366]: [system] Activated service 'org.freedesktop.login1' failed:
   Failed to execute program /usr/libexec/dbus-daemon-launch-helper:  
Success

console-kit-daemon[1387]: CRITICAL:  
polkit_authority_check_authorization:
   assertion 'POLKIT_IS_AUTHORITY (authority)' failed

I have re-emerged sys-apps/dbus dev-libs/dbus-glib  
sys-auth/polkit-kde-agent
as recommended elsewhere but it didn't help.

Does anybody know how to fix this?

Many thanks for hint,
Helmut

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

On Wed, 15 Jan 2014 12:21:37 +0100, Helmut Jarausch wrote:

> The log contains many message like
> 
> dbus[1366]: [system] Activated service 'org.freedesktop.login1' failed:
>    Failed to execute program /usr/libexec/dbus-daemon-launch-helper:  
> Success

I get this on my desktop but not my laptop. I have tried for ages to find
out why it only fails on the desktop and gave up. Now I just "chmod
+x /usr/libexec/dbus-daemon-launch-helper" and it goes away, until the
next update.


-- 
Neil Bothwick

- We are but packets in the internet of Life-

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Helmut Jarausch]

On 01/15/2014 12:37:44 PM, Neil Bothwick wrote:
> On Wed, 15 Jan 2014 12:21:37 +0100, Helmut Jarausch wrote:
> 
> > The log contains many message like
> >
> > dbus[1366]: [system] Activated service 'org.freedesktop.login1'  
> failed:
> >    Failed to execute program /usr/libexec/dbus-daemon-launch-helper:
> > Success
> 
> I get this on my desktop but not my laptop. I have tried for ages to  
> find
> out why it only fails on the desktop and gave up. Now I just "chmod
> +x /usr/libexec/dbus-daemon-launch-helper" and it goes away, until the
> next update.

Many thanks Neil!

On Jul 02, 2012,  Samuel Suominen wrote

Never do that, unless you want everyone on your system to be allowed to  
gain root. As in, that is same as intentionally inserting a  
vulnerability to your own machine.

The solution is to recompile pkgs like dev-libs/dbus-glib after  
dev-libs/glib upgrade (as noted by elog in the end of glib emerge)
Propably 'emerge -e sys-apps/dbus dev-libs/dbus-glib' will do the trick  
if nothing else does

Only, this emerge likes to re-emerge several hundreds of packages.

Any comments?
Helmut

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

On Wed, 15 Jan 2014 12:54:57 +0100, Helmut Jarausch wrote:

> > I get this on my desktop but not my laptop. I have tried for ages to  
> > find
> > out why it only fails on the desktop and gave up. Now I just "chmod
> > +x /usr/libexec/dbus-daemon-launch-helper" and it goes away, until the
> > next update.  
> 
> Many thanks Neil!
> 
> On Jul 02, 2012,  Samuel Suominen wrote
> 
> Never do that, unless you want everyone on your system to be allowed
> to gain root. As in, that is same as intentionally inserting a  
> vulnerability to your own machine.
> 
> The solution is to recompile pkgs like dev-libs/dbus-glib after  
> dev-libs/glib upgrade (as noted by elog in the end of glib emerge)
> Propably 'emerge -e sys-apps/dbus dev-libs/dbus-glib' will do the
> trick if nothing else does

I tried all that and it made no difference. Bear in mind this machine has
been affected like this for more than two years, there is nothing that
has not been re-emerged in that time yet the issue persists.


-- 
Neil Bothwick

Too many clicks spoil the browse.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Wed, 15 Jan 2014 13:37:39 +0000, Neil Bothwick wrote:

> > The solution is to recompile pkgs like dev-libs/dbus-glib after  
> > dev-libs/glib upgrade (as noted by elog in the end of glib emerge)
> > Propably 'emerge -e sys-apps/dbus dev-libs/dbus-glib' will do the
> > trick if nothing else does  
> 
> I tried all that and it made no difference. Bear in mind this machine
> has been affected like this for more than two years, there is nothing
> that has not been re-emerged in that time yet the issue persists.

For the hell of it, I ran 'emerge -e sys-apps/dbus dev-libs/dbus-glib'
again. six hours and a reboot later and nothing has changed :(


-- 
Neil Bothwick

TEXAS VIRUS: Makes sure that it's bigger than any other file.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Helmut Jarausch]

On 01/16/2014 11:36:45 AM, Neil Bothwick wrote:
> On Wed, 15 Jan 2014 13:37:39 +0000, Neil Bothwick wrote:
> 
> > > The solution is to recompile pkgs like dev-libs/dbus-glib after
> > > dev-libs/glib upgrade (as noted by elog in the end of glib emerge)
> > > Propably 'emerge -e sys-apps/dbus dev-libs/dbus-glib' will do the
> > > trick if nothing else does
> >
> > I tried all that and it made no difference. Bear in mind this  
> machine
> > has been affected like this for more than two years, there is  
> nothing
> > that has not been re-emerged in that time yet the issue persists.
> 
> For the hell of it, I ran 'emerge -e sys-apps/dbus dev-libs/dbus-glib'
> again. six hours and a reboot later and nothing has changed :(

Many thanks, you did it for me - I was afraid of that outcome
Helmut


On Wed, 15 Jan 2014 12:21:37 +0100, Helmut Jarausch wrote:
The log contains many message like

dbus[1366]: [system] Activated service 'org.freedesktop.login1' failed:
   Failed to execute program /usr/libexec/dbus-daemon-launch-helper:  
Success

console-kit-daemon[1387]: CRITICAL:  
polkit_authority_check_authorization:
   assertion 'POLKIT_IS_AUTHORITY (authority)' failed

I have re-emerged sys-apps/dbus dev-libs/dbus-glib  
sys-auth/polkit-kde-agent
as recommended elsewhere but it didn't help.

On 01/15/2014 12:37:44 PM, Neil Bothwick wrote:
I get this on my desktop but not my laptop. I have tried for ages to  
find
> out why it only fails on the desktop and gave up. Now I just "chmod
> +x /usr/libexec/dbus-daemon-launch-helper" and it goes away, until the
> next update.

On Jul 02, 2012,  Samuel Suominen wrote

Never do that, unless you want everyone on your system to be allowed to  
gain root. As in, that is same as intentionally inserting a  
vulnerability to your own machine.

The solution is to recompile pkgs like dev-libs/dbus-glib after  
dev-libs/glib upgrade (as noted by elog in the end of glib emerge)
Propably 'emerge -e sys-apps/dbus dev-libs/dbus-glib' will do the trick  
if nothing else does

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Peter Humphrey]

On Wednesday 15 Jan 2014 11:37:44 Neil Bothwick wrote:
> On Wed, 15 Jan 2014 12:21:37 +0100, Helmut Jarausch wrote:
> > The log contains many message like
> > 
> > dbus[1366]: [system] Activated service 'org.freedesktop.login1' failed:
> >    Failed to execute program /usr/libexec/dbus-daemon-launch-helper:
> > Success
> 
> I get this on my desktop but not my laptop. I have tried for ages to find
> out why it only fails on the desktop and gave up. Now I just "chmod
> +x /usr/libexec/dbus-daemon-launch-helper" and it goes away, until the
> next update.

That's interesting. Now that I look at mine, which doesn't throw those errors, 
I find some unusual permissions:

$ ls -l /usr/libexec/dbus-daemon-launch-helper
-rws--x--- 1 root messagebus 316K Dec  1 17:59 /usr/libexec/dbus-daemon-
launch-helper

Is this the same as what doesn't work for you?

-- 
Regards
Peter

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

On Wed, 15 Jan 2014 14:17:18 +0000, Peter Humphrey wrote:

> > I get this on my desktop but not my laptop. I have tried for ages to
> > find out why it only fails on the desktop and gave up. Now I just
> > "chmod +x /usr/libexec/dbus-daemon-launch-helper" and it goes away,
> > until the next update.  
> 
> That's interesting. Now that I look at mine, which doesn't throw those
> errors, I find some unusual permissions:
> 
> $ ls -l /usr/libexec/dbus-daemon-launch-helper
> -rws--x--- 1 root messagebus 316K Dec  1 17:59 /usr/libexec/dbus-daemon-
> launch-helper
> 
> Is this the same as what doesn't work for you?

It is the same as on both the working laptop and non-working desktop?
Those are the permissions set by the dbus install, but one computer
objects to it. The desktop user is a member of every group that the
laptop user belongs to.

Yes, I know that's bad grammar and a preposition is something you should
never end a sentence with.


-- 
Neil Bothwick

Top Oxymorons Number 38: Government organization

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Peter Humphrey]

On Wednesday 15 Jan 2014 14:29:51 Neil Bothwick wrote:
> On Wed, 15 Jan 2014 14:17:18 +0000, Peter Humphrey wrote:
> > > I get this on my desktop but not my laptop. I have tried for ages to
> > > find out why it only fails on the desktop and gave up. Now I just
> > > "chmod +x /usr/libexec/dbus-daemon-launch-helper" and it goes away,
> > > until the next update.
> > 
> > That's interesting. Now that I look at mine, which doesn't throw those
> > errors, I find some unusual permissions:
> > 
> > $ ls -l /usr/libexec/dbus-daemon-launch-helper
> > -rws--x--- 1 root messagebus 316K Dec  1 17:59 /usr/libexec/dbus-daemon-
> > launch-helper
> > 
> > Is this the same as what doesn't work for you?
> 
> It is the same as on both the working laptop and non-working desktop?
> Those are the permissions set by the dbus install, but one computer
> objects to it. The desktop user is a member of every group that the
> laptop user belongs to.
>
> Yes, I know that's bad grammar and a preposition is something you should
> never end a sentence with.

You pinched my line! I often say that a preposition is a perfectly good word 
to end a sentence with.

-- 
Yours,
Bemused of Tideswell

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Walter Dnes]

On Wed, Jan 15, 2014 at 02:29:51PM +0000, Neil Bothwick wrote

> Yes, I know that's bad grammar and a preposition is something you should
> never end a sentence with.

  That is a rule up with which I will not put. (Sir Winston Churchill)

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Peter Humphrey]

On Wednesday 15 Jan 2014 19:12:16 Walter Dnes wrote:

>   That is a rule up with which I will not put. (Sir Winston Churchill)

IIRC that was a put-down in the House of Commons. I forget who'd been too 
pompous that time, but he got it between the eyes.

-- 
Regards
Peter

Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Peter Humphrey]

On Thursday 16 Jan 2014 00:31:52 I wrote:
> On Wednesday 15 Jan 2014 19:12:16 Walter Dnes wrote:
> >   That is a rule up with which I will not put. (Sir Winston Churchill)
> 
> IIRC that was a put-down in the House of Commons. I forget who'd been too
> pompous that time, but he got it between the eyes.

I was mistaken, according to 
http://www.winstonchurchill.org/learn/speeches/quotations . Always a timely 
reminder of human frailty.

-- 
Regards
Peter

[gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[walt]

On 01/15/2014 03:37 AM, Neil Bothwick wrote:
> On Wed, 15 Jan 2014 12:21:37 +0100, Helmut Jarausch wrote:
> 
>> The log contains many message like
>>
>> dbus[1366]: [system] Activated service 'org.freedesktop.login1' failed:
>>    Failed to execute program /usr/libexec/dbus-daemon-launch-helper:  
>> Success
> 
> I get this on my desktop but not my laptop. I have tried for ages to find
> out why it only fails on the desktop and gave up. Now I just "chmod
> +x /usr/libexec/dbus-daemon-launch-helper" and it goes away, until the
> next update.

Helmut is still using consolekit.  Are you still using consolekit?

I have no idea if consolekit is relevant here, but Canek has been telling
us that consolekit is abandonware and we should stop depending on it.

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

On Wed, 15 Jan 2014 16:32:00 -0800, walt wrote:

> > I get this on my desktop but not my laptop. I have tried for ages to
> > find out why it only fails on the desktop and gave up. Now I just
> > "chmod +x /usr/libexec/dbus-daemon-launch-helper" and it goes away,
> > until the next update.  
> 
> Helmut is still using consolekit.  Are you still using consolekit?

Yes, it's the default for kdm so it is enabled on both computers.

> I have no idea if consolekit is relevant here, but Canek has been
> telling us that consolekit is abandonware and we should stop depending
> on it.

That's part of the drive to put everything in systemd, which I do not use.


-- 
Neil Bothwick

Indecision is the key to flexibility.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Canek Peláez Valdés]

[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]

On Jan 16, 2014 3:23 AM, "Neil Bothwick" <neil@digimed.co.uk> wrote:
>
> On Wed, 15 Jan 2014 16:32:00 -0800, walt wrote:
>
> > > I get this on my desktop but not my laptop. I have tried for ages to
> > > find out why it only fails on the desktop and gave up. Now I just
> > > "chmod +x /usr/libexec/dbus-daemon-launch-helper" and it goes away,
> > > until the next update.
> >
> > Helmut is still using consolekit.  Are you still using consolekit?
>
> Yes, it's the default for kdm so it is enabled on both computers.

I don't think it will be the default for much longer; it's unmaintained
code which sooner or later will start to bitrot. Unless someone steps in
and starts taking care of it.

> > I have no idea if consolekit is relevant here, but Canek has been
> > telling us that consolekit is abandonware and we should stop depending
> > on it.
>
> That's part of the drive to put everything in systemd, which I do not use.

Fact is, nobody is maintaining ck; from its homepage[1]:

"ConsoleKit is currently not actively maintained. The focus has shifted to
the built-in seat/user/session management of Software/systemd called
systemd-logind!"

That message has been there for months; in general ck kinda still works,
although it never really solved the problem of properly tracking user
sessions, which is why everybody involved with it quickly jumped ship to
logind, where the problem is properly solved.

However, as the interfaces in the stack evolves, unmaintained code like ck
will simply stop to work. ConsoleKit uses dbus heavily, and with the
introduction of kdbus[2] and the inevitable changes that will happen to
dbus, combined with nobody taking care of ck, I don't think it will keep
working much longer.

Ubuntu and Debian (now that is seriously discussing which modern init
system to use) have been discussing an alternative, API compatible
implementation of logind, but I don't know if it has got nowhere. I think
that has more future than ck, but again, nobody (AFAIK) has stepped in and
do the heavy coding.

Independently, though, I think is safe to say that ConsoleKit is a dead end.

Regards.

[1] http://www.freedesktop.org/wiki/Software/ConsoleKit/
[2] http://lwn.net/SubscriberLink/580194/a2a05056a657f1bb/

[-- Attachment #2: Type: text/html, Size: 2841 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 2563 bytes --]

On Thu, 16 Jan 2014 10:19:22 -0600, Canek Peláez Valdés wrote:

> > > Helmut is still using consolekit.  Are you still using consolekit?  
> >
> > Yes, it's the default for kdm so it is enabled on both computers.  
> 
> I don't think it will be the default for much longer; it's unmaintained
> code which sooner or later will start to bitrot. Unless someone steps in
> and starts taking care of it.

Quite likely, but for now it is the default and in use on both systems in
question.

> > > I have no idea if consolekit is relevant here, but Canek has been
> > > telling us that consolekit is abandonware and we should stop
> > > depending on it.  
> >
> > That's part of the drive to put everything in systemd, which I do not
> > use.  
> 
> Fact is, nobody is maintaining ck; from its homepage[1]:
> 
> "ConsoleKit is currently not actively maintained. The focus has shifted
> to the built-in seat/user/session management of Software/systemd called
> systemd-logind!"

That's what I was paraphrasing above. I checked the latest status on that
page before replying.

> That message has been there for months; in general ck kinda still works,
> although it never really solved the problem of properly tracking user
> sessions, which is why everybody involved with it quickly jumped ship to
> logind, where the problem is properly solved.

The issue for many is that logind is so closely tied to systemd.

> However, as the interfaces in the stack evolves, unmaintained code like
> ck will simply stop to work. ConsoleKit uses dbus heavily, and with the
> introduction of kdbus[2] and the inevitable changes that will happen to
> dbus, combined with nobody taking care of ck, I don't think it will keep
> working much longer.

That's a reasonable prediction.
> 
> Ubuntu and Debian (now that is seriously discussing which modern init
> system to use) have been discussing an alternative, API compatible
> implementation of logind, but I don't know if it has got nowhere. I
> think that has more future than ck, but again, nobody (AFAIK) has
> stepped in and do the heavy coding.

Leaving aside my concerns about systemd, I am not happy with the "all
eggs in one basket" direction things seem to be taking. Whatever happened
to tolls doing one job and doing it well?

> Independently, though, I think is safe to say that ConsoleKit is a dead
> end.

In the future, most probably. but right now it is the preferred option
for KDM.


-- 
Neil Bothwick

I spilled Spot remover on my dog. Now he's gone.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Samuli Suominen]

On 16/01/14 19:39, Neil Bothwick wrote:
> On Thu, 16 Jan 2014 10:19:22 -0600, Canek Peláez Valdés wrote:
>
>>>> Helmut is still using consolekit.  Are you still using consolekit?  
>>> Yes, it's the default for kdm so it is enabled on both computers.  
>> I don't think it will be the default for much longer; it's unmaintained
>> code which sooner or later will start to bitrot. Unless someone steps in
>> and starts taking care of it.
> Quite likely, but for now it is the default and in use on both systems in
> question.
>
>>>> I have no idea if consolekit is relevant here, but Canek has been
>>>> telling us that consolekit is abandonware and we should stop
>>>> depending on it.  
>>> That's part of the drive to put everything in systemd, which I do not
>>> use.  
>> Fact is, nobody is maintaining ck; from its homepage[1]:
>>
>> "ConsoleKit is currently not actively maintained. The focus has shifted
>> to the built-in seat/user/session management of Software/systemd called
>> systemd-logind!"
> That's what I was paraphrasing above. I checked the latest status on that
> page before replying.
>
>> That message has been there for months; in general ck kinda still works,
>> although it never really solved the problem of properly tracking user
>> sessions, which is why everybody involved with it quickly jumped ship to
>> logind, where the problem is properly solved.
> The issue for many is that logind is so closely tied to systemd.
>
>> However, as the interfaces in the stack evolves, unmaintained code like
>> ck will simply stop to work. ConsoleKit uses dbus heavily, and with the
>> introduction of kdbus[2] and the inevitable changes that will happen to
>> dbus, combined with nobody taking care of ck, I don't think it will keep
>> working much longer.
> That's a reasonable prediction.
>> Ubuntu and Debian (now that is seriously discussing which modern init
>> system to use) have been discussing an alternative, API compatible
>> implementation of logind, but I don't know if it has got nowhere. I
>> think that has more future than ck, but again, nobody (AFAIK) has
>> stepped in and do the heavy coding.
> Leaving aside my concerns about systemd, I am not happy with the "all
> eggs in one basket" direction things seem to be taking. Whatever happened
> to tolls doing one job and doing it well?
>
>> Independently, though, I think is safe to say that ConsoleKit is a dead
>> end.
> In the future, most probably. but right now it is the preferred option
> for KDM.
>
>

Right, only GDM (the display manager for GNOME) has dropped ConsoleKit
support so far, that I know, in versions 3.8 and later
So other than GNOME, ConsoleKit is still a go -- thus, compatible with
OpenRC based system

For KDE it might be something else than dbus-glib that needs a
recompile, I'd imagine something like kdelibs or polkit-kde-agent, or both
It could be something else too, but setting the suid bit on
dbus-daemon-launch-helper is stupidest idea ever, that *really* allows
anyone to gain root
However if you run a machine with single user and no open ports on the
machine whatsoever, the attack vector is propably very small, but I still
wouldn't do it

- Samuli

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]

On Fri, 17 Jan 2014 06:56:20 +0200, Samuli Suominen wrote:

> Right, only GDM (the display manager for GNOME) has dropped ConsoleKit
> support so far, that I know, in versions 3.8 and later
> So other than GNOME, ConsoleKit is still a go -- thus, compatible with
> OpenRC based system

I tried USE="-consolekit" but it does not help.
 
> For KDE it might be something else than dbus-glib that needs a
> recompile, I'd imagine something like kdelibs or polkit-kde-agent, or
> both It could be something else too,

This problem has been there for a couple of years, it's reasonable to
assume that all KDE components have been recompiled several times in that
period. In fact, both of those were rebuilt by emerge -e dbus dbus-glib.

> but setting the suid bit on
> dbus-daemon-launch-helper is stupidest idea ever, that *really* allows
> anyone to gain root

Just to be clear, the SUID bit is set by default, I set the other execute
bit (o+x). The file already has group execute permissions, but adding my
user to the messagebus group makes no difference

> However if you run a machine with single user and no open ports on the
> machine whatsoever, the attack vector is propably very small, but I
> still wouldn't do it

The alternative is to stop using KDE, since none of the proposed
solutions, nor anything else I've tried, make any difference.

Edit: Dropping KDE may not make much difference, I still get these
messages when booting without X.


-- 
Neil Bothwick

Why is there an expiration date on sour cream?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Fri, 17 Jan 2014 11:11:06 +0000, Neil Bothwick wrote:

> Edit: Dropping KDE may not make much difference, I still get these
> messages when booting without X.

This got me wondering. If I get the messages when booting to a console
login prompt, it can't be anything to do with X or my user. The file is
group owned by messagebus and checking /etc/passwd and /etc/group
revealed inconsistencies. So I removed the messagebus entries from both
file and ran "emerge -1 --noconfmem dbus dbus-glib" and rebooted.

So far, no more of those messages. Thanks to Helmut for raising the topic
again and thanks to Samuli for giving me the kick up the jacksie I needed
to search for a proper solution to replace the ugly hack.

I'm hours behind in my work now, but I am happy(er) :)


-- 
Neil Bothwick

C:\DOS\SYSTEM\OS2\UTILITIES\DOCS\HELP\WHERE\THE\F$#%\AM\I???

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1258 bytes --]

On Friday 17 Jan 2014 13:27:36 Neil Bothwick wrote:
> On Fri, 17 Jan 2014 11:11:06 +0000, Neil Bothwick wrote:
> > Edit: Dropping KDE may not make much difference, I still get these
> > messages when booting without X.
> 
> This got me wondering. If I get the messages when booting to a console
> login prompt, it can't be anything to do with X or my user. The file is
> group owned by messagebus and checking /etc/passwd and /etc/group
> revealed inconsistencies. So I removed the messagebus entries from both
> file and ran "emerge -1 --noconfmem dbus dbus-glib" and rebooted.
> 
> So far, no more of those messages. Thanks to Helmut for raising the topic
> again and thanks to Samuli for giving me the kick up the jacksie I needed
> to search for a proper solution to replace the ugly hack.
> 
> I'm hours behind in my work now, but I am happy(er) :)

This thread confused me.  I have this in my system and I have not changed the 
permissions from when it was installed:

ls -la /usr/libexec/dbus-daemon-launch-helper
-rws--x--- 1 root messagebus 322984 Jun 22  2013 /usr/libexec/dbus-daemon-
launch-helper

Is the suid bit dangerous and if so what is the alternative?  Should there be 
a bug filed on it?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On Sat, 18 Jan 2014 23:45:00 +0000, Mick wrote:

> This thread confused me.  I have this in my system and I have not
> changed the permissions from when it was installed:
> 
> ls -la /usr/libexec/dbus-daemon-launch-helper
> -rws--x--- 1 root messagebus 322984 Jun 22
> 2013 /usr/libexec/dbus-daemon- launch-helper
> 
> Is the suid bit dangerous and if so what is the alternative?  Should
> there be a bug filed on it?

I think what Samuli was trying to say was that the suid bit is dangerous
if you give global execute permissions to the file, because then anyone
can run it as root. The default of rwx--x--- if safe because only root or
a member of the messagebus group can execute it.

My problem was that the messagebus user was not a member of the
messagebus group thanks to a mismatch of IDs in /etc/{passwd,group} - I
don't know whether this is also the cause of the error messages on
Helmut's system.


-- 
Neil Bothwick

WinErr 042: Virus error - A virus has been activated in a dos-box. The
virus, however, requires Windows. All tasks will automatically be closed
            and the virus will be activated again.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed

[Samuli Suominen]

On 19/01/14 23:31, Neil Bothwick wrote:
> On Sat, 18 Jan 2014 23:45:00 +0000, Mick wrote:
>
>> This thread confused me.  I have this in my system and I have not
>> changed the permissions from when it was installed:
>>
>> ls -la /usr/libexec/dbus-daemon-launch-helper
>> -rws--x--- 1 root messagebus 322984 Jun 22
>> 2013 /usr/libexec/dbus-daemon- launch-helper
>>
>> Is the suid bit dangerous and if so what is the alternative?  Should
>> there be a bug filed on it?
> I think what Samuli was trying to say was that the suid bit is dangerous
> if you give global execute permissions to the file, because then anyone

exactly.   my bad with the wording earlier.