libreport version: 2.0.8 abrt_version: 2.0.7 cmdline: /usr/bin/python -Es /usr/bin/sealert -s comment: looking at this setroubleshoot thingy executable: /usr/bin/sealert kernel: 3.2.3-2.fc16.x86_64 reason: catchall_boolean.py:66:get_then_text:IndexError: tuple index out of range time: Mon 06 Feb 2012 18:42:35 CET uid: 1000 username: ms backtrace: :catchall_boolean.py:66:get_then_text:IndexError: tuple index out of range : :Traceback (most recent call last): : File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 771, in on_previous_button_clicked : self.show_current_alert() : File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 744, in show_current_alert : rb = self.add_row(p, alert, args) : File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 391, in add_row : then_text = alert.substitute(plugin.get_then_text(avc, args)) : File "/usr/share/setroubleshoot/plugins/catchall_boolean.py", line 66, in get_then_text : if os.path.isfile("/usr/share/man/man8/%s_selinux.8.gz" % args[2].split("_")[0]) and args[2] != "": :IndexError: tuple index out of range : :Local variables in innermost frame: :self: <plugins.catchall_boolean.plugin object at 0x469e3d0> :args: ('allow_polyinstantiation', '1') :avc: [<setroubleshoot.audit_data.AuditRecord object at 0x458e310>, <setroubleshoot.audit_data.AuditRecord object at 0x458e350>]
I clicked Details button in Selinux Alert Browser. Package: setroubleshoot-server-3.1.3-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Yes, there is a bug.
Ok, I found it.
emoziko, what is your version of setroubleshoot-plugins $ rpm -q setroubleshoot-plugins
I logged in, abrt popped up. Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
Miroslav have you got this one? Is this broken in Fedora 17? If so lets fix there and back port.
I was checking the SELinux alerts and analysing former and next alerts Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
I was trying to look at a problem in setroubleshoot. When I clicked on details, nothing came up. Unfortunately, I deleted the description before I noticed this bug report. Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
This happened when running sudo yum upgrade (NetworkManager was being upgraded to 0.9.2-1 as part of this). The following SELinux warning popped during the upgrade, followed by this abrtd message: SELinux is preventing /usr/sbin/NetworkManager from read access on the file /etc/sysctl.conf. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that NetworkManager should be allowed read access on the sysctl.conf file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep NetworkManager /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:NetworkManager_t:s0 Target Context system_u:object_r:system_conf_t:s0 Target Objects /etc/sysctl.conf [ file ] Source NetworkManager Source Path /usr/sbin/NetworkManager Port <Unknown> Host igor-hp Source RPM Packages NetworkManager-0.9.4-2.git20120403.fc16.x86_64 Target RPM Packages initscripts-9.34.2-1.fc16.x86_64 Policy RPM selinux-policy-3.10.0-80.fc16.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name igor-hp Platform Linux igor-hp 3.3.1-5.fc16.x86_64 #1 SMP Tue Apr 10 19:56:52 UTC 2012 x86_64 x86_64 Alert Count 2 First Seen Fri 20 Apr 2012 07:55:43 PM EDT Last Seen Fri 20 Apr 2012 07:55:46 PM EDT Local ID 7f0d55af-9915-4df3-b3e0-b09ca060365b Raw Audit Messages type=AVC msg=audit(1334966146.687:448): avc: denied { read } for pid=13357 comm="NetworkManager" name="sysctl.conf" dev="sda5" ino=376246 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:system_conf_t:s0 tclass=file type=SYSCALL msg=audit(1334966146.687:448): arch=x86_64 syscall=open success=no exit=EACCES a0=4c8172 a1=0 a2=0 a3=11 items=0 ppid=1 pid=13357 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=NetworkManager exe=/usr/sbin/NetworkManager subj=system_u:system_r:NetworkManager_t:s0 key=(null) Hash: NetworkManager,NetworkManager_t,system_conf_t,file,read audit2allow #============= NetworkManager_t ============== allow NetworkManager_t system_conf_t:file read; audit2allow -R #============= NetworkManager_t ============== allow NetworkManager_t system_conf_t:file read; Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
I see this rule in selinux-policy-3.10.0-85.fc16
Yes, this is fixed in the latest F16 policy which is in the stable repo.
Opened alerts window with two notifications. Deleted one and then this error poped out. Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
You mean the original error from the comment #1.
Hi, Miroslav. The above was posted through an automatic bug submission in Fedora 16. I am not sure whether the error message is the same but it does look like it. Now I already cleared the alert queue but will report more info if it happens again. Cheers
Opened SELinux Alert Browser, clicked List All Alerts. In the SETroubleshoot Alert List selected a fourth notification out of seven and clicked Delete. Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
So, some index seems to be wrong after a notification is deleted.
Could yout test it with $ rpm -Uvh http://koji.fedoraproject.org/koji/getfile?taskID=4024116&name=setroubleshoot-plugins-3.0.36-1.fc17.1.noarch.rpm
sorry don't have a F17 system to test this on; furthermore can't even reproduce this on F16 by randomly clicking on things; no idea what i had done to get this crash.
I apologize, I missed this is on F16 system.
I was trying to troubleshoot an issue within the SEtroubleshooter. Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
It has been fixed in F17. We need to backport it to F16.
Fixed in setroubleshoot-plugins-3.0.38-1.fc16
(In reply to comment #22) > Fixed in setroubleshoot-plugins-3.0.38-1.fc16 where I can find this updated version of setroubleshoot-plugins? after my latest yum update I have: [root@gianluca gianluca]# yum list setroublesho* Loaded plugins: langpacks, presto, refresh-packagekit Installed Packages setroubleshoot.i686 3.1.3-1.fc16 @updates setroubleshoot-plugins.noarch 3.0.27-1.fc16 @updates setroubleshoot-server.i686 3.1.3-1.fc16 @updates Available Packages setroubleshoot-doc.i686 3.1.3-1.fc16 updates
setroubleshoot-plugins-3.0.38-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/setroubleshoot-plugins-3.0.38-1.fc16
I was attempting to enable setting date and time automatically via KDE system setup. The alert dialog poped up and a notice that it wasn't able to contact pool.ntp.org. I was connected to the Intrnet in the usual manner. Package: setroubleshoot-server-3.1.3-1.fc16 OS Release: Fedora release 16 (Verne)
Emmett please open a separate bug, this looks like a policy issue, not an issue with the tool.
I was deleting alerts Package: setroubleshoot-server-3.1.3-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Package setroubleshoot-plugins-3.0.38-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing setroubleshoot-plugins-3.0.38-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7542/setroubleshoot-plugins-3.0.38-1.fc16 then log in and leave karma (feedback).
Just logged in into F16 Package: setroubleshoot-server-3.1.3-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
setroubleshoot-plugins-3.0.38-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.