Bug 156825 - After installing dbus-0.33-2, avc: denied { connectto } path=/var/run/dbus/system_bus_socket
After installing dbus-0.33-2, avc: denied { connectto } path=/var/run/dbus...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
rawhide
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-04 11:00 EDT by sangu
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-06 12:12:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
dmesg (55.93 KB, text/plain)
2005-05-04 11:00 EDT, sangu
no flags Details

  None (edit)
Description sangu 2005-05-04 11:00:53 EDT
Description of problem:
After installing dbus-0.33-2, 

in dmesg

audit(1115217595.126:0): avc:  denied  { connectto } for
path=/var/run/dbus/system_bus_socket scontext=system_u:system_r:hald_t
tcontext=system_u:system_r:initrc_t tclass=unix_stream_socket
[...]
 path=/var/run/dbus/system_bus_socket scontext=system_u:system_r:cupsd_config_t
tcontext=root:system_r:unconfined_t tclass=unix_stream_socket

Version-Release number of selected component (if applicable):
selinux-policy-targeted-1.23.14-2

How reproducible:
always

Steps to Reproduce:
1. booting
2.
3.
  
Actual results:
 haldaemon can't start.

Expected results:


Additional info:
hal-0.5.1-1

$ls -Zal /var/run/dbus/system_bus_socket
srwxrwxrwx  1 root:object_r:system_dbusd_var_run_t root root 0  5월  4 23:50
/var/run/dbus/system_bus_socket
Comment 1 sangu 2005-05-04 11:00:53 EDT
Created attachment 114016 [details]
dmesg
Comment 2 Daniel Walsh 2005-05-05 07:38:49 EDT
Please update to the latest policy and you might need to relabel.

touch /.autorelabel; reboot
Comment 3 sangu 2005-05-06 12:12:28 EDT
After doing $touch /.autorelabel; reboot, this problem is fixed.

Question: Does I need to rebabel whenever new policy is installed?


Note You need to log in before you can comment on or make changes to this bug.