New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run when installed in /usr/bin but "./" does work #48
Comments
I have no explanation what could cause this. I have not experienced this before. Ardour uses vfork() to launch xjadeo (really xjremote) as child process. That will have the same environment as the parent process and hence should just connect to the same x-window server as Ardour itself. For a 2nd opinion: Does it work when you use the binary from https://nightly.ardour.org/ (demo is fine, installs to /opt and comes with an uninstaller)? |
Probably related to the musl libc. Glibc apparently works fine. But why doesn't the static binary work either? |
didn't work
there are only 2 possibilities:
|
alright it works! just had it installed in /usr/local/bin before and didn't notice. Thanks for the help! |
I'm trying to package harvid and xjadeo for void-linux and it seems like Ardour can't start xjadeo. When running standalone it reports:
However, when executed with ./ it pops up no problem. Any Idea what could cause this?
I first suspected this to be a Problem with Wayland, however I get the same output with X (dwm).
here is the PR for both harvid and xjadeo:
void-linux/void-packages#33586
The text was updated successfully, but these errors were encountered: