FZS GUI v1-5-0 doesn't show system tray icon, while v1-4-1 works

[harbinger]

Hello,

on my W11 x64 b22622-290 (23H1) (installed StartAllBack and TrueLaunchbar) FileZilla Server GUI v1-5-0 doesn't show the system tray icon even when the option is checked in the GUI's menu.

My findings:
v1-4-1 GUI shows the system tray icon correctly on the same machine,
v1-5-0 GUI when booted to Windows Safe Mode, it shows the system tray icon correctly again,
on some of my other PCs with the same configuration (1x x64, 1x arm64) the error doesn't manifest.

Could any dev fix it, please? I can set up remote debugging on the affected machine or some other coop.

Thanks. Ben

[botg]

What happens if you uninstall StartAllBack and TrueLaunchbar?

[harbinger]

It is the same. I just mentioned it, because it is visible from the screenshot.

[darekk]

sam issue on my end, the administrative GUI starts and is obviously running but I can't get to it because the tray icon is not showing at all. Any idea how this can be fixed?

[Fan_Robin]

same problem.i think i tick“enable tray icon”and“minemize to tray”,then no tray icon.i cant use it at all now.
by the way,the config lose after i install 1.50 from 1.4.1.

[oibaf]

Can you all please check the latest nighly build out? It should solve the issue.

[harbinger]

While the issue IS really fixed with Nightly_2022-07-23 and higher, from the same nighly there are 2 new errors, which didn't happen with Stable_v1-5-0.

Error1:

This can be overridden by selecting "install as service, started with windows" and not "keep existing...".

Error2:

This is confusing because this error isn't displayed with Stable_v1-5-0 or v1-4-0.

Also how to disable the warning nag pop-up on Nightly? Is the option for it in the XML?

[harbinger]

Also, where are the older Nightlies (between v1-4-0 and v1-5-0) stored?
I tried to find, with which version tray issue began.
I tried to fake URLs like:
https://filezilla-project.org/nightlies ... -setup.exe
but it doesn't work.

Also on some systems, the tray issue doesn't manifest, so maybe it is just possible to correct something in OS instead?

[oibaf]

Error 1:
this can be overridden by selecting "install as service, started with windows" and not "keep existing...".

Thanks, we'll look into that.

Error2:
This is confusing because this error isn't displayed with Stable_v1-5-0 or v1-4-0.

It's a new feature, to be released with the next version. It informs you of a limitation of the network the server is on and tells you what to do about it. The old server did the same. It should probably be a warning.

Also how to disable the warning nag pop-up on Nightly? Is the option for it in the XML?

There's no option, it's there to remind you not to treat as stable something that is unstable.

[botg]

Also, where are the older Nightlies (between v1-4-0 and v1-5-0) stored?

We don't keep older nightlies. They are ephemeral items not meant to linger.

[oibaf]

Also, where are the older Nightlies (between v1-4-0 and v1-5-0) stored?
I tried to find, with which version tray issue began.
I tried to fake URLs like:
https://filezilla-project.org/nightlies ... -setup.exe
but it doesn't work.

Nightlies are stored for 4 days: https://filezilla-project.org/nightlies_server/

We know when the issue started, thanks to your reporting we could trace it back.

Also on some systems, the tray issue doesn't manifest, so maybe it is just possible to correct something in OS instead?

It had to do with the way icons are handled on hidpi displays with a scaling factor > 100% by wxWidgets.

[harbinger]

It's a new feature, to be released with the next version. It informs you of a limitation of the network the server is on and tells you what to do about it. The old server did the same. It should probably be a warning.

By the old server do you mean v0-9-60-2 x32? Why did you drop x32 bins BTW? Will you also compile arm64 (win32) bins in the future? IMHO all dependencies (visible from files listed in the FZS directory) support arm64.

It had to do with the way icons are handled on hidpi displays with a scaling factor > 100% by wxWidgets.

OK, so basically when you change DPI scaling from 125% to 100% (or to 150%), then it works. Problem solved for me. Maybe you could re-release v1-5-0 as "silent-update" only with this fix for other people because there will be several months until v1-6-0 will arrive.

[boco]

My guess: There will be a 1.5.1.

And 32bit is not provided because that architecture is basically dead. Nearly everything is 64bit now.