Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 cmdline: /usr/bin/python /usr/sbin/firewalld comment: installed firewalld, as suggested by the printer configuration panel. Installed firewalld-applet as a complement. I then reached for the applet in the bottom right of trhe notification area, checked mdns. The applet crashed. executable: /usr/sbin/firewalld kernel: 3.1.2-1.fc16.x86_64 reason: logger.py:117:open:IOError: [Errno 13] Permission non accordée: '/var/log/firewalld' time: mar. 29 nov. 2011 10:53:20 CET uid: 1000 username: fred backtrace: :logger.py:117:open:IOError: [Errno 13] Permission non accordée: '/var/log/firewalld' : :Traceback (most recent call last): : File "/usr/sbin/firewalld", line 112, in <module> : log.fatal(str(e)) : File "/usr/share/firewalld/logger.py", line 407, in fatal : self._log(self.FATAL, format, *args, **kwargs) : File "/usr/share/firewalld/logger.py", line 681, in _log : target.write(_format % dict, level, self, is_debug) : File "/usr/share/firewalld/logger.py", line 121, in write : self.open() : File "/usr/share/firewalld/logger.py", line 117, in open : self.fd = open(self.filename, self.mode) :IOError: [Errno 13] Permission non accordée: '/var/log/firewalld' : :Local variables in innermost frame: :self: <logger.FileLog instance at 0x7f378b182638>
Is there a /var/log/firewalld file? Which permissions does it have? Is the SELinux context of the file ok? You can fix the context with "restorecon /var/log/firewalld".
*** Bug 767654 has been marked as a duplicate of this bug. ***
After reinstalling firewalld: [root@XXXX yyy]# file /var/log/firewalld /var/log/firewalld: ERROR: cannot open `/var/log/firewalld' (No such file or directory) I since removed firewalld, and because there seems to be nothing more than a gnome 2 applet to easily monitor it. I can reinstall it again, if you need more testing from me. Could you confirm the state of support of this dynamic firewall? It is not installed by default, and apart from the printer dialog, i have no idea of which prgram are aware of it.
*** This bug has been marked as a duplicate of bug 693987 ***