Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1559341 - SELinux blocks bluetooth from working
Summary: SELinux blocks bluetooth from working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F28BetaFreezeException F28FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2018-03-22 11:01 UTC by Jiri Eischmann
Modified: 2018-03-26 22:31 UTC (History)
11 users (show)

Fixed In Version: selinux-policy-3.14.1-17.fc28 selinux-policy-3.14.1-18.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-26 22:31:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jiri Eischmann 2018-03-22 11:01:17 UTC 
The current SELinux policy blocks the bluetooth socket and makes bluetooth work very unreliable or not at all.
I either can't connect devices at all or I can, but they disconnect very shortly after that and bluetooth becomes unavailable.
I could reproduce the issue on various computers with F28.

I debugged the issue with the SELinux policy maintainer and it should be fixed in the build in Koji: https://koji.fedoraproject.org/koji/buildinfo?buildID=1061018

I'm filing this bug to make sure that the update lands in Fedora 28 before the final release because I think it's severe enough to qualify for a blocker.
Comment 1 Fedora Blocker Bugs Application 2018-03-22 11:04:56 UTC 
Proposed as a Blocker for 28-final by Fedora user eischmann using the blocker tracking app because:

 This makes Bluetooth not to work which means a whole settings module in gnome-control-center doesn't work which I think doesn't meet the "Default application functionality" criteria.
Comment 2 František Zatloukal 2018-03-22 18:50:48 UTC 
Discussed during blocker review [1]:

AcceptedFreezeException (Beta) - this is a significant functionality issue that will affect lives etc., would be good to fix it for the compose

[1] https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-03-22/
Comment 3 Fedora Update System 2018-03-25 13:12:03 UTC 
selinux-policy-3.14.1-17.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b8cb71b345
Comment 4 Fedora Update System 2018-03-25 20:32:50 UTC 
selinux-policy-3.14.1-17.fc28 has been pushed to the Fedora 28 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-b8cb71b345
Comment 5 Geoffrey Marr 2018-03-26 19:09:34 UTC 
Discussed during the 2018-03-26 blocker review meeting: [1]

The decision to delay the classification of this bug as a blocker was made as it's not really clear whether this should be considered a blocker or not, but as the fix has already been accepted as a Beta FE, we will wait for the fix to be applied and this bug should no longer be a problem.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-03-26/f28-blocker-review.2018-03-26-16.01.txt
Comment 6 Fedora Update System 2018-03-26 21:51:19 UTC 
selinux-policy-3.14.1-18.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7821b2e7c4
Comment 7 Fedora Update System 2018-03-26 22:31:41 UTC 
selinux-policy-3.14.1-18.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.