Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
AppImage fails on Ubuntu 18.04
Executing AppImage 3.11.4 on Ubuntu 18.04 fails:
~/Downloads$ ./Patchwork-3.11.4-linux-x86_64.AppImage installed: X-AppImage-BuildId=c5ceb290-e2f6-11a8-07c2-b1ba5ffda287 image: X-AppImage-BuildId=c5ceb290-e2f6-11a8-07c2-b1ba5ffda287 /tmp/.mount_: symbol lookup error: /tmp/.mount_: undefined symbol: udata_setCommonData_59
~$ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic
Cloning the github repo, npm install and npm start work just fine on this system.
- weixin_39875842 4月前点赞 评论 复制链接分享
I'm not sure, honestly. I've pushed some new prereleases, can you confirm whether this problem is resolved? Thanks!点赞 评论 复制链接分享
- weixin_39783149 4月前
I'm having a similar error with
symbol lookup error: /tmp/.org.chromium.Chromium.85AHMT: undefined symbol: crypto_core_ed25519_scalarbytes
Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic点赞 评论 复制链接分享
I've just pushed a fix that should resolve this, could you let me know if it's working for you in the latest prereleases (or
master)? Thanks!点赞 评论 复制链接分享
- weixin_39875842 4月前
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?点赞 评论 复制链接分享
Hey , sorry to hear that you're having problems with Patchwork right now.
I'm not super familiar with debugging AppImages on Linux, but after searching the web for "undefined symbol: udata_setCommonData_59" it looks like this may be a common issue with other Electron applications.
Can you confirm that your packages are up-to-date with
apt-get update && apt-get dist-upgrade?点赞 评论 复制链接分享
Yes they are up to date, might need a reboot, but the kernel being a few days old should not be an issue.
I am not quite sure how to get more information from the AppImage.. to my understanding it is a static binary/self contained environment so it can't be missing dependencies..点赞 评论 复制链接分享
Reboot didn't help, as expected..点赞 评论 复制链接分享
- weixin_39679091 4月前
As a point of reference my laptop is running 18.04 as well and is working fine with that appImage. In case it helps isolate the issue here's the list of packages I have installed(
apt list --installed) packages.txt点赞 评论 复制链接分享
Are you using the same desktop environment and/or display manager? I'm trying to come up with which other variables might affect this.点赞 评论 复制链接分享
- weixin_39679091 4月前
I'm running xubuntu/xfce with the lightdm desktop manager.点赞 评论 复制链接分享
Mmh.. my system was recently upgraded from 16.04 with unity to 18.04 using do-release-upgrade. I also tried installing the xubuntu-desktop meta package. This didn't help.. For the time being it's okay for me to manually start patchwork from the git repo and with
npm startbut for less techy people this might be more problematic and a showstopper.点赞 评论 复制链接分享
Okay pinned it down to libnode.so .. There existed various versions (apt, node repo, various electron apps) from this library on my system. Patchwork picked up the wrong one. After moving the AppImage to a different folder and removing some of the libs it starts up. Shouldn't the AppImage be selfcontained and override any lib versions already present on the system?点赞 评论 复制链接分享