ipfs-desktop: Taskbar icon not working

OS: Windows 10 x64
Version of IPFS Desktop: 0.30.2

Describe the bug I’m unable to right-click on the IPFS icon on the taskbar to quit the application. No menu appears. I’m only able to open the GUI with left-click!

To Reproduce Steps to reproduce the behavior:

Start IPFS
Right-click on the icon on the taskbar
Nothing happens!

Expected behavior Menu with options should appear!

Screenshots

Additional context The icon also don’t change color when I’m connected! The version 0.30.1 works fine!

combined.log error.log

Thanks

About this issue

Original URL
State: closed
Created 10 months ago
Reactions: 1
Comments: 17 (10 by maintainers)

Commits related to this issue

fix: init done fires even with lng load error i18next has some auto-magical loading of translation files that kicks off loading multiple languages (e.g. 'en', 'en-US', 'en-UK', etc.) but we don't hav... — committed to ipfs/ipfs-desktop by SgtPooki 9 months ago

Most upvoted comments

Try to change C:\Users\<USER NAME FILE>\AppData\Roaming\IPFS Desktop\config.json language to "", is was work for me.

My guess is that this is another one of those bugs in the translation configuration.

Version 0.30.0 started to cause the tray menu to function in a confusing way, and the migration function didn’t work.
Version 0.30.1 fixes the migration function, but still does not fix the tray menu language problem.
Version 0.30.2 fixes the default language(EN?) for tray menu, but use other languages cause prevent right-clicking icons.

Seems like the language system has been screwed up since version 0.30.0 #2600 FYI

yatounoneko on Sep 16, 2023

The fix is out: https://github.com/ipfs/ipfs-desktop/pull/2650. It’s a super simple fix for an odd behavior from i18next: it shows an error when it cannot find a file for a language, even if it successfully resolves to a file for that language.

SgtPooki on Oct 5, 2023

Thanks for submitting this issue @Dominiquini and thanks for providing a resolution @Azulan, this sounds like the correct assumption. IPFS-Desktop started lazy-lazy loading app-context which makes the loads much more faster and reduces the amount of initial load tasks.

However, this transition has not been as smooth as we’d hoped for, especially on the taskbar issues as testing taskbar in a cross-env fashion is hard. Taskbar was not covered with tests and hence it has seen a regression. There is an issue to tracking this.

This issue is currently not reproducible on a mac, and maybe is limited to windows only. Based on the logs you provided, looks like i18n is not initializing properly (which is not the case on a mac):

2023-09-14T03:42:11.812Z info: [ctx] getting i18n.initDone
2023-09-14T03:42:11.812Z info: [ctx] Could not find property i18n.initDone
2023-09-14T03:42:11.812Z info: [launch on startup] disabled
2023-09-14T03:42:11.823Z error: [i18n] init failed

@SgtPooki I think there is a weird race condition (on windows) where the i18n is not being initialized properly.

whizzzkid on Sep 18, 2023