Your message dated Wed, 5 Nov 2008 00:40:21 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Reproducibility of the hal selinux bug
has caused the Debian Bug report #498965,
regarding dbus_bus_get(): An SELinux policy prevents this sender from sending 
this message to this recipient
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
498965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498965
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: selinux-policy-default
Version: 2:0.0.20080702-7
Severity: critical
Justification: breaks unrelated software

Hello,

It seems that some SELinux policy prevents hal from starting:


bounty:/# invoke-rc.d hal start
Starting Hardware abstraction layer: haldinvoke-rc.d: initscript hal,
action "start" failed.

bounty:/# hald --daemon=no --verbose=yes
00:08:02.145 [I] hald.c:669: hal 0.5.11
00:08:02.145 [I] hald.c:734: Will not daemonize
00:08:02.145 [I] hald_dbus.c:5381: local server is listening at
unix:abstract=/var/run/hald/dbus-Taiqx8gvk9,guid=e5eb7f12c69f20514e282eea48cd7d32
00:08:02.147 [E] hald_dbus.c:5747: dbus_bus_get(): An SELinux policy
prevents this sender from sending this message to this recipient
(rejected message had interface "org.freedesktop.DBus" member "Hello"
error name "(unset)" destination "org.freedesktop.DBus")


It seems the problems appeared after upgrading these (related) packages:

2008-09-14 17:30:24 upgrade hal 0.5.11-2 0.5.11-3
2008-09-14 21:35:38 upgrade libhal1 0.5.11-2 0.5.11-3
2008-09-14 21:35:38 upgrade libhal-storage1 0.5.11-2 0.5.11-3
2008-09-14 22:50:52 upgrade pulseaudio-module-hal 0.9.10-2 0.9.10-3

2008-09-14 17:30:30 upgrade selinux-utils 2.0.65-2 2.0.65-4
2008-09-14 17:30:31 upgrade setools 2.4-3 3.3.5.ds-1

2008-09-14 21:35:26 upgrade libselinux1-dev 2.0.65-2 2.0.65-4
2008-09-14 21:35:27 upgrade libselinux1 2.0.65-2 2.0.65-4


I tried upgrading to more recent versions from sid, but I have the same
issue:

2008-09-14 23:51:06 upgrade selinux-policy-default 2:0.0.20080702-6
2:0.0.20080702-7
2008-09-14 23:51:10 upgrade setools 3.3.5.ds-1 3.3.5.ds-3
2008-09-14 23:51:11 upgrade libsetools-tcl 3.3.5.ds-1 3.3.5.ds-3
2008-09-14 23:51:14 upgrade selinux-basics 0.3.3+nmu4 0.3.4



-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable'), (10, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages selinux-policy-default depends on:
ii  libpam-modules                1.0.1-4+b1 Pluggable Authentication Modules f
ii  libselinux1                   2.0.65-4   SELinux shared libraries
ii  libsepol1                     2.0.30-2   Security Enhanced Linux policy lib
ii  policycoreutils               2.0.49-5   SELinux core policy utilities
ii  python                        2.5.2-2    An interactive high-level object-o

Versions of packages selinux-policy-default recommends:
ii  checkpolicy                   2.0.16-1   SELinux policy compiler
ii  setools                       3.3.5.ds-3 tools for Security Enhanced Linux

Versions of packages selinux-policy-default suggests:
pn  logcheck                      <none>     (no description available)
pn  syslog-summary                <none>     (no description available)

-- no debconf information

-- 
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein



--- End Message ---
--- Begin Message ---
Version: 2:0.0.20080702-6

OK, I managed to get rid of the bug by removing all selinux packages I
could (and some other packages, too):

    -bwidget 1.8.0-3
    -checkpolicy 2.0.16-1
    -libsetools-tcl 3.3.5.ds-5
    -python-sepolgen 1.0.11-5
    -selinux-utils 2.0.65-5

Then I purged the following:

    -selinux-basics 0.3.5
    -selinux-policy-default 2:0.0.20080702-8
    -setools 3.3.5.ds-5


I reinstalled selinux-basics which pulled through a recommends
selinux-policy-default (complete list follows)

    +bwidget 1.8.0-3
    +checkpolicy 2.0.16-1
    +libsetools-tcl 3.3.5.ds-5
    +python-selinux 2.0.65-5
    +python-semanage 2.0.25-2
    +python-sepolgen 1.0.11-5
    +selinux-basics 0.3.5
    +selinux-policy-default 2:0.0.20080702-6
    +selinux-utils 2.0.65-5
    +setools 3.3.5.ds-5


then I forced a relabeling via "touch /.autorelabel" and rebooted
(relevant boot parameters are: selinux=1 audit=1 ro enforcing=0)


After the relabeling took place, the system rebooted automatically and
then the problem was gone.




So, in conclusion, I suspect a labeling issue was the problem. Since I
am the only person complaining about this, I am closing this bug now.
Thanks for the assistance and I hope you might find the information
relevant for determinign what was the issue and fix it.



-- 
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein


--- End Message ---

Reply via email to