Anyone see this ? (f13 fully updated) - when this happens i cannot connect my BT mouse - i need to resync the mouse and it works till mouse idles and then it stops again.
PS - i am (and have been for a week or so) running Kyles kernel with the tty sched changes (v2 or something) but this problem arose today.
Summary:
SELinux is preventing /usr/sbin/bluetoothd "getopt" access .
Detailed Description:
SELinux denied access requested by bluetoothd. It is not expected that this access is required by bluetoothd and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access.
Additional Information:
Source Context system_u:system_r:bluetooth_t:s0-s0:c0.c1023 Target Context system_u:object_r:unlabeled_t:s0 Target Objects None [ socket ] Source bluetoothd Source Path /usr/sbin/bluetoothd Port <Unknown> Source RPM Packages bluez-4.64-1.fc13 Target RPM Packages Policy RPM selinux-policy-3.7.19-73.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Platform Linux hx.sapience.com 2.6.36.1-10.fc15.x86_64 #1 SMP Mon Nov 29 14:41:22 UTC 2010 x86_64 x86_64 Alert Count 12 First Seen Mon Nov 29 19:50:26 2010 Last Seen Mon Nov 29 21:19:22 2010 Local ID 31836b48-2806-449c-a54f-220757a9497e Line Numbers
node=hx.prv.sapience.com type=AVC msg=audit(1291083562.766:32696): avc: denied { getopt } for pid=1687 comm="bluetoothd" scontext=system_u:system_r:bluetooth_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=socket
node=hx.prv.sapience.com type=SYSCALL msg=audit(1291083562.766:32696): arch=c000003e syscall=55 success=no exit=-13 a0=1a a1=6 a2=1 a3=7ffff4cc07d0 items=0 ppid=1 pid=1687 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="bluetoothd" exe="/usr/sbin/bluetoothd" subj=system_u:system_r:bluetooth_t:s0-s0:c0.c1023 key=(null)
On 11/29/2010 09:33 PM, Genes MailLists wrote:
Anyone see this ? (f13 fully updated) - when this happens i cannot connect my BT mouse - i need to resync the mouse and it works till mouse idles and then it stops again.
PS - i am (and have been for a week or so) running Kyles kernel with the tty sched changes (v2 or something) but this problem arose today.
2.6.36.1-10.fc15.x86_64 #1 SMP Mon Nov 29
14:41:22
Doh - this is the f15 koji kernel - that must be the problem - I accidently booted it this evening ..
sorry about that - since I am running it on f13 its not clear that issue is of use to you guys as an issue.
gene/
On 11/29/2010 11:19 PM, Genes MailLists wrote:
On 11/29/2010 09:33 PM, Genes MailLists wrote:
In case this is of use - /var/log/messages has this CAP_ issue which is the source of the problem - this does not seem f13 specific.
Nov 29 19:51:02 lap1 setroubleshoot: SELinux is preventing /usr/sbin/bluetoothd "getopt" access . For complete SELinux messages. run sealert -l 31836b48-2806-449c-a54f-220757a9497e Nov 29 19:51:35 lap1 bluetoothd[1687]: getsockopt(L2CAP_OPTIONS): Permission denied (13) Nov 29 19:51:35 lap1 bluetoothd[1687]: getsockopt(L2CAP_OPTIONS): Permission denied (13)
gene/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/29/2010 11:27 PM, Genes MailLists wrote:
On 11/29/2010 11:19 PM, Genes MailLists wrote:
On 11/29/2010 09:33 PM, Genes MailLists wrote:
In case this is of use - /var/log/messages has this CAP_ issue which is the source of the problem - this does not seem f13 specific.
Nov 29 19:51:02 lap1 setroubleshoot: SELinux is preventing /usr/sbin/bluetoothd "getopt" access . For complete SELinux messages. run sealert -l 31836b48-2806-449c-a54f-220757a9497e Nov 29 19:51:35 lap1 bluetoothd[1687]: getsockopt(L2CAP_OPTIONS): Permission denied (13) Nov 29 19:51:35 lap1 bluetoothd[1687]: getsockopt(L2CAP_OPTIONS): Permission denied (13)
gene/
selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
https://bugzilla.redhat.com/show_bug.cgi?id=633424
It is a known issue. Could you add your new info to the bug report.
On 11/30/2010 09:20 AM, Daniel J Walsh wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=633424
It is a known issue. Could you add your new info to the bug report.
done.
g/
selinux@lists.fedoraproject.org