10

I cannot start FileZilla. When I do it, nothing happen. I tried uninstalling and then reinstalling it, but no help. I am using Ubuntu 16.04.

If I start it from the command line, I see the following:

Reading locale option from /home/superuser/.config/filezilla/filezilla.xml

(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed
(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed
(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed
(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed
(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed
(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed
(filezilla:16389): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'width >= -1' failed
Program segmentation fault ( core dumped )
Pablo Bianchi
  • 17,371
velut luna
  • 381

6 Answers6

13

You can reset FileZilla to defaults by making sure that all copies of FileZilla are definitely closed and then running the following command:

mv -v /home/superuser/.config/filezilla/ /home/superuser/.config/filezilla_bak

Then reopen FileZilla which will build a new, clean set of local preferences. This should be enough to get around what is more than likely a bad, local configuration file.

andrew.46
  • 39,359
5

I had the exact same issue. I presumed there was an issue with the filezilla.xml file. I went to /home/$USER/.config/Filezilla/ deleted the old filezilla.xml file.

Then went back into the terminal and typed "filezilla" to open the program. For me, it opened fine and it created a brand-new default XML file in the old file's place. The site manager options are not affected by this as they are in a different file called "sitemanager.xml" which is in the same directory. So the program opened as a fresh new program with the same site manager options as before.

Pablo Bianchi
  • 17,371
Kevin Moore
  • 51
4

Go to ~/.config/Filezilla or ~/.filezilla.

You need to press Ctrl+H to show hidden files if necessary.

Then open filezilla.xml using a text editor.

Remove the Last local directory tag.

Save the file again and reopen filezilla.

This works for me every time.

djhurio
  • 441
Pavan Mehta
  • 141
  • 1
3

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
Community
  • 1
Kreuvf
  • 321
3

In addition to andrew.46 answer, you can now import the old sitemanager.xml file in the backup folder once filezilla opens. Use File->Import menu. This is useful if you had a lot of sites saved.

nssy
  • 31
0

Probably last known window size has become invalid due to a crash or something, as the error message states here:

assertion 'height >= -1' failed

Look for a line into your /home/superuser/.config/filezilla/filezilla.xml file containing:

<Setting name="Window position and size">0 14 38 1098 576 </Setting>

It'll have different values, probably some could be negative. If the line doesn't exist just add it before the line with </Settings>

Use the settings I posted above, as good known state.

Save filezilla.xml and you now should be able to open Filezilla again.

dgonzalez
  • 7,310