Today I encountered the next issue with that glorious update to LMDE7. Filezilla is no longer working, even if the package manager doesn’t show any conflicts.
abu@abu-tc ~ $ filezilla
filezilla: symbol lookup error: filezilla: undefined symbol: _ZNK12wxDataFormateqERKS_, version WXU_3.2
After the annoying issue with PHP and IMAP mentioned here, I really think about restoring to LMDE6, where I never had such issues.
@abu :
Hi Alfred, 
Regarding your problem I found this source dealing with the same topic:
https://www.reddit.com/r/voidlinux/comments/bhcxl4/filezilla_does_not_start_symbol_lookup_error/ .
It might be a compatibility issue between FileZilla and one of its dependencies, such as libfilezilla. I´m not completely sure of it but it may be worth looking into it.
Perhaps also here:
Good luck.
Many greetings from Rosika 
I asked Copilot and it gave a pretty interesting answer. The short version is to try to reinstall or recompile FileZilla on LMDE7.
There is a step 3 and 4 for running a make and debug symbols, but hopefully it won’t go that far for you.
I know this doesn’t help you much but Filezilla works for me in Arch.
This was already done as a first step.
abu@abu-tc ~ $ dpkg -l|grep wx
ii libwxbase3.2-1t64:amd64 3.2.8+dfsg-2 amd64 wxBase library (runtime) - non-GUI support classes of wxWidgets toolkit
ii libwxgtk-gl3.2-1t64:amd64 3.2.8+dfsg-2 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK 3 gl library runtime)
ii libwxgtk3.2-1t64:amd64 3.2.8+dfsg-2 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK 3 runtime)
ii libwxgtk3.2-dev:amd64 3.2.8+dfsg-2 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK 3 development)
ii wx-common 3.2.8+dfsg-2 amd64 wxWidgets Cross-platform C++ GUI toolkit (common support files)
ii wx3.2-headers 3.2.8+dfsg-2 all wxWidgets Cross-platform C++ GUI toolkit (header files)
abu@abu-tc ~ $ ldd /usr/bin/filezilla | grep wx
libwx_gtk3u_aui-3.2.so.0 => /usr/local/lib/libwx_gtk3u_aui-3.2.so.0 (0x00007ff9546f1000)
libwx_gtk3u_xrc-3.2.so.0 => /usr/local/lib/libwx_gtk3u_xrc-3.2.so.0 (0x00007ff9545d8000)
libwx_gtk3u_core-3.2.so.0 => /usr/local/lib/libwx_gtk3u_core-3.2.so.0 (0x00007ff953c00000)
libwx_baseu-3.2.so.0 => /usr/local/lib/libwx_baseu-3.2.so.0 (0x00007ff953800000)
libwx_gtk3u_html-3.2.so.0 => /usr/local/lib/libwx_gtk3u_html-3.2.so.0 (0x00007ff952329000)
libwx_baseu_xml-3.2.so.0 => /usr/local/lib/libwx_baseu_xml-3.2.so.0 (0x00007ff954f15000)
abu@abu-tc ~ $ sudo find /usr/local/lib -type f -name "libwx*3.2*"
/usr/local/lib/libwx_gtk3u_media-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_propgrid-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_ribbon-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_core-3.2.so.0.1.0
/usr/local/lib/libwx_baseu_xml-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_stc-3.2.so.0.1.0
/usr/local/lib/libwx_baseu_net-3.2.so.0.1.0
/usr/local/lib/libwx_baseu-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_aui-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_xrc-3.2.so.0.1.0
/usr/local/lib/libwxcode_gtk3u_wxsqlite3-3.2.so.0.0.0
/usr/local/lib/libwx_gtk3u_html-3.2.so.0.1.0
/usr/local/lib/libwxcode_gtk3u_wxsqlite3-3.2.la
/usr/local/lib/libwx_gtk3u_adv-3.2.so.0.1.0
/usr/local/lib/libwx_gtk3u_richtext-3.2.so.0.1.0
/usr/local/lib/libwxcode_gtk3u_wxsqlite3-3.2.a
/usr/local/lib/libwxcode_gtk3u_wxjson-3.2.so.0.0.0
/usr/local/lib/libwx_gtk3u_qa-3.2.so.0.1.0
I installed lmde 7 last week as i was doing some web site work, clean new install of filezilla and it worked no problem, which does not help you sorry.
Uninstall and try again.
Did you get it direct from the repository ?
It has a new interface but no idea when it changed as its something i use perhaps every 6 months and the last time before now was on 32 bit mint.
Yes, of course.
Obviously something has changed; I have to adjust.
I mean, I have done every upgrade from LMDE 3 → 4 → 5 → 6 → 7, but never came across such kinds of trouble. This banana #7 isn’t ripe enough.
I tried Filezilla once in Void or MX, cant remember which.
There were issues. I concluded that its packaging was not up to standard.
I went back to sftp … it always works.
If you want a gui, you can use ftp, sftp, or sshfs in your File Manager
Are you using the ftp server part of filezilla? It seems to have a lot of unsolved bugs
https://trac.filezilla-project.org/query?status=accepted&status=assigned&status=new&status=reopened&component=FileZilla+Server&order=time&col=id&col=summary&col=owner&col=priority&col=time&type=Bug+report&desc=1&report=10
FileZilla has always been my first choice for sftp, Windows or Linux. Hopefully you can get this straight.
All the required libraries are present , all are 3.2 version.
It seems not to be a library version issue.
filezilla: symbol lookup error: filezilla: undefined symbol: _ZNK12wxDataFormateqERKS_, version WXU_3.2
There is a reference to that in the Freebsd forum… says it requires a reinstall/recompile.
also
It seems there may have been an API change in wxWidgets at 3.2.7
so maybe it is a library version issue after all
It might be, but I never had an issue with FileZilla.
Some things I learned tonight:
undefined symbol: ZNK12wxDataFormateqERKS
Well, I’m sure it is.
It seems to reference a missing or changed resource in the wxDataFormat class of the wxWidgets library.
I am not at home to look at my versions to check but looking at their web site
https://filezilla-project.org/download.php
Says for debian 10 which is not the current version. But is yours the same release number ?
They do have a forum on the site…..
At what stage does it fail ?
Can you try a different FTP application to test your connections
Just a few other items
firewall or turn firewall off,
use port forwarding if you use a VPN ?
Yesss, this one works. Thanks!
Is there any chance we could explain this?
It is not like Debian to include a package which does not work with the rest of the system?
Is the repository controlled by debian or linuxmint ?
Who updates or checks the repository ?
There are so many in the box how could they check them all.
Sadly he did not say which version number he was using and if the new install was the same or not, also if the installation cause something else to be installed which fixed the problem,…
I wonder if putting package a, then buy then c causes an error but if you do, c b a that is ok ? Dont know enough about package management and extra bits it adds.
You can learn stuff the easy way or the hard way, seems like you sadly learned them the hard method.
I‘m more of the anti backup type, always just do fsck and cp. Maybe that I‘m also getting a symbol lookup error when starting Timeshift also has something to do with that.
Meanwhile, I know, that the LMDE/Debian folks are not responsible for my issue.
LMDE7 is shipped with a runtime version of wxWidgets, this was, IIRC, always the case. On my machines, I develop software using wxWidgets, for this I installed self-compiled versions 3.2 and 3.3. My libs live in /usr/local/lib, my LD_LIBRARY_PATH points to that directory, so that all my .so can be found.
After the dist-upgrade replaced FileZilla with a newer version, it didn’t match with my own libs. In the past never been a problem. Obviously, the new filezilla requested a new item that was not added by my libs config. Bingo!
As verification, I installed FileZilla in a completely naked live version of LMDE7, no problem.
What I don’t understand: after removing LD_LIBRARY_PATH and running ldconfig, FileZilla still crashed, even if it should use the official runtime libs then.
For now, I prefer not to compile my libs with a changed config. Maybe later.
The version that @callpaul.eu recommended works, as its tarball contains all required so’s.
I’m looking forward to the next upcoming hassle. 
I don’t care about numbers here. But I expect that an upgraded app finally is executable in the neww environment. Otherwise there should be a compatiblity warning or such.