Bug 1010545 - bus_get_selinux_security_context failed: Broken pipe
Summary: bus_get_selinux_security_context failed: Broken pipe
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-21 10:14 UTC by orti1980
Modified: 2016-07-19 10:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:25:40 UTC
Type: Bug


Attachments (Terms of Use)

Description orti1980 2013-09-21 10:14:48 UTC
Sep 21 12:05:57 localhost systemd: bus_get_selinux_security_context failed: Broken pipe
Sep 21 12:05:57 localhost systemd: Failed to get caller's security context on: Broken pipe
Sep 21 12:05:57 localhost systemd: firewalld.service: main process exited, code=exited, status=1/FAILURE
Sep 21 12:05:57 localhost systemd: Stopped firewalld - dynamic firewall daemon.
Sep 21 12:05:57 localhost systemd: Unit firewalld.service entered failed state.

Comment 1 Jaroslav Reznik 2015-03-03 15:05:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Fedora End Of Life 2016-07-19 10:25:40 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.


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