Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 126814 - updates seem to affect system even if selinux is not active
updates seem to affect system even if selinux is not active
Product: Fedora
Classification: Fedora
Component: selinux-policy-strict (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2004-06-27 13:38 EDT by Michal Jaegermann
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-26 14:01:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2004-06-27 13:38:09 EDT
Description of problem:

Even with 'SELINUX=disabled' in /etc/sysconfig/selinux,
and 'selinux=0' in a boot command for a good measure, if
selinux-policy-strict was installed then updating the package
seems to affect the system.  The most visible to me result is
that after such update one cannot open a new shell either
locally or via ssh.  A reboot clears that condition
(together with everything else, unfortunately).

This is only a guess as nothing gets logged anywhere, AFAICT,
but selinux support seems to be the most likely candidate.
I noticed that effect only recently (last two rawhide updates?).

Version-Release number of selected component (if applicable):
Comment 1 Daniel Walsh 2004-07-20 11:14:21 EDT
Are you still seeing this?

Can you run selinuxconfig when it is happening?

Comment 2 Michal Jaegermann 2004-07-20 11:25:19 EDT
I am no longer sure that I attributed that correctly.  See bug #127048.
It seemed at the time that selinux was the most likely candidate but
possibly this was a coincidence.  OTOH I cannot exclude that connection

Yes, this is still happening, although I cannot really predict when.
I will try selinuxconfig when this will strike again.
Comment 3 Michal Jaegermann 2004-07-22 16:17:29 EDT
I got stuck again after the latest round of updates but this does
not seem to a selinux fault because this time around no
selinux-policy packages are installed.

selinuxconfig just prints

selinux state="disabled"

but otherwise does not have any effect.  More details in comments
to bug #127048.
Comment 4 Daniel Walsh 2004-07-26 14:01:31 EDT
Ok I am going to close this bug and allow the other to move forward.

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