New to Manjaro kde. from windows.
trying to install Rustdesk for the family.
sudo pamac build rustdesk
seems to error on build vcpkg line 515.
should i wait for server to reset?
Is this a temporary problem?
Install rustdesk-bin package. In AUR you will find precompiled versions of some software with the suffix -bin. You can usually try them first before using the package that must be compiled. Itās much easier and much faster.
5 Likes
Also, please do not use sudo with pamac.
Pamac uses polkit for authentication, and will prompt you for your password when required.
5 Likes
As suggested, use rustdesk-bin instead ā this is a binary release assembled on-the-fly rather than being built directly from source ā the result is less overhead and potentially less difficulty installing the application.
pamac build rustdesk-bin
The current rustdesk-bin seems to build without issue, and starts as expected on Plasma.
The usual warnings apply; that use of the AUR is not officially supported by either Manjaro or Arch Linux, and that, if used, switching to the Manjaro Unstable branch (which is the closest to Arch Stable branch) is generally recommended.
Please observe Manjaro forum guidelines when posting code or command output (see links below).
Regards.
What follows is from a standard template.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.
Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:
Required Reading
Highly Recommended
Work with us, not against us
It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.
Simply waiting for others to ask you questions is counter-productive ā typically, nobody has a 
at their disposal ā and your clear, concise and accurate input is often relied upon in order to help you.
Please help others to make informed suggestions based on information you provide.
System Information
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes itās better to ask your system directly; 
Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:
Suggested inxi command (use either):
inxi -zv8 |
(short-form) |
inxi --filter --verbosity=8 |
(long-form) |
| inxi man pages | (manual) |
If running `inxi` within a `chroot` environment
- Add
--color=0to the long-form command, orā¦ - Change the short-form command to
inxi -zv8c0
Your privacy is respected
Update Announcements
Technical Resources
Make sure you have base-devel installed.
1 Like
base-devel is downloaded and installed if not already present in the system.
The AUR isnāt something for new users coming straight from Windows. If you intend to build from sources, you can find the build instructions on Rustdeskās Github page. You may compare this with the PKGBUILD you tried from the AUR.
But on the Github page you also find that Rustdesk is provided on Flathub, so you can open Discover, search for Rustdesk and install it from there. In contrast to some recommendations here, i personally avoid to install executables from the AUR. This isnāt what the AUR is for, and more importantly youāll have no idea of how this executable was build (is it malicious? well of course if you build from source you should check the PKGBUILD, too, but if this merely downloads a executable how to check it? Does it work on your system as it wasnāt build on your system - well sometimes, sometimes not. In the end you realize if the software isnāt part of your distro then the best way to install 3rd party executables is via Flatpack, Snap, maybe Docker etc).
1 Like
On Manjaro?
1 Like
Sourcing applications via the AUR is never a recommendation.
It is, however, an available option ā subject to caveats already indicated, including the recommendation to switch to the Unstable branch if AUR really must be used.
Suggesting that new users coming straight from Windows build an application manually from source is also fraught with the potential for unforeseen problems.
With respect rustdesk and rustdesk-bin ā both have been continually maintained for at least the past four years, despite the scare mongering.
Considering that the GitHub source (via AUR) failed to build (rustdesk), then the binary package rustdesk-bin is the obvious choice (this is what I personally use), if the AUR is to be used at all.
Install RustDesk binary (-bin) via the AUR:
pamac build rustdesk-bin
- (
sudoshould never be used withpamac)
RustDesk isnāt provided by the official Manjaro repositories, which is unfortunate, as the repoās are the most reliable and convenient source for software on Manjaro.
- Manjaro repoās should generally be the first choice.
As mentioned, the containerised flatpak applications are a valid option, despite possible inconveniences;
Install RustDesk as a flatpak with:
flatpak install rustdesk
Snap containerised applications should probably be avoided.
Others may have lengthy opinions on Snap which will likely better support this stance. 
Regards.
Edit:-
I almost forgot to mention that Wayland support for RustDesk is currently experimental, and X11 is recommended if unattended access is required.
This applies no matter how itās installed.
Edit2:- Typoās
1 Like
A standard warning I usually include whenever discover is mentioned in regard to installing applications on Manjaro:
Caution: Arch and Manjaro users should not use discover, because it uses packagekit, which will throw your permissions wide open.
Note that you can remove packagekit & packagekit-qt6 from your system, as they are only optional dependencies for discover:
Output of pamac info discover
pamac info discover
Name : discover
Version : 6.5.3-1
Description : KDE and Plasma resources management GUI
URL : https://apps.kde.org/discover/
Licenses : LGPL-2.0-or-later
Repository : extra
Installed Size : 7.1 MB
Groups : plasma
Depends On : appstream-qt archlinux-appstream-data attica discount gcc-libs glib2 glibc kcmutils kconfig
kcoreaddons kcrash kdbusaddons ki18n kiconthemes kidletime kio kirigami kirigami-addons
kjobwidgets knewstuff knotifications kservice kstatusnotifieritem kuserfeedback kwidgetsaddons
kwindowsystem purpose qcoro qqc2-desktop-style qt6-base qt6-declarative qt6-webview
Optional Dependencies : flatpak: Flatpak packages support
fwupd: firmware update support [Installed]
packagekit-qt6: to manage packages from Arch Linux repositories (not recommended, use at your own risk)
Provides : --
Replaces : --
Conflicts With : --
Packager : Tomaz Canabrava <tcanabrava@archlinux.org>
Build Date : Wed 19 Nov 2025 00:36:41
Validated By : MD5 Sum SHA-256 Sum Signature
Discover will then not be able to install system software, but will still be able to install, remove and update Plasma add-ons such as themes, cursors, plasmoids etc.
You may still be able to install flatpaks via discover though. Iām not 100% sure about that as I donāt use discover or flatpak on my system.
3 Likes
Just donāt use Discover.
5 Likes
Yes - it work perfectly fine - just donāt use the option dependency that integrates to libalpm.
As I recall it, the Summit edition uses Discover to manage flatpak applications.
rustdesk is also available as a pacman package (pkg.zst) from rustdseskās github releases page as one of the assets.
1 Like
Exactly, i overlooked this. And perhaps the ābin packageā on AUR is merely a download wrapper for this, which is the exceptional case for when one can try such an executable from the AUR. But one has to check such things beforehand and still using Flatpaks if officially provided should be better and there is no issue using Discover as GUI frontend for this purpose. (The OP mentioned using Manjaro KDE.)
(There are systems for distributing executables and AUR isnāt such a system.)
Well using some AUR helper is just a shortcut for manually building and taking this shortcut isnāt recommended even less so if you arenāt familiar with the underlying build process. So in case the OP reads a bit about this in the Arch wiki or on Github could increase the awareness of āoh really i just tried doing all of thisā.
The point in using the AUR at all is that a PKGBUILD is provided ā whether building from source or repackaging an existing .deb, .rpm, .appimage, .flatpak or other binary package ā which largely removes the complication of manually building from source or repackaging oneself.
Though, I agree that a modicum of common sense is needed and that checking the PKGBUILD ā at least to verify the souce ā is generally a wise habit. An āAUR helperā like pamac even provides a mechanism for that.
Fun fact: pamac itself can also be sourced via the AUR: pamac.
The AUR does not actually host any packages, only the PKGBUILD which provides the information needed to either build or repackage the source content.
A cursory look at the PKGBUILD of rustdesk-bin shows for example that .pkg.tar.zst is sourced for x86_64 and the .rpm is sourced for aarch64.
Each is automatically repackaged to support an Arch Linux (or Arch Linux based) package management system.
The OP mentioned this error when attempting to build rustdesk.
Interestingly, the error is related to the vcpkg package ā āa free and open-source C/C++ package manager maintained by Microsoft and the C++ communityā ā and not RustDesk itself.
With M$ involvement, Iām really not surprised. 
As already noted, rustdesk-bin also sourced via the AUR builds and installs without issue.
Ultimately the choice is yours, however of the methods available to install RustDesk, Iād personally suggest either rustdesk-bin via AUR or the flatpak.
Regards.
2 Likes