Arch Linux User Repository

==> Retrieving sources...
-> Found rustdesk-1.4.1-x86_64.pkg.tar.zst
==> Validating source_x86_64 files with sha256sums...
rustdesk-1.4.1-x86_64.pkg.tar.zst ... FAILED
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'rustdesk-bin-1.4.1-2': 
error: packages failed to build: rustdesk-bin-1.4.1-2

@markginter31: I tested connecting to a remote machine using an ID, a public IPv6, and a (NAT'd) IPv4, and it worked in all cases.

Both local and remote machines are on the latest 1.4.1. If you experience issues, I'd recommend you downgrade to 1.4.0 until 1.4.1 is released by upstream as stable.

It was my error to update the PKGBUILD to 1.4.1 before upstream officially release this version. I'll make sure that the package is not updated before the upstream announces the new version in the future :)

Installed the latest (1.4.1-2) using yay -- but now if I try to connect over the internet it just sits on the "connecting" screen without actually connecting. I can use the ip directly over VPN -- but it had worked previously over the internet.

Just tested the connection from my Android phone -- it still works fine on the same network, out over the internet to the remote machine. It's just my Arch setup on my laptop that's being contrary :)

@khoyo: Oops, I, in fact, updated this package too early. I've updated the checksums and bumped the pkgrel since the upstream made actual changes.

@Davius: The error in the .install script has been fixed with 1.4.1-1.

Regarding the automatic restart, my standard take is to not automatically restart the services, and let the user handle the restart (like most packages on Arch Linux).

However, as it was reported that Rustdesk crashes during the update, and can make a remote system inaccessible (which is critical if the update is made remotely through Rustdesk itself), I made an exception here, and restart the service automatically.

FYI, there are a few packages in core/extra that also automatically restart their services for the same reason.

As 1.4.1 is currently in its pre-release stage, it still gets updated, which breaks the checksum.

Hi @Zoddo

(1/1) réinstallation rustdesk-bin                                [####################################] 100%
==> NOTE: The RustDesk daemon must be started for RustDesk to work.
==> NOTE: To start it automatically on boot, run 'sudo systemctl enable --now rustdesk' in a terminal.
erreur : la commande n’a pas pu être exécutée correctement

I've got an error, because the service is not launched on my system. It's quite confusionnal. Maybe if the service is not running, propose to run it ? Or as archlinux do, let the user manage the service part.

Also, the Antiz Arch-update tool can restart the services now for the users. I'm not sure if it's a good way to restart the service by default in the pkg.

Best Regards.

@JoaoMachado: Sorry for that. The service will now be restarted automatically (if already started) after the upgrade.

I installed rustdesk-bin on a remote computer a few weeks ago. Just tried to update the remote device and the Rustdesk service was not restarted during the updating of packages.

Had to drive 40 minutes to manually restart the rustdesk service.

I know we discussed this issue, but to not have the service restart in the middle of a remote update is no bueno, I thought this issue was resolved?

wereii maybe make systemctl unmask rustdesk.service ?

I am having problems enabling the systemd service.

If I do

sudo systemctl enable --now rustdesk

it does not start and the unit is disabled again.
Running rustdesk --service manually as non-root gives me policykit terminal login prompts for stuff like dbus systemd unit manipulation so it literally just disables itself.