Description of problem: SELinux is preventing /usr/bin/gdb from 'write' accesses on the directory . ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow gdb to have write access on the directory Then you need to change the label on $FIX_TARGET_PATH Do # semanage fcontext -a -t FILE_TYPE '$FIX_TARGET_PATH' where FILE_TYPE is one of the following: abrt_tmp_t, abrt_upload_watch_tmp_t, abrt_var_cache_t, abrt_var_log_t, abrt_var_run_t, mock_var_lib_t, rpm_var_cache_t, rpm_var_run_t, sosreport_tmp_t, tmp_t, var_log_t, var_run_t, var_spool_t, var_t. Then execute: restorecon -v '$FIX_TARGET_PATH' ***** Plugin catchall (17.1 confidence) suggests ************************** If you believe that gdb should be allowed write access on the 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: # grep gdb /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:object_r:usr_t:s0 Target Objects [ dir ] Source gdb Source Path /usr/bin/gdb Port <Unknown> Host (removed) Source RPM Packages gdb-7.7.1-21.fc21.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-166.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.15.0-rc8 #1 SMP Mon Jun 16 15:10:43 JST 2014 x86_64 x86_64 Alert Count 4 First Seen 2014-06-16 16:09:21 JST Last Seen 2014-06-16 16:09:27 JST Local ID a6ea88b6-e26c-4708-b525-f4e4b29c7f36 Raw Audit Messages type=AVC msg=audit(1402902567.523:446): avc: denied { write } for pid=2534 comm="gdb" name="command" dev="sda6" ino=2233149 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir type=SYSCALL msg=audit(1402902567.523:446): arch=x86_64 syscall=open success=no exit=EACCES a0=317aef0 a1=2c1 a2=81a4 a3=39babc55d0 items=0 ppid=2533 pid=2534 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=gdb exe=/usr/bin/gdb subj=system_u:system_r:abrt_t:s0-s0:c0.c1023 key=(null) Hash: gdb,abrt_t,usr_t,dir,write Additional info: reporter: libreport-2.2.2 hashmarkername: setroubleshoot kernel: 3.15.0-rc8 type: libreport Potential duplicate: bug 665543
Description of problem: firefox crashed when i got this error Additional info: reporter: libreport-2.2.2 hashmarkername: setroubleshoot kernel: 3.15.0-rc8 type: libreport
Any idea where the command directory is?
Description of problem: firefox crashed Additional info: reporter: libreport-2.2.2 hashmarkername: setroubleshoot kernel: 3.15.0-rc8 type: libreport
My guess this appened in /usr/share/gdb/python/gdb/command/ For some reason it was trying to compile a phython program.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.