ufw 0.31: UnicodeDecodeError errors

So, even this fails:
sudo LC_ALL=tr_TR.UTF-8 ufw status

So it seems we did not actually fix the original bug correctly. I have test cases now to test this and will revert the fix.

LC_ALL=tr_TR.UTF-8 ufw status doesn't fail for me. I don't have even Turkish translations (they aren't shipped).

Hm, anyway, it can fail for you if you have them from other sources than the shipped tarball, but the original issue IS fixed. Just saying. :)

I am actually unable to trigger the "string" vs "strIng" issue at all within ufw itself if I revert the codecs.open() change. Eg, if I apply the following diff to src/backend.py:

=== modified file 'src/backend.py'
--- src/backend.py 2011-05-14 16:03:00 +0000
+++ src/backend.py 2012-03-12 23:03:33 +0000
@@ -205,6 +205,7 @@

             orig.close()

+ print self.defaults
         # do some default policy sanity checking
         policies = ['accept', 'accept_no_track', 'drop', 'reject']
         for c in [ 'input', 'output', 'forward' ]:

Then do:
$ sudo LC_TYPE=tr_TR.UTF-8 ufw status
{'ipt_modules': 'nf_conntrack_ftp nf_nat_ftp nf_conntrack_netbios_ns', 'default_output_policy': 'accept', 'loglevel': 'low', 'manage_builtins': 'no', 'enabled': 'no', 'default_input_policy': 'drop', 'default_forward_policy': 'drop', 'ipv6': 'yes', 'default_application_policy': 'skip'}
Status: inactive

You can see that I don't have default_Input_policy, but the proper 'default_Input_policy'. I think that this ufw-frontends needs to be adjusted. Please file a new bug. I am reverting this change in ufw.

I installed the language-pack-tr translations in Ubuntu and cannot trigger the issue in ufw. Please file a new bug with a reduced test case on how ufw itself is failing as opposed to how ufw-frontends is using it. I suggest ufw-frontends explicitly set LC_CTYPE for now.

Meh, comment #5 is confusing. First, the indentation is wrong for the diff, and second I should have said:
"You can see that I don't have default_Input_policy, but the proper 'default_input_policy'."

Sigh, this is the actual test I used to prove to myself that this isn't ufw's fault:
$ sudo LC_ALL=tr_TR.UTF-8 ufw status
{u'ipt_modules': u'nf_conntrack_ftp nf_nat_ftp nf_conntrack_netbios_ns', u'default_output_policy': u'accept', u'loglevel': u'low', u'manage_builtins': u'no', u'enabled': u'no', u'default_input_policy': u'drop', u'default_forward_policy': u'drop', u'ipv6': u'yes', u'default_application_policy': u'skip'}
Durum: kapalı

This bug was fixed in the package ufw - 0.31-0ubuntu2

---------------
ufw (0.31-0ubuntu2) precise; urgency=low

  * revert r752 which causes ufw to fail with certain locales (LP: #953372)
 -- Jamie Strandboge <email address hidden> Mon, 12 Mar 2012 18:15:05 -0500

The reason why it's all fine with ufw is it doesn't set up locale*. It gets translated strings but doesn't set the environment which is perfectly fine, I think.

How to test that: if you add these lines to /usr/sbin/ufw:

 24 import locale
 25 locale.setlocale(locale.LC_ALL, '')

then you will get this with LC_ALL=tr_TR.UTF-8 ufw status:
{'Ipt_modules': 'nf_conntrack_ftp nf_nat_ftp nf_conntrack_netbios_ns', 'default_applIcatIon_polIcy': 'skIp', 'loglevel': 'low', 'manage_buIltIns': 'no', 'enabled': 'yes', 'default_Input_polIcy': 'drop', 'default_forward_polIcy': 'drop', 'Ipv6': 'yes', 'default_output_polIcy': 'accept'}
ERROR: Missing policy for 'input'

providing that you don't use codecs.open(), but normal open().

What that frontend changes is that it executes ufw code with user's locale and that's why it is OK in ufw but not there.

I guess nothing is to be changed in ufw then. However please keep this in mind in case you want to implement setting locale in ufw at some point.

Thanks for all!

*import locale; locale.getlocale() returns "(None, None)", unlike in that frontend: "('tr_TR', 'UTF-8')" or any

This was fixed in 0.31.1.