From fedora-list  Mon Mar 23 06:49:17 2015
From: "T.C. Hollingsworth" <tchollingsworth () gmail ! com>
Date: Mon, 23 Mar 2015 06:49:17 +0000
To: fedora-list
Subject: Re: Polkit General Protection Fault
Message-Id: <CAJVv0OnhQAj-fgGCN-a9EMfMyzURbT=P_QtNjM0k1zV+S4a0_g () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=fedora-list&m=142709337124731
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============3216011490127940124=="

--===============3216011490127940124==
Content-Type: multipart/alternative; boundary=001a11c3ede4a1dda40511ef10dc

--001a11c3ede4a1dda40511ef10dc
Content-Type: text/plain; charset=UTF-8

On Mar 22, 2015 2:54 PM, "Arthur Dent" <misc.lists@blueyonder.co.uk> wrote:
>
> Hello All,
>
> I have, for some time, been getting these messages in my logs:
>
> =============8<=============================================
> WARNING:  General Protection Faults in these executables
>     traps: polkitd :  2 Time(s)

Looks like polkitd crashed twice during your logwatch report interval. If
you have the Automatic Bug Reporting Tool (ABRT) installed it should have
picked these crashes up and allow you to file a bug for them.

I believe polkitd will be automatically started by dbus when it is needed
again so you might not ever notice any ill effects. On the other hand, you
might find that you are unable to perform administrator actions from the
GUI when this happens. It wouldn't affect anything else.

>  **Unmatched Entries**
<snip>

These are all completely harmless. You should configure logwatch to ignore
them and/or file a bug to have them ignored by the default configuration.

-T.C.

--001a11c3ede4a1dda40511ef10dc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">On Mar 22, 2015 2:54 PM, &quot;Arthur Dent&quot; &lt;<a href=
=3D"mailto:misc.lists@blueyonder.co.uk">misc.lists@blueyonder.co.uk</a>&gt;=
 wrote:<br>
&gt;<br>
&gt; Hello All,<br>
&gt;<br>
&gt; I have, for some time, been getting these messages in my logs:<br>
&gt;<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D8&lt;=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt; WARNING:=C2=A0 General Protection Faults in these executables<br>
&gt; =C2=A0 =C2=A0 traps: polkitd :=C2=A0 2 Time(s)</p>
<p dir=3D"ltr">Looks like polkitd crashed twice during your logwatch report=
 interval. If you have the Automatic Bug Reporting Tool (ABRT) installed it=
 should have picked these crashes up and allow you to file a bug for them.<=
/p>
<p dir=3D"ltr">I believe polkitd will be automatically started by dbus when=
 it is needed again so you might not ever notice any ill effects. On the ot=
her hand, you might find that you are unable to perform administrator actio=
ns from the GUI when this happens. It wouldn&#39;t affect anything else.</p=
>
<p dir=3D"ltr">&gt; =C2=A0**Unmatched Entries**<br>
&lt;snip&gt;</p>
<p dir=3D"ltr">These are all completely harmless. You should configure logw=
atch to ignore them and/or file a bug to have them ignored by the default c=
onfiguration.</p>
<p dir=3D"ltr">-T.C.</p>

--001a11c3ede4a1dda40511ef10dc--

--===============3216011490127940124==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCnVzZXJzIG1haWxpbmcgbGlzdAp1c2Vyc0BsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1
bnN1YnNjcmliZSBvciBjaGFuZ2Ugc3Vic2NyaXB0aW9uIG9wdGlvbnM6Cmh0dHBzOi8vYWRtaW4u
ZmVkb3JhcHJvamVjdC5vcmcvbWFpbG1hbi9saXN0aW5mby91c2VycwpGZWRvcmEgQ29kZSBvZiBD
b25kdWN0OiBodHRwOi8vZmVkb3JhcHJvamVjdC5vcmcvY29kZS1vZi1jb25kdWN0Ckd1aWRlbGlu
ZXM6IGh0dHA6Ly9mZWRvcmFwcm9qZWN0Lm9yZy93aWtpL01haWxpbmdfbGlzdF9ndWlkZWxpbmVz
CkhhdmUgYSBxdWVzdGlvbj8gQXNrIGF3YXk6IGh0dHA6Ly9hc2suZmVkb3JhcHJvamVjdC5vcmcK

--===============3216011490127940124==--