Hide Forgot
abrt version: 1.1.14 architecture: i686 cmdline: /usr/bin/python -Es /usr/bin/sealert -s comment: The above steps will reproduce this every time. component: setroubleshoot executable: /usr/bin/sealert kernel: 2.6.35.10-74.fc14.i686.PAE package: setroubleshoot-server-3.0.23-1.fc14 reason: allow_execstack.py:92:get_if_text:IndexError: tuple index out of range release: Fedora release 14 (Laughlin) time: 1296493830 uid: 500 backtrace ----- allow_execstack.py:92:get_if_text:IndexError: tuple index out of range Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/setroubleshoot/browser.py", line 648, in on_details_button_clicked message = self.alert_list[self.current_alert].format_text() File "/usr/lib/python2.7/site-packages/setroubleshoot/signature.py", line 545, in format_text txt = self.substitute(p.get_if_text(self.audit_event.records, args)) File "/usr/share/setroubleshoot/plugins/allow_execstack.py", line 92, in get_if_text path = args[0] IndexError: tuple index out of range Local variables in innermost frame: self: <plugins.allow_execstack.plugin object at 0xaffc9ec> args: () avc: [<setroubleshoot.audit_data.AuditRecord object at 0xaf9bb4c>, <setroubleshoot.audit_data.AuditRecord object at 0xaf9bb6c>] How to reproduce ----- 1. Ran RSSOWL which produced an selinux "permission denied" message about executable stack. 2. SELinux Alert Browser came up about the execstack, though the source process said soffice.bin and now RSSOWL (which uses java) for some reason. 3. Clicked on Details within SELinux alert browser, and received a crash notification from ABRT.
Created attachment 476240 [details] File: backtrace
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I was browsing through alerts with the "Previous" and "Next" buttons. 2. 3.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- No idea...
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.viewing some old Secure linux reports 2.deleting them 3.using a Active Directory administrator user
This is caused by a mismatch between the plugins and the time the alert was cought. Can you just list all alerts and delete the allow_execstack alert. Then the problem will go away.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. not sure, I changed the boolean "setsebool -P allow_postfix_local_write_mail_spool 1"
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Save a file from an email (in this case pdf) 2. Error popup 3. Comment ----- Happened different times, even with other files than pdf. just tried to save an attachment from an email
This bug https://bugzilla.redhat.com/show_bug.cgi?id=652297 or this blog will tell you how to fix the allow_execstack SELinux policy problem. http://danwalsh.livejournal.com/39155.html http://danwalsh.livejournal.com/38736.html The setroubleshoot problem is caused by a newer plugin then the when the original execstack happened, I believe. If you delete the alert and it happens again setroubleshoot will not crash.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I got this when I cleaned my list of old SE alerts by repeatedly clicking delete. I probably had an execstack alert in the queue.
IMHO the improved handling of allow_execstack itself is fine, but I would like to clarify that it IMHO is not so fine that it isn't backwards compatible.
Yes I am fixing that problem. :^( Fixed in setroubleshoot-plugins-3.0.13.fc14
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Deleted last event 2. Close app 3.
setroubleshoot-plugins-3.0.13-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/setroubleshoot-plugins-3.0.13-1.fc14
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I was configuring access to a Windows shared folder. No idea how to reproduce it, nor did I try. 2. 3.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Deleted one avc denial in selinux alert browser Unknown how reproducible
setroubleshoot-plugins-3.0.13-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update setroubleshoot-plugins'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/setroubleshoot-plugins-3.0.13-1.fc14
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Started up Fedora 14 Logged on to it. Had an SELinux alert. Clicked on it to look at it. error was in exec-plugin wanted to laaok at the details ----crash Comment ----- I had an alert in SELINUX and wanted to look at it. Normally you have a description and how to resolve it. When I wanted to look at that it chrashed.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open SE-Policy-Window Comment ----- After I get an SE Policy-Alert I want to configure it. I click on the icon in the systray to open the SE Policy-Program
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Got SElinux denial notification 2. Clicked on icon to start troubleshooter 3. Got crash notification
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. install wifi driver 2. install wifi scanner 3. crash happen
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Deleted one of the SELinux messages 2. 3.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Tried to open the Details option on an SELinux Alert (which usually pops up when Firefox is opened) 2. 3. Comment ----- There seems to be some plug-in in Firefox that is stack executable as the SE Linux message pops up all the time.
Did you update to the latest plugins?
Yes, to the extent that plug-ins are updated in Fedora or Fusion repositories .. I update my system almost daily.
The fix is in updates-testing right now.
yum -y update --enablerepo=updates-testing setroubleshoot\*
Thanks for such a quick response. Update completed as suggested above. The Troubleshoot option in SE Linux Alert now points to nspluginwrapper as the culprit ... /usr/lib64/nspluginwrapper/plugin-config on my system. It suggests three possible solutions, 1) reporting a bug ("if you do not think /usr/lib64/nspluginwrapper/plugin-config should need to map stack memory that is both writable and executable", 2) allowing unconfined executables to make their stack executable (indicated as "should never be necessary", 3) for now, allowing execstack access on processes labeled unconfined_t (indicated as "should be reported as a bug") BTW ... I am a long-time Linux Desktop user and enthusiastic supporter of Fedora/Red Hat, but not a computer pro so I may quickly get beyond my basic skill set on this, given the three options above. I certainly do not know which is the most reasonable option, although 2 and 3 certainly look like more potential problems in the making.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. On a freshly rebooted system with NOTHING yet running, 2. I Saw a warning about a security violation, and so I clicked to see it. 3. I clicked on the "Details" button in the SELinux Alert Browser BOOM! core dump. Comment ----- I hope this backtrace enables fixing what was a surprising core dump during what one would expect is a VERY ordinary activity.
setroubleshoot-server-3.0.25-1.fc14 should fix that problem
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Received a sealert warning 2. openened tool to fix 3. crash
Please attach /var/lib/setroubleshoot/setroubleshoot_database.xml
Hi Daniel, here's my setroubleshoot_database.xml file, I'll attach to this ticket. I haven't tried reproducing this bug since reported it, and have not tried updating setroubleshoot\* from updates-testing yet.
Created attachment 478090 [details] Requested setroubleshoot_database.xml
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Opened 'SELinux Troubleshooter' to see if that's why the Eaton 'Intelligent Power Protector' software isn't working. 2.I scrolled back to message 2 of 3, then forward to message 3 of 3. 3.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Opened 'SELinux Troubleshooter' to see if that's why the Eaton 'Intelligent Power Protector' software isn't working. 2.I scrolled back to message 1 of 2, then forward to message 2 of 2. 3.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Click on SE Linux warning after booting up. 2. Click 'Details' to see more information about the warning
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.trying to see some alerts 2. 3.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No idea. 2. 3.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I was deleting notifications in SELinux 2. 3.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don't know.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. 8 Comment ----- 8
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. All I did was reboot and got these crash messages.....
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I try to see the information and the program crash
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Clicked 'Ignore' on alert view page 2. Then clicked 'Previous error' 3.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don't remember :(
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just handling sel warnings 2. 3.
Package: setroubleshoot-server-3.0.15-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.instalar wine (no hubo problemas aquí) 2.abrir "mspaint.exe" 3.selinux alerta aparece 4.caída
Package: setroubleshoot-server-3.0.19-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Was just looking at the log of errors from the SELinux tool. 2. Did a relabel as suggested by the SELinux tool of my home directories 3. Upon browsing further with the SELinux tool it crashed Comment ----- Also happened without the relabel of home.
Package: setroubleshoot-server-3.0.23-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Logged out after update 2. Logged back in after logging out. 3. Comment ----- logged out after an update to the system. I logged back into the system and SElinux crashed. This came up.
Package: setroubleshoot-server-3.0.25-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.no idea 2. 3.
setroubleshoot-plugins-3.0.13-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.