
This happens every time when bringing Wire window from tray, i.e. first I close the window with X to minimize it to tray, then I click on its icon in the launcher to bring it back, and there I get the error.
If I click on the tray icon > Open Wire, there's no error.
Can repro that...
@gregor, sorry, do you mean "can" or "can't"?
Can - we opened an issue internally and will take a look.
Seems like it was introduced with Electron 1.6 :/
Are there beta versions available for each platform before the releases are published? I'd like to test them and report back to help release Wire to the mainstream users free of highly visible bugs like this one.
@anatoli26 The best option is to build the master branch, as we don't have publicly available pre-release binaries.
Yeah, I though about that, but an issue could be added in the latest build, untested by the community testers. Also, it's difficult to be building the packages frequently (like every day or 2) for the community testers and this way some parts of the new functionality may not receive enough usage. Also, the iOS version can't be tested by the community this way.
Would it be reasonable to introduce some staging period for the release builds and announce them as such? And enroll testers for beta versions of the iOS builds?
@anatoli26 We will start using the releases section more and possible link there to the pre-release binaries. Would that work?
Sure, it would be great! If we (the Wire community enthusiasts) could somehow receive the news that a new pre-release binary is available, that would be enough.
It would be useful to have some channel for this type of single and bi-directional communications, in this case for the community developers & testers (like what we have discussed in another issue where you mentioned Medium).
I can reproduce this issue on my laptop. Here is my set up
OS: Debian Sid
DE: Gnome Shell
When I first launch Wire it loads with no issue. If I close then launch from the Gnome System Tray then the error does not show up If I launch the app from the panel or after searching for the app that error pops up. If I close the app on the Tray then I can launch from the panel with no issue. It looks like if the app is running on background that to relaunch it from the panel causes an error.
Thanks for reporting. This is a known issue with Electron 1.6.1 found in 2.11.2722. We downgraded to the older version 1.4.15 of Electron again and released 2.12.2729.
I can reproduce on Ubuntu Gnome 16.04 LTS. The error does not pop up if Wire is launched manually it seems, but it does if Wire > "Launch Wire on Startup" is selected.
Can it be related to https://github.com/electron/electron/issues/4733 ?
Update:
I thought my system was updated. I installed the 64bit .deb-version, should not updates be available by running sudo apt update && sudo apt upgrade? I had to download from the website to update.
The above system was running Wire 2.11.2722, I cannot reproduce on Wire 2.12.2729.
I think we can close this issue now..
Closing it as it looks like it's fixed in the 2.12.2729
The issue still persists in electron 1.6.2. We are tracking it - but for now version starting from 2.13.2730 will again exhibit this problem.
Just installed Wire from PPA on Linux, seeing it again. Is there absolutely no fix for this in the latest electron? Is this happening in other apps to? Could you please provide a link to the corresponding bug in electron?
https://github.com/electron/electron/issues/8862
Thanks for reporting. We did not keep track of this on Linux side before the release. We do have an internal ticket tracking this though linked to Windows. The underlying Electron issue has not yet been fixed but there is a workaround that we might implement for the next release.
Renaming the issue for easier discoverability.
is this now fixed? it is a little unclear reading this thread! please close if yes!
Yes it was fixed with https://github.com/wireapp/wire-desktop/pull/593
Most helpful comment
https://github.com/electron/electron/issues/8862
Thanks for reporting. We did not keep track of this on Linux side before the release. We do have an internal ticket tracking this though linked to Windows. The underlying Electron issue has not yet been fixed but there is a workaround that we might implement for the next release.