🐞 Bug `filezilla` won't launch

[VenomousSteam81]

Describe the bug filezilla won't launch because of a different error (this is not like #10479)

To Reproduce Steps to reproduce the behavior:

1. Please indicate where the command(s) were executed.

My environment was (crosh, bash or VT-2): VT-2

2. I executed the command(s) below:

     filezilla

   Output:

     filezilla: error while loading shared libraries: libgspell-1.so.2: cannot open shared object file: No such file or directory

   Expected behavior filezilla launching fine with no issues.

**System Information: Paste the output of crew sysinfo -v between the two *** below. If you cannot execute crew, display the output of cat /etc/lsb-release instead.**

---

Expand

- Architecture: `aarch64` (`armv7l`) - Processor vendor: `ARM` - User space: `32-bit` - Chromebrew Kernel version: `5.15` - Chromebrew Running in Container: `false` - Chromebrew version: `1.52.9` - Chromebrew prefix: `/usr/local` - Chromebrew libdir: `/usr/local/lib` - Last update in local repository: f9c0c199d `LLVM 19.1 (#10508) (45 minutes ago)` - OS variant: `Chrome OS` - OS version: `hana-release/R126-15886.74.0` - OS channel: `stable-channel`

---

[satmandu]

Does installing gspell help?

[VenomousSteam81]

No. It's already installed

[satmandu]

Doing this:

upx -d `which filezilla` 
lddtree `which filezilla`

Gives this:

And then

chronos@rpi51-armv7l:2.37 M126 /usr/local/lib/crew/packages (master >|SPARSE)$ crew whatprovides libwx_gtk3u_aui-3.2.so.0
wxwidgets: /usr/local/lib/libwx_gtk3u_aui-3.2.so.0
wxwidgets: /usr/local/lib/libwx_gtk3u_aui-3.2.so.0.2.1

Total found: 2
chronos@rpi51-armv7l:2.37 M126 /usr/local/lib/crew/packages (master >|SPARSE)$

Tells us that we need a rebuild of wxwidgets...

[uberhacker]

Nice sleuthing @satmandu! Looks like wxwidgets needs an update anyway. See https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.6.

[satmandu]

Nice sleuthing @satmandu! Looks like wxwidgets needs an update anyway. See https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.6.

Already building...

[satmandu]

Hopefully that PR fixes that issue...

[VenomousSteam81]

Testing now.

[VenomousSteam81]

Now we are back to square one. I'm getting the exact same output I got from #10479

[uberhacker]

@VenomousSteam81: This is working for me in multiple environments. Did you run crew update && crew upgrade?