Cannot reproduce

Any chance we can get a backtrace? Any errors in dmesg?

Same for me (exact same output, exact same version of filezilla).

dmesg only outputs the following line:
[855677.804541] traps: filezilla[28417] general protection ip:7f328e9c71b6 sp:7fffdfd4c410 error:0 in libwx_gtk2u_core-3.0.so.0.2.0[7f328e4b5000+60a000]

I've searched the filezilla forum & issue tracker, but found nothing useful :(
[https://forum.filezilla-project.org/index.php]
[https://trac.filezilla-project.org/wiki/Queries]

Any quick pointer on where to start with generating a backtrace?

Thank you

That's enough to make me wonder if it's a theme issue. Try a different gtk2 theme.

Hello, I just updated to the latest filezilla v3.16.0-1, but it still wouldn't start.

So; I moved $HOME/.filezilla/filezilla.xml out of the way for a clean slate.

Now it started :)

I was using a non-standard theme ('Blukis'), & the clean config uses 'OpenCrystal',
however once it's started successfully with the clean config file;
I've switched back to Blukis, & it's continuing to start correctly as expected.

So; something else must be causing the issue... </sherlock>

I selectively deleted lines & tried launching; I diff'ed once it worked;

This line was causing the issue;
<Setting name="Last local directory" type="string">/SOME/PATH/THAT/NO/LONGER/EXISTS</Setting>

I had recently done some refactoring of my files, & so that remembered-path
(from the last time Filezilla was shutdown) no longer existed.

Thus; I simply removed the path:
<Setting name="Last local directory" type="string"></Setting>

And now everything is working great :)

Thank you all for your time.

^_^

--HEAD KANGAROO
KangarooCreativeTeam.com™

Hi, Thanks for the tips. I wiped the filezilla config folder but establish a connection is not possible:
------------
wxD-Bus: CPowerManagementInhibitor: Requesting busy
Segmentation fault (core dumped)
--------------

I will create a new bug. This bug can be closed because the segmentation fault seems to be solved as discussed above