TL;DR:
In filezilla.xml
there is the empty element <Setting name="Language Code" type="string" />
. If you add an installed locale such as en_GB.UTF-8
(use locale -a
to find available locales), so that you get <Setting name="Language Code" type="string">en_GB.UTF-8</Setting>
everything should run smoothly again.
The long version:
I recently ran into this problem as well, using Ubuntu 16.04.3 and FileZilla 3.15.0.2.
The solutions posted here are based on deleting stuff, but that did not solve my problem. I could start FileZilla again, indeed, but it would still crash on start-up if the last local directory contained non-ASCII characters. File and directory names with non-ASCII characters were just blank. Uploading these was also no good idea.
The following line is the culprit:
<Setting name="Language Code" type="string" />
as I would have expected some language or encoding (such as ISO 8859-15). So, I tried one of my installed locales:
<Setting name="Language Code" type="string">en_GB.UTF-8</Setting>
Now, starting FileZilla would show files and directories with non-ASCII characters again.
If you want to find out which locales you have installed, use:
locale -a
If you are not sure whether you are also affected by this issue, this might help: When running filezilla --version
with the empty language code, the output looks like this:
Reading locale option from /home/kreuvf/.filezilla/filezilla.xml
FileZilla 3.15.0.2, compiled on 2016-02-25
Another indicator I remembered when reading a related question is the following entry in the kern.log
:
kernel: [39162.363835] traps: filezilla[19354] general protection ip:7f99fa048ce6 sp:7fff363ae5e0 error:0 in libwx_gtk2u_core-3.0.so.0.2.0[7f99f9b48000+5f9000]
The different message compared to the linked question may stem from different kernels (more than three years difference) and all the accompanying things that might have changed in the meantime. Nonetheless, in both cases it is libwx_gtk2u_core-3.0.so.0.2.0
and also the offset (?) of 5f9000
matches.
So, if it looks like that for you, chances are good that this solution will work for you. If things are working correctly again, it should look like this:
Reading locale option from /home/kreuvf/.filezilla/filezilla.xml
setlocale en_GB.UTF-8 successful
locale set to en_GB.UTF-8
FileZilla 3.15.0.2, compiled on 2016-02-25
mv -v /home/superuser/.config/filezilla/ /home/superuser/.config/filezilla_bak
and then reopen filezilla