Skip to content
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

script exits with error on ARM64 platform #117

Open
apisashla opened this issue Sep 6, 2023 · 2 comments
Open

script exits with error on ARM64 platform #117

apisashla opened this issue Sep 6, 2023 · 2 comments

Comments

@apisashla
Copy link

apisashla commented Sep 6, 2023

I know this hasn't been updated in a while which is fine, but in case anyone has had a similar issue and found a workaround, I'm having trouble running snap-sync on my ARM platform (Raspberry Pi 400 running EndeavourOS, an Arch derivative.) Was happy to find it packaged for aarch64 at all, but it doesn't appear to run.

After installation via yay, attempting to run the interactive script with no options and a blank btrfs-formatted usb mounted results in the following:

snap-sync version 0.7, Copyright (C) 2016-2021 Wes Barnett
snap-sync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the license for more information. 

Could not connect: No such file or directory
Exited due to error on line 163.
exit status: 1
command: sudo -u $u DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(sudo -u $u id -u)/bus notify-send -a $name "$1" "$2" --icon="dialog-$3"
bash line: 171
function name: notify

If I knew more about either btrfs or dbus I'm sure I could find a solution, but I don't. Thanks in advance!

Edit: in case it's relevant, I was accessing this pi via ssh-tunneled TigerVNC at the time.

@dcanuhe
Copy link

dcanuhe commented Oct 31, 2023

@apisashla I got the same error on archlinux, except the first part was more descriptive (didn't write it down and have fixed it since, but it said something like this):

[...] The name org.freedesktop.Notifications was not provided by any .service files
Exited due to error on line 163.
exit status: 1
command: sudo [...]
bash line: 171

I fixed it by installing a notification server.

@apisashla
Copy link
Author

@dcanuhe Thanks! I do actually have a notification server on that particular Arch device, which is why I was confused - however, I was able to run it anyway by running with the -q option, so I'd recommend that to anyone running into that problem on aarch64 device and/or EndeavourOS and/or KDE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants