It is more than 1 month I cannot lounch properly Tropy. Program window appear, and then after several seconds the window gets gray and program crashes. The log is attached.
I"m runing Arch Linux, system is often updated. The crashes happen at Lenovo notebook and also powerfull desctop PC. I tried local Tropy install and also AppImage, tried different versions, incl. Tropy-1.16.3-beta.2-x86_64.AppImage.
Thanks in advance for any suggestions!
tropy.log (4.6 KB)
Does it also crash using the tropy package from the AUR?
On desctop PC I managed to install, but again crashed. Just now tried to install on the notebook and it was not successful: "==> Starting build()…
==> ERROR: A failure occurred in build().
Aborting…
→ error making: tropy-exit status 4
→ Failed to install the following packages. Manual intervention is required:
tropy - exit status 4
“”
Will check later on the desctop. Thanks!
Solved!
Installed from the source, after cloning github repo. Followed advices of poe.com:
For developers, here are the warnings at the time of installation:
messages > npm install
npm warn Unknown project config “sharp_libvips_binary_host”. This will stop working in the next major version of npm.
npm warn Unknown project config “sharp_install_force”. This will stop working in the next major version of npm.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated boolean@3.2.0: Package no longer supported. Contact Support at npm | Support for more info.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
added 1183 packages, and audited 1184 packages in 16s
231 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
messages > npm run build
npm warn Unknown project config “sharp_libvips_binary_host”. This will stop working in the next major version of npm.
npm warn Unknown project config “sharp_install_force”. This will stop working in the next major version of npm.
tropy@1.16.3-beta.2 prebuild
npm run clean && npm run rollup
npm warn Unknown env config “sharp-install-force”. This will stop working in the next major version of npm.
npm warn Unknown env config “sharp-libvips-binary-host”. This will stop working in the next major version of npm.
npm warn Unknown project config “sharp_libvips_binary_host”. This will stop working in the next major version of npm.
npm warn Unknown project config “sharp_install_force”. This will stop working in the next major version of npm.
tropy@1.16.3-beta.2 clean
shx rm -rf coverage doc dist lib .nyc_output npm-debug.log internal mocha
npm warn Unknown env config “sharp-install-force”. This will stop working in the next major version of npm.
npm warn Unknown env config “sharp-libvips-binary-host”. This will stop working in the next major version of npm.
npm warn Unknown project config “sharp_libvips_binary_host”. This will stop working in the next major version of npm.
npm warn Unknown project config “sharp_install_force”. This will stop working in the next major version of npm.
Thanks for this nice software!
It sounds like there was a compatibility issue with the locally installed libvips. Instead of a custom build, I would recommend installing Tropy via Flatpak, because this will run isolated from the system libvips.