Bug 689716 - [abrt] crash detected in policycoreutils-gui-2.0.74-4.fc12
Summary: [abrt] crash detected in policycoreutils-gui-2.0.74-4.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: policycoreutils
Version: 6.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: BaseOS QE Security Team
URL:
Whiteboard: abrt_hash:4f66cc03
Depends On: 532139
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-22 09:24 UTC by Red Hat Case Diagnostics
Modified: 2018-11-14 13:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-26 14:22:28 UTC
Target Upstream Version:


Attachments (Terms of Use)
File: backtrace (1.05 KB, text/plain)
2011-03-22 09:25 UTC, Red Hat Case Diagnostics
no flags Details
File: backtrace (1.18 KB, text/plain)
2011-03-25 08:21 UTC, Red Hat Case Diagnostics
no flags Details
File: backtrace (1.05 KB, text/plain)
2011-04-14 15:49 UTC, Red Hat Case Diagnostics
no flags Details

Description Red Hat Case Diagnostics 2011-03-22 09:24:52 UTC
+++ This bug was initially created as a clone of Bug 532139 +++


abrt detected a crash.


How to reproduce
-----
1.  Open "system-config-selinux" tool
2.
3.


Comment
-----
I've tried to open SELinux management tool just after login to KDE

Additional information
======


Attached files
----
backtrace

cmdline
-----
/usr/bin/python /usr/share/system-config-selinux/system-config-selinux.py 


component
-----
policycoreutils


executable
-----
/usr/share/system-config-selinux/system-config-selinux.py


kernel
-----
2.6.31-23.fc12.i686


package
-----
policycoreutils-gui-2.0.74-4.fc12


uuid
-----
4f66cc03

--- Additional comment from xeno.pl onFri Oct 30 20:34:50 EDT 2009 ---
Created attachment 366857 [details]
File: backtrace

--- Additional comment from triage.org onMon Nov 16 14:43:55 EST 2009 ---

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from xeno.pl onFri Dec 11 21:44:11 EST 2009 ---
I've tried to reproduce it with fresh updates:
python-2.6.2-2.fc12.i686
policycoreutils-gui-2.0.74-17.fc12.i686
selinux-policy-targeted-3.6.32-55.fc12.noarch

and it seems to be ok now, I couldn't reproduce the crash anymore. I think this bug can be closed.

--- Additional comment from case-diagnostics onMon Jan 03 12:34:22 EST 2011 ---
Created attachment 471474 [details]
File: backtrace

--- Additional comment from case-diagnostics onMon Jan 03 12:34:28 EST 2011 ---
A new attachment to case 00398504 matches the hash in the whiteboard of this bug.
Attachment URL: https://api.access.redhat.com/rs/cases/00398504/attachments/c6425d13-64e6-3109-bca6-3f929dc1c88c
Hash value: abrt_hash:4f66cc03

Comment 1 Red Hat Case Diagnostics 2011-03-22 09:25:12 UTC
Created attachment 486759 [details]
File: backtrace

Comment 4 Tomas Mraz 2011-03-22 09:40:31 UTC
Why it was assigned to authconfig component?

Comment 5 RHEL Program Management 2011-03-22 09:48:49 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 6 Red Hat Case Diagnostics 2011-03-25 08:21:11 UTC
Created attachment 487501 [details]
File: backtrace

Comment 8 Red Hat Case Diagnostics 2011-04-14 15:49:14 UTC
Created attachment 492158 [details]
File: backtrace

Comment 10 Daniel Walsh 2011-05-26 14:22:28 UTC
This bug is caused by people running a gui tool without giving it access to the display.

Since you run this tool as root, you have to give it Xauth capability to reach the display.


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