You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A constellation of known issues in Electron appear to affect the current Linux builds of Tusk, making them unusable on Linux systems with a certain unlucky combination of library versions. I have installed Tusk 0.11.0-472 from the Debian package for amd64 architecture. This package appears to be affected, and the bug presents as immediate segmentation fault on launch. My system is Ubuntu 18.10.
I had the same issue on a different Electron-based application, which was resolved by updating to a newer release of the same package. Based on available information, I expect the reason is a new version of the included the Electron framework, and not updates internal to the application.
Please review the below issues and consider whether a new set of packages can be published with a fixed build of Electron, in order to make Electron usable to a broader range of users.
A constellation of known issues in Electron appear to affect the current Linux builds of Tusk, making them unusable on Linux systems with a certain unlucky combination of library versions. I have installed Tusk 0.11.0-472 from the Debian package for amd64 architecture. This package appears to be affected, and the bug presents as immediate segmentation fault on launch. My system is Ubuntu 18.10.
I had the same issue on a different Electron-based application, which was resolved by updating to a newer release of the same package. Based on available information, I expect the reason is a new version of the included the Electron framework, and not updates internal to the application.
Please review the below issues and consider whether a new set of packages can be published with a fixed build of Electron, in order to make Electron usable to a broader range of users.
electron/electron#13972
electron/electron#13972
Some application teams have followed a similar line by addressing the Electron issues within the internal workflow.
BoostIO/BoostNote-Legacy#2603
The text was updated successfully, but these errors were encountered: