Description of problem: SELinux is preventing (uetoothd) from 'mounton' accesses on the directory /var/lib/bluetooth. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that (uetoothd) should be allowed mounton access on the bluetooth directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c '(uetoothd)' --raw | audit2allow -M my-uetoothd # semodule -X 300 -i my-uetoothd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:bluetooth_var_lib_t:s0 Target Objects /var/lib/bluetooth [ dir ] Source (uetoothd) Source Path (uetoothd) Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages bluez-5.48-3.fc27.x86_64 Policy RPM selinux-policy-3.13.1-283.24.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.15.3-300.fc27.x86_64 #1 SMP Tue Feb 13 17:02:01 UTC 2018 x86_64 x86_64 Alert Count 1 First Seen 2018-02-21 21:16:04 AEDT Last Seen 2018-02-21 21:16:04 AEDT Local ID f8fbf7d4-9ff9-429f-b16d-c3d73cfc3214 Raw Audit Messages type=AVC msg=audit(1519208164.680:109): avc: denied { mounton } for pid=22624 comm="(uetoothd)" path="/var/lib/bluetooth" dev="dm-0" ino=540485187 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:bluetooth_var_lib_t:s0 tclass=dir permissive=0 Hash: (uetoothd),init_t,bluetooth_var_lib_t,dir,mounton Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport Potential duplicate: bug 1502141
Description of problem: After the installation of Wireshark, still in the same session, only remote interfaces were recognized and therefore available in Wireshark, therefore Ethernet and Bluetooth interfaces were not listed. After logout and login back, the alert occured, and Ethernet and Bluetooth interfaces were at last listed. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: Alert occured while Wireshark was launched (Ethernet interface selected). Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: Wireshark is running and reading capture from file (.pcapng). No capture are currently operated. Computer is using only wired connection and bluetooth is disactivated. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: just restart Fedora27 Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: System was reboot. Wireshark was launched. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: No application was launched. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: The alert is renewed, just after each current one has been deleted. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: On system start. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: Bluetooth problem on start Fedora 27 Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.4-300.fc27.x86_64 type: libreport
Description of problem: After using JBL Bluetooth speakers, I'm frequently getting this SELinux warning. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Description of problem: Aparecio el error de la nada, ababa de instalar Dolphin Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.9-300.fc27.x86_64 type: libreport
Description of problem: i dont know Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.3-300.fc27.x86_64 type: libreport
Created attachment 1400433 [details] Wireshark v2.4.4 – Bluetooth interface option unchecked After investigation I noticed on my system, which may have specific a configuration, that issue appeared to be tied to the option in Wireshark v2.4.4 that allows for activation of the capture on the Bluetooth interface. Once that option was unchecked, the present issue no longer occurred. Once option was checked back to its default, issue occurred as it did before with that same configuration.
Description of problem: Restarted the bluetooth service Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.14.16-300.fc27.x86_64 type: libreport
Description of problem: Issue reoccured. despite Bluetooth interface had been since previous message disabled in Wireshark. Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.4-300.fc27.x86_64 type: libreport
Description of problem: At reboot, got this pop-up Version-Release number of selected component: selinux-policy-3.13.1-283.24.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.4-300.fc27.x86_64 type: libreport
Description of problem: This happened at startup. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.4-300.fc27.x86_64 type: libreport
Description of problem: Problem occured after launching GNOME. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
*** Bug 1551310 has been marked as a duplicate of this bug. ***
*** Bug 1551404 has been marked as a duplicate of this bug. ***
Description of problem: No idea, sorry. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: on login Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
*** Bug 1551987 has been marked as a duplicate of this bug. ***
Description of problem: This happens on a default install on a Dell Latitude E7440 after logging in. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: The SELinux Alert appeared after booting up. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
*** Bug 1552435 has been marked as a duplicate of this bug. ***
Get this too occasionally out of nowhere on a Thinkpad X230. My bluetooth module is disabled.
Description of problem: After updating, the problem appeared at system bot Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: Al momento del arranque del sistema Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: I don't know Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
*** Bug 1552766 has been marked as a duplicate of this bug. ***
selinux-policy-3.13.1-283.27.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424
Description of problem: This happened on boot right after today's upgrade. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: At the first boot after a "fixfiles onboot" Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: Alert SELinux at the boot of system after update system of 07/08/2018 on Fedora 27 Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: Popped up after the latest system update and restarting the laptop afterwards. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: When booting my system, this SELinux alert appears. I find strange that the process name is "uetoothd". I would have expected "bluetoothd". Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
*** Bug 1553117 has been marked as a duplicate of this bug. ***
Description of problem: Not sure why this happened. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
What does "Status: NEW → POST" mean?
Description of problem: Ran dnf update and rebooted. The only relevant package I can think of was blueberry, updated from 1.1.20-1.fc27 to 1.1.20-6.fc27. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: I plugged my USB bluetooth device into a USB port then the SEL alert immediately occurred. With that USB bluetooth device still plugged in, lsusb showed: [pete@E6430 doc-sys]$ /usr/bin/lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:648b Microdia Integrated Webcam Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [pete@E6430 doc-sys]$ Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
selinux-policy-3.13.1-283.27.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-32ebae3424
Description of problem: Presumably in connection with connecting a bluetooth device (Parrot Zik 2.0 headset?) "uetoothd"? A typo somewhere? Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: This message seems to be generated by SELinux Troubleshooter everytime I login to GNOME. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: This selinux error message started to appear after a dnf system-upgrade from Fedora 26 to 27. Looks like a typo in some selinux rule ? Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: AVCs seen on fresh boot Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: Problem occurs after logging into gnome. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
Description of problem: Whenever I start my computer and enter with my password this error happens. I do not do anything to show it. Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
selinux-policy-3.13.1-283.28.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424
*** Bug 1554699 has been marked as a duplicate of this bug. ***
Description of problem: I get the SELinux message on system startup after logging in to the desktop environment via GDM. I have not changed bluetooth settings (not intentionally to my knowledge, anyway). Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.7-300.fc27.x86_64 type: libreport
selinux-policy-3.13.1-283.28.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-32ebae3424
Description of problem: Seen on fresh boot Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.6-300.fc27.x86_64 type: libreport
I have seen this problem 'shortly after' - not immediately after - I upgraded to Fedora 27 on two laptops: one Macbook Pro 11.3 and one Macbook Air (late 2010). It happens consistently on every startup. I am running sddm and plasma KDE on both laptops. I do not have wireshark installed and no application is launched at startup. As soon as the plasma display opens, the Selinux complains about uetoothd and mounton, every time.
Description of problem: No conecta el bluetooth en lenovo g40-70 Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.9-300.fc27.x86_64 type: libreport
selinux-policy-3.13.1-283.28.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: The problem happend after I turned on the bluetooth from the Fedora setting. Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.9-300.fc27.x86_64 type: libreport
Description of problem: I was not using bluetooth. It just appeared on it's own Version-Release number of selected component: selinux-policy-3.13.1-283.26.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.15.8-300.fc27.x86_64 type: libreport