Bug 978006

Summary: [abrt] policycoreutils-python-2.1.13-27.3.fc17: __init__.py:28:policy:RuntimeError: Cannot allocate memory
Product: [Fedora] Fedora Reporter: kdg1955 <kdg1955>
Component: policycoreutilsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b05ab736e10dd32302e9236f171a8fd22caa79a7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 00:04:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ none

Description kdg1955 2013-06-25 19:25:41 UTC
Description of problem:
1) selinux is disabled (in /etc/selinux/config)
2) then type on konsole
	$> semanage --help
		Traceback (most recent call last):
		  File "/usr/sbin/semanage", line 25, in <module>
		    import seobject
		  File "/usr/lib64/python2.7/site-packages/seobject.py", line 27, in <module>
		    import sepolicy
		  File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 31, in <module>
		    policy(policy_file)
		  File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 28, in policy
		    _policy.policy(policy_file)
		RuntimeError: Cannot allocate memory
3) abrt reported this error

Version-Release number of selected component:
policycoreutils-python-2.1.13-27.3.fc17

Additional info:
cmdline:        /usr/bin/python -Es /usr/sbin/semanage --help
executable:     /usr/sbin/semanage
kernel:         3.8.13-100.fc17.x86_64
runlevel:       N 5
uid:            1000
ureports_counter: 1

Truncated backtrace:
__init__.py:28:policy:RuntimeError: Cannot allocate memory

Traceback (most recent call last):
  File "/usr/sbin/semanage", line 25, in <module>
    import seobject
  File "/usr/lib64/python2.7/site-packages/seobject.py", line 27, in <module>
    import sepolicy
  File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 31, in <module>
    policy(policy_file)
  File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 28, in policy
    _policy.policy(policy_file)
RuntimeError: Cannot allocate memory

Local variables in innermost frame:
policy_file: None

Comment 1 kdg1955 2013-06-25 19:25:44 UTC
Created attachment 765261 [details]
File: backtrace

Comment 2 kdg1955 2013-06-25 19:25:47 UTC
Created attachment 765262 [details]
File: core_backtrace

Comment 3 kdg1955 2013-06-25 19:25:51 UTC
Created attachment 765263 [details]
File: environ

Comment 4 Daniel Walsh 2013-06-27 19:43:10 UTC
Any chance that you could test this on F18 or F19?  Not likely that we would push a fix on F17.  And I don't run machines with SELinux disabled.  :^)

Comment 5 kdg1955 2013-06-28 11:54:45 UTC
(In reply to Daniel Walsh from comment #4)
> Any chance that you could test this on F18 or F19?  Not likely that we would
> push a fix on F17.  And I don't run machines with SELinux disabled.  :^)

I started to discover selinux, and this was the reason that selinux was still 'disabled' on my PC. 
For my it is LOW priority, but it is a bug (and a fix isn't needed in F17).

Comment 6 Fedora End Of Life 2013-07-03 22:17:45 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2013-08-01 00:04:21 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.