From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Cc: Samuli Suominen <ssuominen@gentoo.org>
Subject: Re: [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed
Date: Thu, 16 Jan 2014 11:45:58 +0100 [thread overview]
Message-ID: <1389869158.3913.0@numa-i.igpm.rwth-aachen.de> (raw)
In-Reply-To: <20140116103645.3cef6d4e@hactar.digimed.co.uk> (from neil@digimed.co.uk on Thu Jan 16 11:36:45 2014)
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
next prev parent reply other threads:[~2014-01-16 10:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 11:21 [gentoo-user] KDE slow / console-kit-daemon POLKIT_IS_AUTHORITY failed Helmut Jarausch
2014-01-15 11:37 ` Neil Bothwick
2014-01-15 11:54 ` Helmut Jarausch
2014-01-15 13:37 ` Neil Bothwick
2014-01-16 10:36 ` Neil Bothwick
2014-01-16 10:45 ` Helmut Jarausch [this message]
2014-01-15 14:17 ` Peter Humphrey
2014-01-15 14:29 ` Neil Bothwick
2014-01-15 16:08 ` Peter Humphrey
2014-01-16 0:12 ` Walter Dnes
2014-01-16 0:31 ` Peter Humphrey
2014-01-16 1:14 ` Peter Humphrey
2014-01-16 0:32 ` [gentoo-user] " walt
2014-01-16 9:23 ` Neil Bothwick
2014-01-16 16:19 ` Canek Peláez Valdés
2014-01-16 17:39 ` Neil Bothwick
2014-01-17 4:56 ` Samuli Suominen
2014-01-17 11:11 ` Neil Bothwick
2014-01-17 13:27 ` Neil Bothwick
2014-01-18 23:45 ` Mick
2014-01-19 21:31 ` Neil Bothwick
2014-01-20 16:30 ` Samuli Suominen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1389869158.3913.0@numa-i.igpm.rwth-aachen.de \
--to=jarausch@igpm.rwth-aachen.de \
--cc=gentoo-user@lists.gentoo.org \
--cc=ssuominen@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox