Puppy Linux Discussion Forum

Hi. I'm trying to make Anydesk 6.2 run. Console notifies "libpolkit-gobject-1.so.0" is not found. To compile this, libmozjs-52.so must be compiled first (I installed libmozjs185 from repositories and no luck) and for that, JS-52.2.1gnome1 is needed, which can't be compiled either in my 4GB notebook, because some Python 2.7 virtual environment error can't be resolved and secondly, it seemingly needs at least 8GB of RAM to compile.
My question is: is this library so problematic to get? Or should it be got easily and all of the above is just something wrong in my system?

@01101001b - I've gziped that library for you, assuming it's 64bit. Not sure where Fatdog's libs go,
so expand it in an empty folder (via tar -zxvf) & move both lib & its link to appropriate lib folder.

Thank you so much @ozsouth !

It was a nice try. Now if I try to run Anydesk as root, this error appears:
"sh: lsb_release: command not found
double free or corruption (fasttop)".

And if I use run-as-spot:
"dash: 1: anydesk: not found".

Interesting output when I run "ld anydesk":
"ld: error in anydesk(.eh_frame); no .eh_frame_hdr table will be created.
ld: warning: cannot find entry symbol _start; defaulting to 0000000000415100"

"ldd anydesk" shows no library is missing.

So this is it. Nevertheless, your response is greatly appreciated Thanks again!

@01101001b

Anydesk was very problematic to install. Just use Rustdesk instead. It works like TeamViewer

What are you trying to achieve?

Have you had a look at BackSeatDriver that is included in Fatdog?

Anydesk was very problematic to install. Just use Rustdesk instead.

Thanks @mistfire ! It almost worked in my system (for some reason, it failed to recognize my X server as X11... 'cause it is). A quite promising project!

p310don wrote: ↑Thu Sep 01, 2022 1:25 pm

What are you trying to achieve?

I was "Trying to make Anydesk 6.2 run", maybe?

p310don wrote: ↑Thu Sep 01, 2022 1:25 pm

Have you had a look at BackSeatDriver that is included in Fatdog?

Yes, I know BSD. Not my cup of tea, though. Nonetheless, your "heads up" is truly appreciated

@01101001b

it failed to recognize my X server as X11..

Had the same problem with Rustdesk, many reports of this on the web, could not find a solution.

Have you tried @mikewalsh Anydesk Portable?

Thanks
wizard

failed to recognize my X server as X11

It might help to delete the -nolisten tcp option in /usr/bin/xwin

it failed to recognize my X server as X11...

wizard wrote:

Had the same problem with Rustdesk, many reports of this on the web

Glad to know my system is not the culprit then

wizard wrote:

Have you tried @mikewalsh Anydesk Portable?

I have. This time the missing library has changed. Now it's "libsystemd.so.0" ... and that is the end of the road for me Truly thankful for your help @wizard !

williams2 wrote:

It might help to delete the -nolisten tcp option in /usr/bin/xwin

I failed to find that option in xwin. No surprise, though, 'cause I can confirm FD64 has grown apart from Puppy in not a minor number of aspects Thanks for the tip @williams2 !

wizard wrote: ↑Sun Sep 04, 2022 2:18 pm

@01101001b

it failed to recognize my X server as X11..

Had the same problem with Rustdesk, many reports of this on the web, could not find a solution.

Have you tried @mikewalsh Anydesk Portable?

Thanks
wizard

Although the rustdesk error message was shown, did you try to connect remotely using it?

@01101001b Last I looked at AnyDesk for Fatdog64, version 6.0.1 did run. I haven't bothered to keep up with AnyDesk upgrades partly because I lost interest for its remote audio support on Linux, a simplex channel from controlled PC to controller PC only. AnyDesk for Windows and Mac did better at the time. AnyDesk 6.2 for Linux might do better now, I don't know.

To make 6.0.1 work you needed to install package elogind, which can be downloaded from the pulseaudio-depends subfolder of the shared folder link in the first post of this thread circa late 2020. You also needed to create a symbolic link from /usr/bin/lsb_release to /bin/true. You wouldn't run AnyDesk's own installer script but instead unpack the AnyDesk 6.0.1 archive and place apples with apples in the / file system hierarchy. The end result would be capable of full remote desktop control but incapable of unattended login or audio transmission.

For AnyDesk 6.2 on Fatdog64 I'd expect a similar roadmap as the one I traced above, with similar results in case of success. However, I can't predict whether there can be any success, given that 6.2 has certaintly diverged internally from 6.0.1 so YMMV. If you have installed polkit- or systemd-related packages on your Fatdog64 system from previous experiments, make sure to clear them out before you engage in this experiment.

Why is it that you need AnyDesk 6.2? Do you need to control remote Windows and Mac systems? Then AnyDesk would be a good choice. You may also consider no-machine for a similar set of features. I have successfully used version 7.0.211 to control MacOS 10.14 Mojave and Windows 7.1 PC from Fatdog64.

Alternatively, for screen sharing only in a cross-platform environment, you may want to consider one of the many VNC-based solutions. Screen sharing is enough to control a remote PC without audio or file sharing. Fatdog64 offers several makes of VNC clients and servers - search for VNC in the Gslapt package manager or just use the pre-installed TigerVNC client (if you need a VNC server, x11vnc is a good choice). To establish connection, the remote controller/controlled Windows PC would need to run a VNC client/server respectively, such as TigerVNC, UltraVNC, RealVNC, and so on.

@williams2

For reference:
Hardware = Intel quad core
Ram = 4gb
OS = Fossapup64
rustdesk-1.1.9.deb
xdotools

edit xwin:

/usr/bin/xinit ${XINITRC} -- -br -nolisten tcp > $LOGFILE_X 2>&1

to:

/usr/bin/xinit ${XINITRC} -- -br > $LOGFILE_X 2>&1

save and restart x

Produces same Rustdesk error

@mistfire

Yes, did try connect and got this error:

Thanks
wizard

@wizard

For me I just ignore the X11 error message on RustDesk. It just works on my QuickPup64

Does your firewall enabled? Make sure also that the remote computer has rustdesk too

@mistfire

Both computers running same version of Rustdesk, no firewalls in use.

Thanks
wizard

wizard wrote: ↑Tue Sep 06, 2022 12:50 am

@mistfire

Both computers running same version of Rustdesk, no firewalls in use.

Thanks
wizard

I wonder if the deps in your system are satisfied enough if checkdeps command exists run this command

checkdeps -system

@mistfire

Running rustdesk from terminal shows no errors and running checkdeps on the binary shows no missing dependencies.

Thanks
wizard

Try this, run rustdesk, if connecting to remote fails then read the log files /var/log . It might get some clues why it fails.

Also check if libssl 1.2.1 was installed.

step wrote: ↑Mon Sep 05, 2022 8:53 am

Why is it that you need AnyDesk 6.2?

No particular reason for that specific version apart from the fact I was trying to make it run. I pointed it out to be "in the same page" with anyone who could eventually assist me.

step wrote: ↑Mon Sep 05, 2022 8:53 am

Do you need to control remote Windows and Mac systems?

You hit the mark.

step wrote: ↑Mon Sep 05, 2022 8:53 am

You may also consider no-machine for a similar set of features.

No-machine shapes up as a sound option. I'll keep it in mind. Thx!

As a side note, let me tell you I enjoyed reading your solid, painstaking reply