Description of problem: latest chrome 7880:7880:0613/104503:ERROR:shared_memory_posix.cc(290)] Creating shared memory in /dev/shm/.com.google.Chrome.aGwmG9 failed: Permission denied [7880:7880:0613/104503:ERROR:shared_memory_posix.cc(293)] Unable to access(W_OK|X_OK) /dev/shm: Permission denied [7880:7880:0613/104503:FATAL:shared_memory_posix.cc(295)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. Aborted (core dumped) SELinux is preventing google-chrome-s from 'create' accesses on the file 63. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that google-chrome-s should be allowed create access on the 63 file 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 'google-chrome-s' --raw | audit2allow -M my-googlechromes # semodule -X 300 -i my-googlechromes.pp Additional Information: Source Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Context unconfined_u:object_r:unconfined_t:s0 Target Objects 63 [ file ] Source google-chrome-s Source Path google-chrome-s Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-194.fc25.noarch selinux- policy-3.13.1-195.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.7.0-0.rc2.git1.1.fc25.x86_64 #1 SMP Tue Jun 7 13:28:43 UTC 2016 x86_64 x86_64 Alert Count 5 First Seen 2016-05-26 15:42:46 BST Last Seen 2016-06-13 10:28:38 BST Local ID 451ced9a-8fe3-4a2b-9718-57c538f7c220 Raw Audit Messages type=AVC msg=audit(1465810118.119:243): avc: denied { create } for pid=7433 comm="google-chrome-s" name="63" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=file permissive=0 Hash: google-chrome-s,unconfined_t,unconfined_t,file,create Version-Release number of selected component: selinux-policy-3.13.1-194.fc25.noarch selinux-policy-3.13.1-195.fc25.noarch Additional info: reporter: libreport-2.7.1 hashmarkername: setroubleshoot kernel: 4.7.0-0.rc2.git1.1.fc25.x86_64 reproducible: Not sure how to reproduce the problem type: libreport
Fixed in selinux-policy-3.13.1-196.fc25.noarch
This problem is now affecting Fedora 24 with the 4.7.2 kernel. Will this fix be backported?
Getting the same avc on F24 + 4.7.2
Got this error today after update on F24 + 4.7.2
*** Bug 1372909 has been marked as a duplicate of this bug. ***
*** Bug 1372931 has been marked as a duplicate of this bug. ***
Need this back ported to f23, f24, f25
Description of problem: Happened in the background on restoring Chrome windows after upgrade of Chrome and reboot Version-Release number of selected component: selinux-policy-3.13.1-158.21.fc23.noarch Additional info: reporter: libreport-2.6.4 hashmarkername: setroubleshoot kernel: 4.7.2-101.fc23.x86_64 type: libreport
Description of problem: Indításkor jelzett Version-Release number of selected component: selinux-policy-3.13.1-158.21.fc23.noarch Additional info: reporter: libreport-2.6.4 hashmarkername: setroubleshoot kernel: 4.7.2-101.fc23.x86_64 type: libreport
same problem ++++ SELinux is preventing google-chrome-s from create access on the file 63. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that google-chrome-s should be allowed create access on the 63 file 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 'google-chrome-s' --raw | audit2allow -M my-googlechromes # semodule -X 300 -i my-googlechromes.pp Additional Information: Source Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Context unconfined_u:object_r:unconfined_t:s0 Target Objects 63 [ file ] Source google-chrome-s Source Path google-chrome-s Port <Unknown> Host Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.14.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name Platform Linux 4.7.2-201.fc24.x86_64 #1 SMP Fri Aug 26 15:58:40 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-05 19:28:43 EET Last Seen 2016-09-05 19:28:43 EET Local ID c3983017-3e9e-4e15-b57f-55ec1d4d5b58 Raw Audit Messages type=AVC msg=audit(1473096523.992:226): avc: denied { create } for pid=2126 comm="google-chrome-s" name="63" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=file permissive=0 Hash: google-chrome-s,unconfined_t,unconfined_t,file,create
Description of problem: On opening Version 53.0.2785.92 (64-bit) of Google Chrome, SELinux Alert popped up. Version-Release number of selected component: selinux-policy-3.13.1-158.21.fc23.noarch Additional info: reporter: libreport-2.6.4 hashmarkername: setroubleshoot kernel: 4.7.2-101.fc23.x86_64 type: libreport
This still happens. fedora 24 and google-chrome-stable 53.0.2785.92-1 SELinux is preventing google-chrome-s from create access on the file 63. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that google-chrome-s should be allowed create access on the 63 file 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 'google-chrome-s' --raw | audit2allow -M my-googlechromes # semodule -X 300 -i my-googlechromes.pp Additional Information: Source Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Context unconfined_u:object_r:unconfined_t:s0 Target Objects 63 [ file ] Source google-chrome-s Source Path google-chrome-s Port <Unknown> Host w520 Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.14.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name w520 Platform Linux w520 4.7.2-201.fc24.x86_64 #1 SMP Fri Aug 26 15:58:40 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-06 12:43:26 EEST Last Seen 2016-09-06 12:43:26 EEST Local ID e412f736-ea88-44a3-9dcb-162c77a5b0fe Raw Audit Messages type=AVC msg=audit(1473155006.704:211): avc: denied { create } for pid=4562 comm="google-chrome-s" name="63" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=file permissive=0 Hash: google-chrome-s,unconfined_t,unconfined_t,file,create
F24 and latest Chrome stable (53.0.2785.92). SELinux is preventing google-chrome-s from 'create' accesses on the file 63. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that google-chrome-s should be allowed create access on the 63 file 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 'google-chrome-s' --raw | audit2allow -M my-googlechromes # semodule -X 300 -i my-googlechromes.pp Additional Information: Source Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Context unconfined_u:object_r:unconfined_t:s0 Target Objects 63 [ file ] Source google-chrome-s Source Path google-chrome-s Port <Unknown> Host t450s Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.14.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name t450s Platform Linux t450s 4.7.2-201.fc24.x86_64 #1 SMP Fri Aug 26 15:58:40 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-06 07:59:19 BRT Last Seen 2016-09-06 07:59:19 BRT Local ID ee903a0b-d197-4bea-a617-2e2a60ee9168 Raw Audit Messages type=AVC msg=audit(1473159559.702:264): avc: denied { create } for pid=2974 comm="google-chrome-s" name="63" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=file permissive=0 Hash: google-chrome-s,unconfined_t,unconfined_t,file,create
This should not be allowed. Aside from the /dev/shm error (which may be unrelated), this seems identical to bug 1370475, which seems to be a kernel bug, but does not cause a fatal error to applications.
I agree, I am now seeing this in other domains. we need to add dontaudit domain self:file create;
Description of problem: Run google chrome right after start-up Version-Release number of selected component: selinux-policy-3.13.1-158.21.fc23.noarch Additional info: reporter: libreport-2.6.4 hashmarkername: setroubleshoot kernel: 4.7.2-101.fc23.x86_64 type: libreport
I am also facing the same problem. Fedora-24 KDE Kernel : 4.7.2 SE Linux Policy : 3.13.1-191.14
Description of problem: Google Chrome browser was updated to version 53.0.2785.101-1. When I started the browser, this SELinux warning came up. Version-Release number of selected component: selinux-policy-3.13.1-158.21.fc23.noarch Additional info: reporter: libreport-2.6.4 hashmarkername: setroubleshoot kernel: 4.7.2-101.fc23.x86_64 type: libreport
*** Bug 1339410 has been marked as a duplicate of this bug. ***
*** Bug 1370098 has been marked as a duplicate of this bug. ***
*** Bug 1373023 has been marked as a duplicate of this bug. ***
*** Bug 1370003 has been marked as a duplicate of this bug. ***
*** Bug 1373669 has been marked as a duplicate of this bug. ***
*** Bug 1374258 has been marked as a duplicate of this bug. ***
*** Bug 1374318 has been marked as a duplicate of this bug. ***
Description of problem: Start-up after most recent update. Chrome is running Hangouts and Keep "apps" maybe one of those fired this off? Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: each time starting google chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Make sure google chrome application is closed. Open google chrome, SELinux Alert appears in lower corner. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: run google chrome stable following update selinux pops up avc denial Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Everytime I try to open google chrome for the first time after booting my notebook this happens. It started to trigger after I made and update on my SO. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: After updating to Google Chrome (google-chrome-stable-53.0.2785.101-1.x86_64) I started receiving the warning message from SElinux. Unfortunately, it's not clear to me what the path for the file "63" is. Doing a search of the filesystem, it appears like it may be a file in /proc. I may be submitting this report to the wrong people but just in case. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Every time i opened the chrome the systme show the notice of avc denial. It shows an attemp from chrome to access file 63. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: start chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Las pestañas de google chrome se encontraban abiertas, seleccione reiniciar equipo y actualizar sin cerrar chrome y el evento sucedió. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: google chrome is giving selinux alert on start. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: I was booting the computer. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Starting Google Chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Most recent dnf update caused this error. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Opening google-chrome version 53.0.2785.101 (64 bit). Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: I launched google chrome and this immediately happened Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Start Chrome, get SE alert. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: dwnlded Vivaldi 1.4 64bit RPM choose to open with yumex installed first open produced alert Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: I just opened Google Chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Logged into machine after it was powered off. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: After installing google chrome the error comes up every so often. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: opened chrome browser Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
FYI, we need to backport this policy fix to systems running kernel v4.7 or higher.
Description of problem: I have a google account attached to google chrome and it automatically logs in at each chrome start. 1. Open google chrome. 2. Reboot. 3. Open google chrome again. Chrome doesn't complain but SElinux does. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Was just using chrome with a couple of tabs open. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
This issue is dontaudited in all supported Fedoras (23,24,25,Rawhide.) Fix will be part of new updates.
Description of problem: Error occured right after opening Google Chrome. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Happens every time I open Google Chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Exactly the problem occurs every time you open the last stable kernel as well as with 4.7.3 relace Chrome-200. x86_64 fc24 rack-.
Description of problem: This has been happening for some time now. I was thinkning that it will resolve after some updates but it seems that it needs to be reported. Sorry for the noise if it's unrelated or not a bug. Thanks. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: I just launched Google Chrome. I know Google Chrome is not part of Fedora, and is not a FLOSS either. But audit2allow suggests: allow unconfined_t self:file create; and that is strange. I do not know well SELinux but it seems that chrome, even being unconfined_t, cannot create a file. It that the correct interpretation? Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
There are so many reports from F24 (including mine), that I think the bug must be reopened against F24. I would have preferred to open a new one, but setroubleshoot consider this bug as a duplicate, even if its resolution is RAWHIDE. So let's reopen this bug, and target it to F24.
Please leave it reported on Rawhide. For F24 we have another BZ. Update with fix for this issue is in fedora-testing repos. https://bodhi.fedoraproject.org/updates/FEDORA-2016-fe39b806b6
Description of problem: juste launching google chrome, not first time... maybe after update... look like it wants to access and create files withour permissions should we trust google ? Regarde Arikomagik Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: When I open Google Chrome Application then this message is displayed via SELinux. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Using XFCE on Fedora 24, Google Chrome throws an SELinux access error. This occurs when Chrome is opened from the Applications menu or when it is opened with a keyboard shortcut (Super + b). This seems to be a error caused by the application itself, not by how it is opened. Although instructions are provided on how to resolve this temporarily, I am unsure of the root cause and don't know how to resolve it more permanently. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
I also had this issue, and I can confirm that the update from testing solves it. Thanks !
Description of problem: avvio google-chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: This problem is happening after starting the latest version of Google Chrome (53.0.2785.116) Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: start chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Each time you start the Google Chrome browser gives me this error in Fedora 24 - 64 bits Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Description of problem: Started Chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: starting chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: I frist did a fresh install of fedora then ran dnf distro-sync then downloaded google-chrome rpm file the google's site then installed rpm using gnome software center then launched the program and the bug report got generated Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Launched Google Chrome. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Just opened a new terminal with zsh (Terminix Quake mode to be specific), but the issue is happening with bash, so I don't know what really happened. Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Oh, I see it now, it happened with the command `screenfetch` which I use in my ~/.zshrc.
Description of problem: Errors occurs on startup of Google Chrome consistantly. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Launch google chrome (current version 53.0.2785.116 (64-bit)) Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: On opening Google Chrome right after starting up Fedora, I get this SELinux Alert. I haven't had any usability problem following the alert. Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
+1 To this happening with me: SELinux is preventing google-chrome-s from create access on the file 63. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that google-chrome-s should be allowed create access on the 63 file 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 'google-chrome-s' --raw | audit2allow -M my-googlechromes # semodule -X 300 -i my-googlechromes.pp Additional Information: Source Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Context unconfined_u:object_r:unconfined_t:s0 Target Objects 63 [ file ] Source google-chrome-s Source Path google-chrome-s Port <Unknown> Host eldenador.giftdigital Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.14.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name eldenador.giftdigital Platform Linux eldenador.giftdigital 4.7.3-200.fc24.x86_64 #1 SMP Wed Sep 7 17:31:21 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-21 09:15:56 AEST Last Seen 2016-09-21 09:15:56 AEST Local ID b706b9dd-148b-47ed-8fe9-bbfa5ec62be9 Raw Audit Messages type=AVC msg=audit(1474413356.348:205): avc: denied { create } for pid=2245 comm="google-chrome-s" name="63" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unconfined_t:s0 tclass=file permissive=0 Hash: google-chrome-s,unconfined_t,unconfined_t,file,create
Description of problem: Every start Google-chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: Starting google-chrome Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: It happened while using chrome to watch videos Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport
Description of problem: started chrome after a power failure Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.3-200.fc24.x86_64 type: libreport