Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/python -Es /usr/sbin/semanage boolean -l crash_function: apol_attr_get_by_query executable: /usr/bin/python2.7 kernel: 3.7.5-201.fc18.x86_64 remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 apol_attr_get_by_query at type-query.c:132 #1 get_attribs at info.c:176 #2 info at info.c:996 #3 wrap_info at info.c:1023 #4 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4098 #5 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740 #6 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:3330 #7 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4194 #8 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119 #9 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740
Created attachment 694375 [details] File: backtrace
Created attachment 694376 [details] File: cgroup
Created attachment 694377 [details] File: core_backtrace
Created attachment 694378 [details] File: dso_list
Created attachment 694379 [details] File: environ
Created attachment 694380 [details] File: limits
Created attachment 694381 [details] File: maps
Created attachment 694382 [details] File: open_fds
Created attachment 694383 [details] File: proc_pid_status
Created attachment 694384 [details] File: var_log_messages
Thank you for reporting this bug. How reproducible is this problem? If you run the program from a terminal, is an error message printed? What is the output of running the following command? rpm -q policycoreutils-python Looking at the backtrace, it looks like the problem occurred in the program's single thread in apol_attr_get_by_query Reassigning component from "python" to "policycoreutils"; hopefully the policycoreutils maintainer will be able to figure this out further or reassign as necessary.
(In reply to comment #11) > Thank you for reporting this bug. > > How reproducible is this problem? If you run the program from a terminal, > is an error message printed? > > What is the output of running the following command? > rpm -q policycoreutils-python > > Looking at the backtrace, it looks like the problem occurred in the > program's single thread in apol_attr_get_by_query > > Reassigning component from "python" to "policycoreutils"; hopefully the > policycoreutils maintainer will be able to figure this out further or > reassign as necessary. I don't know how to reproduce this problem or what caused this problem? the output is: rpm -q policycoreutils-python policycoreutils-python-2.1.13-55.fc18.x86_64
I can not recreate this bug, but we have fixed some python handling in the latest code.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.