Package Details: anydesk-bin 6.2.0-2

Git Clone URL: (read-only, click to copy)
Package Base: anydesk-bin
Description: The Fast Remote Desktop Application
Upstream URL:
Keywords: anydesk desktop remote
Licenses: custom
Conflicts: anydesk
Provides: anydesk
Replaces: anydesk-debian
Submitter: D3SOX
Maintainer: D3SOX (severach)
Last Packager: D3SOX
Votes: 187
Popularity: 2.61
First Submitted: 2020-02-26 00:13 (UTC)
Last Updated: 2022-06-24 18:26 (UTC)

Latest Comments

PhotonX commented on 2022-08-09 15:41 (UTC)

Thanks, looks like it was a temporary issue with Anydesk servers which is fixed now:

D3SOX commented on 2022-08-09 13:35 (UTC)

@PhotonX I just built the package successfully, make sure your system clock is correct

PhotonX commented on 2022-08-09 13:29 (UTC)

Is it just me, or does the Anydesk download server really have an expired SSL certificate right now?

D3SOX commented on 2022-08-03 15:13 (UTC)

@k0r0ng I found and I'm fairly certain that there will never be a source-based package. So actually yes, but I also think it's okay the way it is right now

k0r0ng commented on 2022-08-03 15:07 (UTC)

Since AnyDesk is proprietary software, shouldn't this package be named anydesk instead of anydesk-bin?

D3SOX commented on 2022-07-25 07:03 (UTC)

@ihipop Can you test if this happens on a Debian-based distro with the official deb? (You can use a live system for convenience) Because as I said I don't believe it has something to do with packaging. If it still happens with that setup then I think your only option is to contact the AnyDesk Linux team.

ihipop commented on 2022-07-25 06:57 (UTC)


I already have these value settled ,other app works well excepted anydesk 6.2 which is working well before update

m8D2 commented on 2022-07-21 22:58 (UTC)

For those of you who use X11 autologin and yet Anydesk still reporting "Anydesk remote server display not supported e.g Wayland"

Try this:

Add "type=x11" to /etc/pam.d/system-login:

-session optional type=x11


D3SOX commented on 2022-06-27 05:50 (UTC) (edited on 2022-06-27 05:50 (UTC) by D3SOX)

@ihipop I don't think it's a packaging issue per se. You can try out setting one of these

ihipop commented on 2022-06-27 04:56 (UTC)

after upgrade to 6.2, I can not have a scaled UI on hidpi screen The UI looks so tiny

nursoda commented on 2022-06-11 23:12 (UTC)

@boustanihani: Works fine here!?

boustanihani commented on 2022-06-11 19:11 (UTC)

Error on Manjaro-Gnome: Could not connect to Anydesk network (ssl_14094415)

Could someone update this package :)

D3SOX commented on 2021-09-27 18:27 (UTC)

@jgmdev Thank you I tried to build it in a clean chroot, and it seems like it doesn't install that, fixed ^^

jgmdev commented on 2021-09-27 18:20 (UTC)

libxkbfile is another required dependency

D3SOX commented on 2021-07-23 23:03 (UTC)

@Mounicq Works fine for me without. The patchelf command during build replaces it with which is provided by the pango package. How did you install it and what distro are you on?

Mounicq commented on 2021-07-23 22:23 (UTC)

anydesk-bin 6.1.1-4 anydesk: error while loading shared libraries: cannot open shared object file: No such file or directory also need pangox-compat as a dependancy.

D3SOX commented on 2021-06-28 07:16 (UTC)

@alexanberni Thanks for pointing that out. I will add it as a dependency.

alexanberni commented on 2021-06-28 06:25 (UTC)

For version 6.1.1, need install 'polkit', for fix error with this text "error loading libpolkit-gobject-1.0"

jose1711 commented on 2021-05-10 05:47 (UTC)

the idea was to give a suggestion to the user - not to edit the file directly.

D3SOX commented on 2021-05-10 05:27 (UTC)

Yes, I also think this should not be added. However, I can add a warning when the package is installed and display-manager.service is not enabled with a link to that forum thread.

amish commented on 2021-05-10 01:44 (UTC)

Package should not modify the critical PAM file or any file not owned by package itself, in anyway. Those who want the feature can do it themselves.

galvez_65 commented on 2021-05-10 01:28 (UTC)

@jose1711, what are the ramifications of adding type=x11 to pam.d/system-login? I personally think that modifying scripts like this with the post-install sounds pretty dangerous. I would prefer it not be added to the post-install. That said echoing a suggestion for the user to edit the script themselves would be ok.

jose1711 commented on 2021-05-09 20:26 (UTC)

It's quite useful to know that w/o a running login manager you might get an error trying to connect to anydesk. Solution:

I wonder if this can be added as part of post-install script.

D3SOX commented on 2021-04-29 17:28 (UTC)

@jogai It seems like AnyDesk fixed it. I moved it to the optional dependencies because AnyDesk looks kinda weird without Adwaita installed.

D3SOX commented on 2021-04-29 05:48 (UTC)

@jogai Yes, I think so.
The reason I included it is when you're using AnyDesk with a dark GTK theme the fonts are white on a light gray background. Maybe they even fixed it, I'll have to check.
I will test this later and if they didn't fix it try to use a start script that checks if the themes are installed for the desktop entry instead of editing it directly.

jogai commented on 2021-04-28 20:02 (UTC)

Would it be possible to build without gnome-themes-extra dependency?

D3SOX commented on 2021-04-16 06:43 (UTC)

@geomaster I added it. Thank you!

geomaster commented on 2021-04-16 05:45 (UTC) (edited on 2021-04-16 05:46 (UTC) by geomaster)

After update to anydesk-bin 6.1.1 found some errors

anydesk: error while loading shared libraries: cannot open shared object file: No such file or directory

Add minizip to dependencies

leinher commented on 2020-10-20 13:59 (UTC)

I'm not able to use the VPN connection with anydesk.

lightning symbol (Top right) --> VPN --> Start

VPN Status: Error: Error on TUN Device Start IP: (default) Subnet: (default)

Anyone has an idea to fix that?

Version: 5.5.6 License: free-1

OJaksch commented on 2020-07-30 05:59 (UTC)

I'm dropping this package in favor of anydesk-bin

Some years ago, when I started maintaining the first AUR package of anydesk, the binarys of anydesk-debian and anydesk-generic (anydesk-bin) were different, if I remember correctly. This isn't the case anymore so there is no further reason for two packages of the same content, but with another approach.

If somebody is interested in adopting this package, free to do so.

severach commented on 2020-07-29 19:15 (UTC)

See anydesk-bin for a pangox fix.

D3SOX commented on 2020-06-21 11:35 (UTC) (edited on 2020-06-21 11:36 (UTC) by D3SOX)

@zuzavo That's not the alias rather than a display name. The alias looks like xyz@ad and people can connect to you with it instead of using the id

pragyanone commented on 2020-06-21 11:34 (UTC) (edited on 2020-06-21 11:34 (UTC) by pragyanone)

@D3SOX OK. @zuzavo No, that doesn't help.

zuzavo commented on 2020-06-20 11:07 (UTC)

@pragyanone Settings / Privace ??

D3SOX commented on 2020-06-20 10:56 (UTC)

@pragyanone I think it's not possible in the linux version

pragyanone commented on 2020-06-20 10:55 (UTC)

How can I create an alias/username? In windows using the free version of Anydesk, creating alias/username is prompted at the first start, and which is available only once in the free version. Where is that option here in this platform?

D3SOX commented on 2020-06-06 18:37 (UTC)

@joelostblom You are correct. Thank you for mentioning that. I added it as a dependency.

joelostblom commented on 2020-06-06 18:33 (UTC)

Should lsb-release be listed as a dependency for this package? I see sh: lsb_release: command not found when running anydesk without lsb-release installed.

damian101 commented on 2020-05-29 21:16 (UTC)

To enable autostart run sudo systemctl enable anydesk.

D3SOX commented on 2020-05-16 12:44 (UTC)

I've fixed the issue with GNOME not detecting the menu entry

D3SOX commented on 2020-05-16 11:16 (UTC)

@hawaka Ok I'll investigate it in a VM. On my host with KDE everything worked perfectly. Sorry for the inconveniences.

hawaka commented on 2020-05-16 11:15 (UTC)

Whit the new edit to the PKGBUILD gnome's menu doesn't show "anydesk". I even checked in the menu editor, it's not there. It can still be run from the terminal.

Removing the edit (reverting the PKGBUILD to it's previous state) fixes this problem.

Note: Whether I had "anydesk" in an app-folder prior to the update doesn't seem to make a difference.

D3SOX commented on 2020-05-15 21:19 (UTC)

I have pushed an update which adds the gnome themes as dependency and force uses Adwaita for the AnyDesk application. This should fix issues with text being not/barely readable

D3SOX commented on 2020-05-15 06:43 (UTC)

Thank you for your feedback. This is an issue on AnyDesk's side when using a dark GTK Theme which also bugs me a little. I think I can fix it by letting this package depend on Adwaita and run the application with that theme. I think there is an environment variable to change the theme for one application but I'm not sure. I will research it later.

duckdave commented on 2020-05-15 05:46 (UTC)

I have a cosmetic issue, the font color and background a very bright so its not good readable. Anyway the app works great, thanks a lot!

ARCHologist commented on 2020-05-13 18:21 (UTC)

Works for me now too. Thanks a lot.

galvez_65 commented on 2020-05-06 21:30 (UTC)

@severach @D3SOX Wow this works great! I love this community 2 days from issue discovered to a great patch put in place to resolve the issue, plus I learned soemthing too. Thanks for maintaining this too

nursoda commented on 2020-05-06 21:03 (UTC)

@D3SOX: Absolutely! I already had withdrewn my comment when I saw that you had added the dependency already. A BIG thank you for your package support and that you strive to find the best compatible solution.

D3SOX commented on 2020-05-06 20:41 (UTC)

@nursoda It's only a make dependency so I think the current version should be fine

D3SOX commented on 2020-05-06 20:08 (UTC)

@severach Thank you very much for providing this! I did not know about patchelf and that it can do this kind of stuff.

severach commented on 2020-05-06 20:02 (UTC) (edited on 2020-05-06 20:02 (UTC) by severach)


patchelf --replace-needed '' '' "${pkgdir}/usr/bin/anydesk"

galvez_65 commented on 2020-05-06 16:09 (UTC)

@D3SOX won't disagree with it being a total and complete hack! The real solution will be for anydesk to remove it as a requirement, but that's nether here not there.

D3SOX commented on 2020-05-06 13:55 (UTC)

@galvez_65 I would also prefer not to keep pangox-compat but manjaro has not removed it from the repos and it's currently a requirement on anydesks side. The link is a very hacky solution

galvez_65 commented on 2020-05-06 13:48 (UTC)

considering pangox-compat is deprecated and considering works, I went back to the original idea is linking, but took a page form anydesk-debian and put the link in /usr/lib/anydesk, renamed anydesk to anydesk-bin and added a shellscript 'LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/anydesk /usr/lib/anydesk-bin $@'

I would prefer that we not keep pangox-compat as a dependency if we can avoid it.

just my 2 cents for what's worth

nursoda commented on 2020-05-06 04:55 (UTC)

I had anydesk-bin 5.5.5-4 installed (which worked fine if pongox-compat was uninstalled). Trying to install anydesk-bin 5.5.5-5 in that situation yields conflict with pangox-compat. Uninstalling anydesk-bin (5.5.5-4) and reinstalling (5.5.5-5) solves the conflict.

[My question: Why compile pangox-compat when the current pango 1.0 works fine? Shouldn't there rather be a detection whether is present and make sure there's a link to it?]

john3voltas commented on 2020-05-05 20:54 (UTC) (edited on 2020-05-05 20:55 (UTC) by john3voltas)

I'm on Manjaro and it was failing earlier today.
I just tried it again and it's working perfectly. Thanks to the software house for sharing this very useful tool with us and thank you @D3SOX for keeping this package for us.

zuzavo commented on 2020-05-05 15:52 (UTC) (edited on 2020-05-05 15:52 (UTC) by zuzavo)

@D3SOX pangox-compat appears today in the AUR

nebenzahl commented on 2020-05-05 12:22 (UTC)

@PocketSam @Zesko Thank you for putting the problem and the solution here. For the problem with the deprecated packages, the installation "pacaur -S anydesk-debian" solved the problem, now it is working. Just take care because now the executable that should be executed is "/usr/bin/anydesk.bin"

zuzavo commented on 2020-05-04 22:03 (UTC)

@D3SOX, Is there no chance to talk to the developer who has removed the package to try to get it back? (I have no idea how Arch developers work ...)

galvez_65 commented on 2020-05-04 12:14 (UTC)

thanks for getting on this so soon!. Ran into the issue this weekend after some orphan clean-up.

D3SOX commented on 2020-05-04 09:21 (UTC) (edited on 2020-05-04 09:32 (UTC) by D3SOX)

@Zesko Thanks for mentioning that. I haven't thought about Manjaro repos

@PocketSam You can install version 5.5.5-3 of the package until Manjaro resolves this. I provided instructions in the pinned comment

Zesko commented on 2020-05-04 09:18 (UTC) (edited on 2020-05-04 09:24 (UTC) by Zesko)

@PocketSam 'pangox-compat-0.0.2+2+gedb9e09-3' is still in the Manjaro repos, not in the Arch repos. Manjaro did not remove it. But you wait until Manjaro will remove it. Or you can install 'anydesk-debian' in AUR.

D3SOX commented on 2020-05-04 09:01 (UTC) (edited on 2020-05-05 12:26 (UTC) by D3SOX)

@PocketSam I don't know much about pacaur but can you try a clean build? You might consider using yay or trizen. You can remove pangox-compat from your system since it's no longer in the repositories

PocketSam commented on 2020-05-04 08:59 (UTC)

For some reason I can't install package. pacaur installs pangox-compat which conflicts with anydesk-bin.

$ LC_ALL=C pacaur -a -S anydesk-bin :: resolving dependencies... :: looking for inter-conflicts...

AUR Packages (1) anydesk-bin-5.5.5-4
Repo Packages (2) gtkglext-1.2.0-11 pangox-compat-0.0.2+2+gedb9e09-3

Repo Download Size: 0.00 MiB Repo Installed Size: 1.68 MiB

:: Proceed with installation? [Y/n]

ik_5 commented on 2020-05-04 06:37 (UTC)

Updated the package and now it works well for me.

Thank you very much

kelepiradam commented on 2020-05-04 05:43 (UTC) (edited on 2020-05-04 06:41 (UTC) by kelepiradam)

If anyone already has anydesk-bin 5.5.5-2 installed then removing pango related conflicts and the workaround from the build file enables proper installation of 5.5.5-4 over 5.5.5-2 and anydesk continues to work fine. I will use this workaround until a proper solution comes for pango.

galvez_65 commented on 2020-05-04 02:20 (UTC)

Anydesk is failing to load because it can't find pangox, which was removed the repos 2 days ago. I still had it in my cache so I reinstalled it, but its an obsolete dependency so I hope anydesk fixes this.

Zesko commented on 2020-05-03 17:50 (UTC)

I have the same issue today. The solution is to install 'anydesk-debian' AUR package.

D3SOX commented on 2020-05-03 17:18 (UTC) (edited on 2020-05-04 13:37 (UTC) by D3SOX)

@zuzavo Yes, generally speaking it's a bad idea but currently the pangox-compat package is not there so I added the symlink to the package. It's an ancient library but nevertheless I don't know why it was removed

zuzavo commented on 2020-05-03 17:04 (UTC)

I've read in the forums that link and change the names of the libs isn't a good idea. Soon or late the whole thing will break in any update. (related to another issue...)

D3SOX commented on 2020-05-03 16:16 (UTC) (edited on 2020-05-04 09:31 (UTC) by D3SOX)

For Manjaro users:

You can install version 5.5.5-3 of the package until Manjaro also removes pangox-compat

mkdir anydesk-bin && cd anydesk-bin && curl -o PKGBUILD && makepkg -rsi

For Arch users:

It seems that the pangox-compat package has been removed from the repositories. (And I was not notified before removing it, although I maintain a package which depends on it) (

I added a workaround to the package that adds a symlink for which seems to work. (If anybody has a better solution please tell me!)

nursoda commented on 2020-05-03 13:55 (UTC)

I did not have pangox-compat nor pango-anydesk installed, updated to latest anydesk-bin and could not start it due to

anydesk: error while loading shared libraries: cannot open shared object file: No such file or directory

As proposed by israuor, symlinking the "missing" shared object solved it:

sudo -i cd /usr/lib ln -s

My question is only how the package could avoid that manual interaction.

D3SOX commented on 2020-05-03 10:35 (UTC)

My guess is that the the anydesk pango compat package did leave traces. I'm adding it to the conflicts

ik_5 commented on 2020-05-03 09:04 (UTC)

Like @israuor I also get the same error. I removed pango-anydesk and anydesk-bin and reinstalled them at the same order, and it is still happening.

Looking at libpangox libraries I do have on my machine:

/usr/lib/ /usr/lib/ /usr/lib/ /usr/lib32/ /usr/lib32/ /usr/lib32/ /usr/share/anydesk/files/pango-1.43.0-2/ /usr/share/anydesk/files/pango-1.43.0-2/ /usr/share/anydesk/files/pango-1.43.0-2/

israuor commented on 2020-05-03 05:55 (UTC) (edited on 2020-05-03 05:56 (UTC) by israuor)

when starting the executable I get following error:

'' anydesk: error while loading shared libraries: cannot open shared object file: No such file or directory

Using archlinux with xfce and also gnome. Am I missing something?

PeXArtZ commented on 2020-05-02 11:50 (UTC)

After switching from anydesk-debian to anydesk-bin it needs a lot of time to start. Any reasons and fixes for this?

devourer commented on 2020-05-02 10:50 (UTC)

Since the pangox-compat dependency has been removed, I had to create a link in /usr/lib in order to get the latest update running, like so: sudo ln -s

Brebro commented on 2020-04-26 19:47 (UTC)

For some reason I am able to connect to my phone but not other computers. Tried using both -bin and -debian and both had the same issue (on 5.5.4 and 5.5.5). When connecting to another PC that has a set password it asks for the password 3 times before disconnecting saying "Connection closed". If anyone has had this issue before please let me know. Thanks!

ARCHologist commented on 2020-04-26 17:04 (UTC)

@D3SOX On my laptop the anydesk-bin package works. So it has something to do with my PC and not your package. Perhaps some dependency in a wrong version. I will see if I can find out.

ARCHologist commented on 2020-04-25 17:06 (UTC)

Since I switched to anydesk-bin (5.5.5-2) I can't connect to the anydesk server anymore. After downgrading to 5.5.1-2 from my yay cache it works again. I'm not sure if it is a problem of the latest anydesk version or of the anydesk-bin package. Anyone else having this problem?

D3SOX commented on 2020-03-02 17:59 (UTC)

@termuellinator Thank you for your feedback. You are right, I forgot to add the icon to the package. I have now added the icon and the license to the package.

termuellinator commented on 2020-03-02 17:15 (UTC)

it seems the anydesk icon is missing - it is correctly named in the .desktop file, but not present in /usr/share/pixmaps.

I'd think adding install -Dm 644 "${srcdir}/anydesk-${pkgver}/icons/hicolor/scalable/apps/anydesk.svg" "${pkgdir}/usr/share/pixmaps/anydesk.svg"

should do the trick?

D3SOX commented on 2020-03-01 23:45 (UTC)

@jpegxguy AnyDesk offers Generic Linux and Debian packages. The previous 'anydesk' AUR package used the deb package to build the arch package. I had some bugs with the package and it also needs an older pango version so I created this new package and we decided to offer both packages

jpegxguy commented on 2020-03-01 23:39 (UTC)

What's the point of the debian version?

D3SOX commented on 2020-03-01 16:59 (UTC)

@SpotlightKid I added it to the conflicts list. The old 'anydesk' package is still there. It moved to 'anydesk-debian'. This package is built using the AnyDesk generic Linux packages and the 'anydesk-debian' package using the deb files.

SpotlightKid commented on 2020-03-01 16:47 (UTC) (edited on 2020-03-01 16:48 (UTC) by SpotlightKid)

Can you add 'anydesk' to provides/conflicts, please? I had installed that package before it disappeared from AUR.

galvez_65 commented on 2020-02-20 14:12 (UTC)

Thank you the new dependency fix is working great! I just removed the flatpak version of Anydesk and am back to using this package

FredBezies commented on 2020-02-18 08:36 (UTC)

You have to remove Anydesk, install pango-anydesk and reinstall anydesk once again.

pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)
pango-anydesk: /usr/share/anydesk/files/pango-1.43.0-2/ exists in filesystem (owned by anydesk)

Marc.2377 commented on 2020-01-22 21:30 (UTC) (edited on 2020-01-22 21:31 (UTC) by Marc.2377)

Thanks for the 5.5.1-2 package, your strategy works great. However, to minimize concerns regarding the blob files, you could pull the previous package from the official Arch Linux archive ( and use that. This could be done two ways: either distribute the necessary files and check hashes during makepkg, or include logic to pull them in PKGBUILD.

oislone commented on 2020-01-09 11:57 (UTC)

i new install manjaro and anydesk. host can connect guest, but screen no refresh. i remove manjaro video-linux. now is fine.

rrprabhu commented on 2020-01-07 23:36 (UTC)

Using Manjaro arch. Confirmed that incoming connections were a blank screen Solution was to downgrade pango to 1:1.43.0 as per below inputs Fixed the problem and was able to do incoming connections into the box

guynamed_rob commented on 2019-12-30 13:40 (UTC) (edited on 2019-12-30 14:04 (UTC) by guynamed_rob)

Followed @2dorf4u advice and downgraded pango. Works for anydesk, HOWEVER.

It broke the manjaro xfce file manager. So I had to upgrade pango again.

galvez_65 commented on 2019-12-12 01:16 (UTC)

I just tried the flatpak 5.5.1 version on Arch with the Gnome DE and it's working as expected. Don't know if its KDE or Manjaro

giswqs commented on 2019-12-11 16:53 (UTC)

I have been using the flatpak version for several months now. It has been working fine now until today when I updated Manjaro KDE ([Stable Update] 2019-12-10). Now when I double click to connect a remote desktop, AnyDesk disappears but nothing happens.

2dorf4u commented on 2019-11-18 15:40 (UTC)

@ggnoredo I don't think there will be any permanent solution until the Anydesk developers themselves run into this problem with the recent versions of pango and are forced to fix it. Right now they seem to be targeting Ubuntu LTS 18.04, so it may be a loooong time until that happens.

yiufung commented on 2019-11-18 14:31 (UTC)

I swap my capslock and left ctrl using Xmodmap, but Anydesk seems to be overwriting my settings. Is there anyway to avoid it?

galvez_65 commented on 2019-11-16 20:09 (UTC)

I'm still using the flatpak version because the native install is still not working. 2dorf4u says dongrading pango fixes the issue

ggnoredo commented on 2019-11-16 19:34 (UTC)

no update on blank incoming connection dialog window?

serjflint commented on 2019-10-29 13:59 (UTC)

Have the same problem with blank unresponding windows on incoming connections. The process just hangs and eats CPU. Flatpak version doesn't start at all. Solution from @2dorf4u by downgrading pango to 1:1.43.0-2 solved the problem. The system is Manjaro Kernel 5.3.7 KDE 5.17.1

linuxyz commented on 2019-10-26 06:34 (UTC) (edited on 2019-10-26 06:35 (UTC) by linuxyz)

I'm still using the @2dorf4u's solution since that's the only way to get AnyDesk working without the black screen bug.

2dorf4u commented on 2019-09-26 20:48 (UTC) (edited on 2019-09-26 20:51 (UTC) by 2dorf4u)

I was having the same problem with the empty/frozen incoming session window.

I did a bit of testing based on the hints by @johannvonperfect below and found that the problem is caused by pango, starting from version 1:1.44-1.

I was able to fix it by downgrading pango to 1:1.43.0-2.

lewis2e commented on 2019-09-25 18:05 (UTC)

I get the same "empty window problem" that everyone else is getting. Using KDE.

jc-aur commented on 2019-09-18 16:23 (UTC) (edited on 2019-09-18 16:23 (UTC) by jc-aur)

Tried the most recent version, doesn't work on me either, same empty windwow error. Tried the flatpak: it works. May be useful to track what dependency may be missing.

galvez_65 commented on 2019-09-06 15:27 (UTC)

being a GTK incomparability would explain why the flatpak version works and the native one does not. Hopefully anydesk will fix this upstream

heavysink commented on 2019-09-06 13:35 (UTC) (edited on 2019-09-06 13:36 (UTC) by heavysink)

@erkana @galvez_65 Having the same problem with cinnamon, new window on the remote site but empty. However LXQT does not have such problem. So I suspect there is something with GTK based environments.

Tried to send message to support twice but never replied...

erkana commented on 2019-09-06 06:42 (UTC)

I am using Gnome with X11 (fresh install) and when incoming connection I have the same problem described by galvez_65, there is a new window open for confirmation but it's empty.

johannvonperfect commented on 2019-08-22 19:13 (UTC)

Still having issues. Piggybacking on galvez_65 re: dependencies - I am certainly not advanced enough to know what dependencies are doing what, but going through the dependencies for this package, the only dependencies that I see that have been updated in July 2019 or later are glib2 (7.26.19 - flagged out-of-date 8.21.19), glibc (7.23.19 - flagged-out-of-date 8.1.19), and pango (8.14.19, but with frequent updates including beginning of August).

galvez_65 commented on 2019-08-14 14:42 (UTC)

I don't think the issue is specifically with the version number, it's likely some library incompatibility because the flatpak version works as expected.

johannvonperfect commented on 2019-08-14 14:06 (UTC) (edited on 2019-08-14 14:06 (UTC) by johannvonperfect)

I have been having the same problem as mihaly4 below for the past couple of weeks at this point. 5.1.1 is still the most recent version available for Linux though.

For a couple of additional data points, I am actually using Manjaro (before the mandatory gtfo noob reply, I'M SORRY) and I am trying to connect from a Windows 10 machine. The most recent version for Windows is 5.2.2, so it is possible that the problem was introduced somewhere over there. I have a support ticket in with them as well.

mihaly4 commented on 2019-08-14 06:33 (UTC)

Recent updates broke unattended access. A remote connection attempt fails with an error "desk_rt_ipc_error".

galvez_65 commented on 2019-08-12 12:44 (UTC)

Some recent update is preventing the anydesk remote control confirmation window from showing up. When a user requests remote access a white box pops up with no way to confirm or deny access. Not sure when this became an issue because I had not tried to grant remote access to my arch machine in quite some some. The flatpak version of anydesk works as expected so it has to be an dependency issues with arch.

OJaksch commented on 2019-06-13 15:37 (UTC)

Alas, the first time I updated a package and did no install - and then it happens that the original package has a bug in the permissions of its subfolders.

Now fixed. Mea culpa!

theaifam5 commented on 2019-06-13 14:58 (UTC)

Please fix it:

warning: directory permissions differ on /usr/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/bin/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/anydesk/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/anydesk/files/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/applications/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/pixmaps/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/polkit-1/ filesystem: 755 package: 700 warning: directory permissions differ on /usr/share/polkit-1/actions/ filesystem: 755 package: 700

itsizzy commented on 2019-03-11 16:01 (UTC)

@ibraheemmoosa are you by any chance using Wayland instead of X? If yes, that's not supported by the upstream/vendor. You'll have to change to an X11 session to use Anydesk...

OJaksch commented on 2019-02-17 11:09 (UTC)

@ibraheemmoosa Maybe you found a bug in AnyDesk or a broken/missing dependency in my package as other users are reporting this too:

Please file your problem direct to AnyDesk at ; they're are friendly and helpful.

ibraheemmoosa commented on 2019-02-17 04:19 (UTC)

I am getting this error when I try to connect to a remote computer. "terminate called after throwing an instance of 'base::invalid_argument_exception_t'". I have tested with an Ubuntu machine and an Android phone. I am running Gnome in Arch.

esa1975 commented on 2019-02-02 16:07 (UTC)

@szsong @nicolehopperBBY - Disabling the option 'Transmit hotkeys' under Settings - Display seems to fix it for me after experiencing the same issue. FWIW, I have used this same version on Linux Mint 19.1 and did not experience this issue.

szsong commented on 2019-01-04 07:40 (UTC)

@nicolehopperB8Y I'm having similar issue on KDE. When I press "shift + ," the remote side CAN see "<", but if I keep holding "shift" and then press ",", the remote side see "," instead of "<".

Ctrl + c and Ctrl + v etc. works in similar way or even worse: sometimes "Ctrl+c" only functions as "c" without "Ctrl".

No idea what's causing the problem. I tried to set "ignore global shortcuts" in "Window Rules" but the issue persists.

voklav commented on 2018-12-27 00:24 (UTC) (edited on 2018-12-27 00:29 (UTC) by voklav)

@SonicoXD To work anydesk property and run in the background, type this in terminal: [wolf@wolf-pc ~]$ systemctl enable anydesk

[wolf@wolf-pc ~]$ systemctl start anydesk

Tested and worked in manjaro Xfce

nicolehopperB8Y commented on 2018-11-13 11:07 (UTC)

@OJaksch: here is the output of ldd:

I currently don't have time to try vnc now, sorry.

OJaksch commented on 2018-11-13 08:58 (UTC) (edited on 2018-11-13 09:26 (UTC) by OJaksch)

@nicolehopperB8Y: Yes, I can reproduce this. First thing is that I'd to activate keyboard mapping to "Translate" in i3/anydesk to gain use of the shift+xx combination, but the control and alt keys are somewhat "dead". Maybe it's i3's own keyboard binding? Tried vnc (not as an alternative but for further investigation)?

Can you send me the output of 'ldd /usr/bin/anydesk' please?

nicolehopperB8Y commented on 2018-11-11 04:12 (UTC)

@OJaksch: after update to the latest AUR version today, I was able to connect when using i3wm, but the keyboard is not working correctly: the modifier key doesn't work for me, i.e. when I press "shift + ," the remote side only saw "," not "<" as I expected. I can't save document by pressing Ctrl + s (which only generates s on the remote side). Can you reproduce this?

OJaksch commented on 2018-11-10 13:58 (UTC) (edited on 2018-11-10 13:59 (UTC) by OJaksch)

I'm very sorry but I can't reproduce this issue. I setup a fresh but very minimalistic arch vm with xorg-server, i3 (group), lightdm as display manager and anydesk. Within i3 I then can connect to and fully control my host and the same vice versa. I've no idea what's going wrong at your side...

OJaksch commented on 2018-11-10 12:58 (UTC)

@nicolehopperB8Y I'll try to help you i3 users for sure. Let me try to setup a arch vm with i3 to see what's going wrong and to identify potentially missing deps. I'm sure to get this baby going beneath i3 :) You can contact me directly in the meanwhile.

nicolehopperB8Y commented on 2018-11-10 12:36 (UTC) (edited on 2018-11-10 12:37 (UTC) by nicolehopperB8Y)

@OJaksch: I contacted them, and they replied as below:


thank you for your message!

AnyDesk needs a DE to work correctly. You may try to add our dependencies manually, so that it also may work with i3wm.

See here:

Freundliche Grüße / Kind regards

<name> AnyDesk Support

@OJaksch: Can you help me check if there are any missing dependencies in this AUR package? The names of those listed in anydesk support site look strange to me because archlinux doesn't have the same naming convention.

OJaksch commented on 2018-11-07 17:19 (UTC)

Very interesting that all bugs are related to i3. I'll try to reproduce this - but you can contact AnyDesk directly by also. They're very friendly and helpful.

bayi commented on 2018-11-07 17:09 (UTC) (edited on 2018-11-07 17:09 (UTC) by bayi)

hi, i also have the i3 issue with anydesk on my desktop and laptop too.

Tried the anydesk-test package, same. Tried with intel, nvidia, modeset drivers all same.

In gnome/kde it works fine, only i3 is "freezing" while trying to connect to a host with anydesk.

Seems like im missing some service that gnome/kde is running, how could i debug whats the cause of this ?

SilverMight commented on 2018-10-23 22:36 (UTC)

@nicolehopperB8Y also experiencing this on i3

commented on 2018-09-19 16:50 (UTC)

I use ratpoison as window manager and no problem.

nicolehopperB8Y commented on 2018-09-19 16:32 (UTC)

AnyDesk turns white and cpu usage keeps increasing when using this package in i3wm, haven't tested in another wm/de though.

SonicoXD commented on 2018-07-31 00:22 (UTC)

@OJaksch thank you! At the end I used a silly workaround. I minimized the program with AllTray and hid AnyDesk's original icon so I would only get the AllTray one. However, AnyDesk was not working if the screen was locked (using light-locker). Is this normal?

OJaksch commented on 2018-07-09 09:39 (UTC)

@churro: I'm very sorry, but this is not my responsibility.

But feel free to contact AnyDesk directly at - they're very friendly and helpful.

OJaksch commented on 2018-07-09 09:35 (UTC)

@SonicoXD: Sure, any comments and questions are welcome. And yes, the application should (in my opinion) run in the background, visible through systray's symbol. But it seems you're right: If I close (not quit) the application it vanishes after a few seconds from systray and task list.

Maybe the answer lies here: "Exit: Closes the current session. If installed, AnyDesk will still be running on the machine. This is indicated by the tray icon. If not installed (no tray icon), closing the last AnyDesk window will terminate AnyDesk and your machine will not be online in the AnyDesk network."

I'll have a look into this as my PKGBUILD needs some love (ie autostart has changed) - and this could be the exact solution for you.

churro commented on 2018-07-06 14:52 (UTC)

the application installed fine and seems to run fine. However, it doesn't mesh well with my dark qt theme. Is there anyway to set it so it launches with a white theme to avoid this problem?

SonicoXD commented on 2018-07-06 04:20 (UTC)

Sorry, not sure if I should ask this here. I suspect that when closing the main window, the service should keep running. Is there any way to do this? And also to start AnyDesk on boot?

OJaksch commented on 2018-06-25 16:02 (UTC)

@Tah9phee: Thanks for the kind words. You (and all others) are always welcome!

Tah9phee commented on 2018-06-25 14:18 (UTC)

@OJaksch: thank you! This was what I suspected from the research I was able to do, and your explanation here is great in helping me on the path to learning more and more about the AUR and it's workings. Thanks for taking the time to reply.. installing! And thank you for your maintenance here - much appreciated.

OJaksch commented on 2018-06-24 10:35 (UTC)

@Tah9phee: Have a look at Read and understand how an AUR package is built - then you'll know that commands executed within build process are running below the path of ${BUILDDIR}. This ensures that ie 'rm -rf etc/' removes the given path there. Sure, I could use 'rm -rf ${pkgdir}/etc/' but this would remove the real /etc/ in case of malfunction/typo/emptyness of ${pkgdir} ;)

Tah9phee commented on 2018-06-23 22:32 (UTC)


Just wondering if you could provide an explanation for the following last line in the PKGBUILD ( :

"rm -rf etc/"

This line feels SCARY. Could you comment? Anyone else?

OJaksch commented on 2018-06-21 13:09 (UTC) (edited on 2020-02-18 08:43 (UTC) by OJaksch)

This new version has a new dependency (pango-anydesk) which in turn installs a proper and working older version of pango, which is used by AnyDesk only.

To update to this new version and it's dep you have to uninstall package anydesk first and reinstall it again. New installs aren't affected.

Sorry for any inconveniences.

OJaksch commented on 2018-06-15 07:56 (UTC)

@harrys_laugh: Can't reproduce this on my KDE box. Will try it on i3 the next days. Stay tuned.

harrys_laugh commented on 2018-06-14 19:44 (UTC)

I updated today to 2.9.5-2. Afterwards anydesk freezes and weirds out my i3 session anytime I'm establishing a connection. I can't create new windows and existing terminals freeze. Had to go back to 2.9.4 which works fine

OJaksch commented on 2018-01-30 07:09 (UTC) (edited on 2018-01-30 09:01 (UTC) by OJaksch)

@RemoteAdmin No, seems that you're right. Either I missed that or it's a fairly new dep. Will check and complete that in pkgbuild. Thanks for reporting this!

EDIT: fixed :)

RemoteAdmin commented on 2018-01-30 04:19 (UTC)

Correct me if I'm wrong but shouldn't "libxtst" be a dependency?

At least the binary is requiring it:

readelf -d /usr/bin/anydesk

0x0000000000000001 (NEEDED) Shared library: []

OJaksch commented on 2018-01-14 11:09 (UTC) (edited on 2018-01-16 13:53 (UTC) by OJaksch)

@maximevince Commented and forwarded to Let's see what they will say.

Answer from anydesk:

Wayland is not supported. Wayland has no possibility in it's protocol to take the screen for now. Therefore we had to program an own screen grabber for every desktop and then ask the user for permission (especially gnome3 makes it difficult). AnyDesk and Wayland is starting through XWayland, but as soon as a session is started or tapped, there will used many X11 libraries that XWayland doesn't support (MIT-SHM for example).

If you are interested in AnyDesk under Wayland, I ask you to send a mail to the Wayland devs (the more, the better; we have already sent one) so a unified capture interface would be installed in Wayland (here, the devs then just have to consider security measures). -- Wayland wird von uns nicht unterstützt. Wayland hat im Protokoll keine Möglichkeit vorgesehen das Bild abzugreiffen und dies offengelassen, wie die Compositors das Implementieren. Daher müssten wir für jeden Desktop ein eigenes Screen Grab Programm schreiben und dies teilweile vom Nutzer erst autorisieren lassen (und gerade GNOME 3 macht es einem hier nicht leicht). AnyDesk startet und Wayland zwar, da XWayland vorgeschalten wird, aber sobald eine sitzung gestartet oder abgegriffen wird werden viele X11 Libraries genutzt, die XWayland nicht unterstützt (MIT-SHM z.B.).

Falls Sie Interesse an AnyDesk unter Wayland haben, bitte ich sie, den Wayland devs eine Mail zu schicken (je mehr, umso besser, wir haben auch schon eine abgesetzt), damit eine einheitliche Capture Schnittstelle in Wayland eingebaut wird (hier müssen sich die Devs dann eben ggf. Sicherheitsmaßnahmen überlegen).

maximevince commented on 2018-01-14 08:30 (UTC)

AnyDesk closing immediately after connecting (e.g. to Win7 host) seems to be cause by some Wayland issue. Switching to Xorg fixes the problem for me.

olav_st commented on 2017-09-30 14:20 (UTC)

I got the following error when trying to use anydesk: sh: lsb_release: command not found The fix was to install the package `lsb-release`. Maybe it should be added to the list of dependencies?

ghmeta commented on 2017-05-22 01:34 (UTC) (edited on 2017-05-23 12:52 (UTC) by ghmeta)

Hi, I install anydesk by `makepkg -si`. But anydesk has no response when I create new connection. There is only a anydesk icon in my toolbar, I can not seed any window about anydesk. I have solved it. It's because of my driver problem.

termuellinator commented on 2017-04-14 11:43 (UTC)

@ltcmdrdata i've got the same problem here on 2 manjaro-pcs and when tested on a VM. No matter if remote pc is linux or windows. also, when trying to connect to a linux-pc from a windows one, the same behaviour occurs. Didn't find anything in the anydesk-forums though...

OJaksch commented on 2017-03-30 11:24 (UTC)

> Any idea why I can not connect to remote client (Windows 7 with anydesk 3.1.1)? No, not yet, but I'm sure that this is a Windows-thing with it's firewall profiles. Maybe yours has "public" active and is blocking incoming packets therefore?

ltcmdrdata commented on 2017-03-30 11:19 (UTC)

Any idea why I can not connect to remote client (Windows 7 with anydesk 3.1.1)? The client works perfect (I can connect to it from an anydesk Windows Host). On my 2 Arch Linux computer (desktop and notebook), I can not connect to any other host. Anydesk starts and shows the connection screen. Whe I enter the ID of the remote computer, the connections starts and asks for password. When I enter it, the window disappears and nothing happens. At the remote computer the anydesk windows shows up and it seems that I am connect. When I try it several times, the window on the remote computer shows several connections, but I do not get any window of the remote computer on my desktop. I do not get any error logs at console or syslog...

OJaksch commented on 2017-01-14 10:34 (UTC) (edited on 2017-01-23 12:29 (UTC) by OJaksch)

Fixed this morning. Please report if Gnome still doesn't feel happy. Thanks for pointing this out. EDIT: I contacted anydesk: This will be fixed in the next release by anydesk itself. Great!

dodomorandi commented on 2017-01-13 21:06 (UTC)

I noticed that the following files have CLRFs: /usr/share/pixmaps/anydesk.xpm /usr/share/applications/anydesk.desktop /etc/xdg/autostart/anydesk.desktop I found it quite weird. I looked at the tar.gz files ([amd64|i386].tar.gz) and they seem to be unaffected. However, they are missing the anydesk.desktop files. I am not totally sure, but the GNOME autostart system does not seem to like the CLRFs inside .desktop files, even if they work flawlessly when you run them manually.

OJaksch commented on 2016-10-08 03:50 (UTC)

No need to hurry - Flagging a package out-of-date is sufficient ;) I saw the upcoming 2.5.0 at their changelog since weeks, they send promotional mails, but no info about release so I missed that.

termuellinator commented on 2016-10-07 23:55 (UTC)

# Maintainer: Oliver Jaksch <> pkgname=anydesk pkgver=2.5.0 pkgrel=1 pkgdesc="'AnyDesk Free' is an All-In-One Software for Remote Support" arch=('i686' 'x86_64') url="" license=('custom:Freeware') depends=('gtkglext') optdepends=('libpulse') source_i686=(${pkgname}_${pkgver}-1_i386.deb) source_x86_64=(${pkgname}_${pkgver}-1_amd64.deb) sha256sums_i686=('c978aafbc9d7203b805052dd2aa3a673211da76786c769a8bfdd322dc85446f5') sha256sums_x86_64=('c5ad3ea227e875db1ef0e78474b1039ac8fefe0965c306196dec6b8e1a8917b7') package() { cd "${pkgdir}" tar xf "${srcdir}/data.tar.gz" # If you want to keep the autostart mode, comment next line rm -rf etc/ } should be the current PKGBUILD :)

Esspy commented on 2015-11-14 14:39 (UTC)

it seems i was a little to fast. After >10 seconds the initial screen was transfered. so it basically works but very very slow. i've tried win -> win on the same machines indeed the broadcast is very fast. but if i try from linux to win the connection is very slow. its seems there are some performance problems in the linux version. i've tried all options. i've used the latest version of your PKGBUILD.

OJaksch commented on 2015-11-14 13:00 (UTC)

Oh, and another attempt might be to manually checkout the "other" version at That's the version I used 'til yesterday in this package. What pkgrel of this pkgbuild do you have used?

OJaksch commented on 2015-11-14 12:49 (UTC)

Strange. Looks like there's missing a dependency at your side I don't know of. Please have a look at , speacially and report back when successful. I'll update the package asap then. Another way that might be helpful is to start anydesk from cli as it brings some output to stdout.

Esspy commented on 2015-11-14 11:58 (UTC)

after some reading i found out that for local connections you've to tell the local ip or hostname (not the AD address). After that the local connection works fast with some visual glitches when moving windows around. But WAN still has no video just a gray window. Firewall is off.

OJaksch commented on 2015-11-14 09:15 (UTC)

I just re-tested pkgrel 2 as client with arch and win as server by WAN but works very fast. Maybe a firewall issue?

Esspy commented on 2015-11-14 08:06 (UTC)

did anydesk work for anyone? i've tried over LAN and WAN but no success. On LAN its is terrible slow and over WAN there is a connection but no video. Any hints?

xarbit commented on 2015-11-13 21:10 (UTC)

Thanks OJaksch, got it.. na, don't need autostart :-)

OJaksch commented on 2015-11-13 21:02 (UTC)

scujas, thanks for your suggestion. I agree with you, so I updated this package. Please have an eye at PKGBUILD regarding autostart feature.

xarbit commented on 2015-11-13 17:06 (UTC)

you should consider to use the deb files instead of the tar.gz. They at least include .desktop files and so.

OJaksch commented on 2015-09-10 17:25 (UTC)

Sure, it's updated. Thanks for ye request. Hope many of us will find this tool useful.

Ravenman commented on 2015-09-10 16:54 (UTC)

Can you add gtkglext like dependence for this package, please?