Red Hat Bugzilla – Bug 1290970
SELinux is preventing /usr/bin/gdb from write access on the directory /usr/share/glib-2.0/gdb.
Last modified: 2016-12-20 11:57:10 EST
SELinux is preventing /usr/bin/gdb from write access on the directory /usr/share/glib-2.0/gdb. ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow gdb to have write access on the gdb directory Then e' necessario modificare l'etichetta su /usr/share/glib-2.0/gdb Do # semanage fcontext -a -t TIPO_FILE '/usr/share/glib-2.0/gdb' dove TIPO_FILE è uno dei seguenti: 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. Quindi eseguire: restorecon -v '/usr/share/glib-2.0/gdb' ***** Plugin catchall (17.1 confidence) suggests ************************** If si crede che gdb dovrebbe avere possibilità di accesso write sui gdb directory in modo predefinito. Then si dovrebbe riportare il problema come bug. E' possibile generare un modulo di politica locale per consentire questo accesso. Do consentire questo accesso per il momento eseguendo: # 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 /usr/share/glib-2.0/gdb [ dir ] Source gdb Source Path /usr/bin/gdb Port <Unknown> Source RPM Packages gdb-7.10-29.fc23.x86_64 Target RPM Packages glib2-devel-2.46.2-1.fc23.x86_64 Policy RPM selinux-policy-3.13.1-155.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Platform Linux 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 x86_64 x86_64 Alert Count 18 First Seen 2015-12-05 08:34:19 CET Last Seen 2015-12-11 08:13:19 CET Raw Audit Messages type=AVC msg=audit(1449817999.371:528): avc: denied { write } for pid=2304 comm="gdb" name="gdb" dev="sdb2" ino=16646889 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir permissive=0 type=SYSCALL msg=audit(1449817999.371:528): arch=x86_64 syscall=mkdir success=no exit=EACCES a0=7fb34da39c20 a1=1ff a2=7fb35d4a9380 a3=7ffda9c490f0 items=0 ppid=2303 pid=2304 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
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.