filezilla complains of assertion failed on launch

[Nicolás Abel Carbone]

Fillezilla displays an error at opening:

An assertion failed!
../src/gtk/toplevel.cpp(988): assert "m_widget" failed in Show(): invalid frame

I attach the backtrack.

The program runs fine if the error dialog is dismissed, but it shows again in next start despite unselecting "Show this dialog next time"

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: filezilla 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Mar 8 15:09:02 2018
ExecutablePath: /usr/bin/filezilla
InstallationDate: Installed on 2018-02-23 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: filezilla
Signal: 5
SourcePackage: filezilla
StacktraceTop:
 raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:51
 wxGUIAppTraits::ShowAssertDialog(wxString const&) () at /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
 wxAppConsoleBase::OnAssertFailure(wchar_t const*, int, wchar_t const*, wchar_t const*, wchar_t const*) () at /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
 wxApp::OnAssertFailure(wchar_t const*, int, wchar_t const*, wchar_t const*, wchar_t const*) () at /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
Title: filezilla crashed with signal 5 in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1737374, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.