Description of problem: This error condition occurred immediately after I used the audit2allow for setting up an openvpn connection. The SELinux change was without incident and is working. I don't know if there is any relationship between these events, but there were very close in time. Commands/Procedure used: Imported openvpn file and configured as usual, then, sudo dnf install policycoreutils-devel sudo ausearch -c 'openvpn' --raw | audit2allow -M my-openvpn sudo semodule -X 300 -i my-openvpn.pp Successful working vpn Version-Release number of selected component: tracker-miners-2.0.4-3.fc28 Additional info: reporter: libreport-2.9.4 backtrace_rating: 4 cmdline: /usr/libexec/tracker-miner-fs crash_function: g_type_check_instance_is_a executable: /usr/libexec/tracker-miner-fs journald_cursor: s=e4237f3a17514752946a00216d540877;i=9a6d;b=78b520225ef7469a9ea80338d7719b63;m=2c42357db;t=56d2c0c7d1476;x=2dd488b2945f3830 kernel: 4.16.3-301.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:4013 #1 g_file_equal at gfile.c:769 #2 writeback_remove_recursively at tracker-miner-files.c:266 #3 miner_files_filter_event at tracker-miner-files.c:309 #4 filter_event at tracker-miner-fs.c:2117 #5 file_notifier_file_deleted at tracker-miner-fs.c:2143 #6 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #7 _g_closure_invoke_va at gclosure.c:867 #10 monitor_item_deleted_cb at tracker-file-notifier.c:1305 #11 ffi_call_unix64 at ../src/x86/unix64.S:76
Created attachment 1442228 [details] File: backtrace
Created attachment 1442229 [details] File: cgroup
Created attachment 1442230 [details] File: core_backtrace
Created attachment 1442231 [details] File: cpuinfo
Created attachment 1442232 [details] File: dso_list
Created attachment 1442233 [details] File: environ
Created attachment 1442234 [details] File: exploitable
Created attachment 1442235 [details] File: limits
Created attachment 1442236 [details] File: maps
Created attachment 1442237 [details] File: mountinfo
Created attachment 1442238 [details] File: open_fds
Created attachment 1442239 [details] File: proc_pid_status
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.