Bug 1520147
| Summary: | bluetooth gives error on bootup; does not work properly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Duchek <johnduchek> |
| Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | dwalsh, jan.public, johnduchek, lvrabec, mgrepl, plautrba, pmoore, ppisar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | selinux-policy-3.13.1-283.26.fc27 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-27 17:22:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1492482 | ||
Hi, Could you reproduce the issue and attach output of: #ausearch -m AVC,USER_AVC -ts today Thanks, Lukas. I am sorry. I sent this on the 7th, but it apparently did not get here. Here is that email.
I had disconnected the bluetooth dongle. Took me a bit to find it. Once I plugged it in, (it is a usb3.0 btdongle) I immediately got the error on bootup. I ran your command and the result is attached.
Thanks,
John
On 01/04/2018 08:56 AM, bugzilla wrote:
> ausearch -m AVC,USER_AVC -ts today
--
John Duchek
ausearch.txt
----
time->Sun Jan 7 07:56:36 2018
type=USER_AVC msg=audit(1515333396.772:224): pid=790 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_call interface=org.freedesktop.DBus.Properties member=GetAll dest=:1.7 spid=1851 tpid=894 scontext=system_u:system_r:blueman_t:s0 tcontext=system_u:system_r:policykit_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
----
time->Sun Jan 7 07:56:36 2018
type=USER_AVC msg=audit(1515333396.816:226): pid=790 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_call interface=org.freedesktop.PolicyKit1.Authority member=CheckAuthorization dest=:1.7 spid=1851 tpid=894 scontext=system_u:system_r:blueman_t:s0 tcontext=system_u:system_r:policykit_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
----
time->Sun Jan 7 07:56:37 2018
type=USER_AVC msg=audit(1515333397.867:228): pid=790 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_call interface=org.freedesktop.PolicyKit1.Authority member=CheckAuthorization dest=:1.7 spid=1851 tpid=894 scontext=system_u:system_r:blueman_t:s0 tcontext=system_u:system_r:policykit_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
selinux-policy-3.13.1-283.26.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-a9711c96b2 selinux-policy-3.13.1-283.26.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a9711c96b2 selinux-policy-3.13.1-283.26.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: When Fedora 27 boots up bluetooth devices do not work properly Version-Release number of selected component (if applicable): unknown How reproducible: Every bootup. Steps to Reproduce: 1.boot up 2.read error message 3. Actual results: When booting up this error appears: "you might not be able to connect to the bluetooth network via this machine. Exception g-io-error-quark: GDBus.Error:org.freedesktop.DBus.Python.GLib.Error: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/dbus/service.py", line 707, in _message_cb retval = candidate_method(self, *args, **keywords) File "/usr/lib/python3.6/site-packages/blueman/main/DbusService.py", line 38, in wrapper return method(*args[1:], **kwargs) File "/usr/lib/python3.6/site-packages/blueman/plugins/mechanism/Network.py", line 56, in ReloadNetwork self.confirm_authorization(caller, "org.blueman.network.setup") File "/usr/libexec/blueman-mechanism", line 166, in confirm_authorization action_id, {}, 1, "") File "/usr/lib64/python3.6/site-packages/gi/overrides/Gio.py", line 191, in __call__ None) GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender=":1.48" (uid=0 pid=1802 comm="python3 /usr/libexec/blueman-mechanism " label="system_u:system_r:blueman_t:s0") interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" error name="(unset)" requested_reply="0" destination=":1.8" (uid=995 pid=963 comm="/usr/lib/polkit-1/polkitd --no-debug " label="system_u:system_r:policykit_t:s0") (9) (36) If I run dmesg | grep bluetooth I get [ 34.037995] SELinux: Class bluetooth_socket not defined in policy. If I get bluetooth running at all, playing music, it skips often and is unlistenable. It skips especially badly if running another application. Expected results: Error message goes away and bluetooth work properly. Additional info: None