ufw crashed with KeyError in get_default_application_policy()

Bug #399290 reported by cement_head
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gui-ufw (Ubuntu)
Invalid
Undecided
Unassigned
ufw (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ufw

switching ufw on/off using Gufw

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/ufw
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx hsfengine wl
Package: ufw 0.23.3
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/sbin/ufw status verbose
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en
 SHELL=/bin/bash
PythonArgs: ['/usr/sbin/ufw', 'status', 'verbose']
SourcePackage: ufw
Title: ufw crashed with KeyError in get_default_application_policy()
Uname: Linux 2.6.27-14-generic i686
UserGroups:

Tags: apport-crash
Revision history for this message
cement_head (andorjkiss) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

It sounds like you don't have these lines in /etc/default/ufw:
# set the default application policy to ACCEPT, DROP, REJECT or SKIP. Please
# note that setting this to ACCEPT may be a security risk. See 'man ufw' for
# details
DEFAULT_APPLICATION_POLICY="SKIP"

These were added in 8.10. Did this machine upgrade from 8.04 LTS? If so, did you merge the /etc/default/ufw changes properly?

Added gufw task as it's possible gufw might have had something to do with the line removal.

visibility: private → public
Changed in ufw (Ubuntu):
status: New → Incomplete
Revision history for this message
cement_head (andorjkiss) wrote :

Hi Jamie,

  Thankyou, thankyou, thanks! Adding those lines fixed the bug AND fixed the lack of the rules showing up in my status window!

- Andor

Changed in ufw (Ubuntu):
status: Incomplete → Fix Released
costales (costales)
Changed in gui-ufw (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.