Summary: SELinux is preventing /usr/bin/gdb "write" access on /usr/share/glib-2.0/gdb. Detailed Description: SELinux denied access requested by gdb. It is not expected that this access is required by gdb and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:xdm_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> Host (removed) Source RPM Packages gdb-7.0.1-29.fc12 Target RPM Packages glib2-devel-2.22.3-2.fc12 Policy RPM selinux-policy-3.6.32-69.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.12-174.2.3.fc12.x86_64 #1 SMP Mon Jan 18 19:52:07 UTC 2010 x86_64 x86_64 Alert Count 2 First Seen Tue 26 Jan 2010 07:50:29 PM MST Last Seen Tue 26 Jan 2010 07:50:29 PM MST Local ID 36213101-fcc1-4407-a54e-64be9c9d8a48 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1264560629.300:19): avc: denied { write } for pid=2206 comm="gdb" name="gdb" dev=sda3 ino=94225 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:usr_t:s0 tclass=dir node=(removed) type=SYSCALL msg=audit(1264560629.300:19): arch=c000003e syscall=2 success=no exit=-13 a0=7fff104adf50 a1=2c1 a2=81ed a3=7f65923b3ad0 items=0 ppid=2205 pid=2206 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:xdm_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-69.fc12,catchall,gdb,xdm_t,usr_t,dir,write audit2allow suggests: audit2allow is not installed.
*** This bug has been marked as a duplicate of bug 528554 ***