Request: please make an AppImage available #414

Closed
opened 2026-02-20 23:00:47 -05:00 by deekerman · 82 comments
Owner

Originally created by @fluffynuts on GitHub (May 21, 2022).

Hi, this looks great! If possible, please make an AppImage available in releases, for linux hosts which aren't deb-based?

Originally created by @fluffynuts on GitHub (May 21, 2022). Hi, this looks great! If possible, please make an AppImage available in releases, for linux hosts which aren't deb-based?
Author
Owner

@maverick74 commented on GitHub (May 21, 2022):

We also have RPM packages.
But an appimage of this would be gold!!!

(I wonder why the other appimage issue #33 was closed... @rustdesk Didn't give a reason for the won't fix...)

@maverick74 commented on GitHub (May 21, 2022): We also have RPM packages. But an appimage of this would be gold!!! (I wonder why the other appimage issue #33 was closed... @rustdesk Didn't give a reason for the won't fix...)
Author
Owner

@rustdesk commented on GitHub (May 22, 2022):

closed

Very sorry for this.

@rustdesk commented on GitHub (May 22, 2022): > closed Very sorry for this.
Author
Owner

@rustdesk commented on GitHub (May 22, 2022):

AppImage, Snap, Flatpak, which one should be? Each one has their followers.

BTW, we have a snap one, though I have not pushed to store yet, and it requires manually connect something. https://github.com/rustdesk/rustdesk/tree/master/snap

@rustdesk commented on GitHub (May 22, 2022): AppImage, Snap, Flatpak, which one should be? Each one has their followers. BTW, we have a snap one, though I have not pushed to store yet, and it requires manually connect something. https://github.com/rustdesk/rustdesk/tree/master/snap
Author
Owner

@rustdesk commented on GitHub (May 22, 2022):

deb-based

Not only deb, we have the other 3, they are the most popular distros.

@rustdesk commented on GitHub (May 22, 2022): > deb-based Not only deb, we have the other 3, they are the most popular distros.
Author
Owner

@fluffynuts commented on GitHub (May 22, 2022):

snap requires systemd

AppImage is standalone, "just works" - it's a great alternative, imo. Much like AnyDesk, this allows anyone to just download a binary and use it, without involving actually installing a package.

@fluffynuts commented on GitHub (May 22, 2022): snap requires systemd AppImage is standalone, "just works" - it's a great alternative, imo. Much like AnyDesk, this allows anyone to just download a binary and use it, without involving actually installing a package.
Author
Owner

@fluffynuts commented on GitHub (May 22, 2022):

Personally, I use Gentoo, and I don't (yet) know enough about creating an ebuild to piece one together. First, I'm going to see about building from source. I'd love an open-source alternative to AnyDesk.

@fluffynuts commented on GitHub (May 22, 2022): Personally, I use Gentoo, and I don't (yet) know enough about creating an ebuild to piece one together. First, I'm going to see about building from source. I'd love an open-source alternative to AnyDesk.
Author
Owner

@fluffynuts commented on GitHub (May 22, 2022):

hm, sciter isn't open-source, at least, not open-for-everyone ): it looks like there's a discussion around using Flutter or Tauri to replace it? Guess I'll hang on - my 2c vote is for Tauri, but I'm sure my opinion carries little weight 😄

@fluffynuts commented on GitHub (May 22, 2022): hm, sciter isn't open-source, at least, not open-for-everyone ): it looks like there's a discussion around using Flutter or Tauri to replace it? Guess I'll hang on - my 2c vote is for Tauri, but I'm sure my opinion carries little weight :smile:
Author
Owner

@maverick74 commented on GitHub (May 22, 2022):

AppImage, Snap, Flatpak, which one should be? Each one has their followers.

I see what you mean...
But AppImages has their good points: it does not need to be installed (we can mail it, share it caring it in a pen drive) and it works in all Linux distros.

Snap is Ubuntu specific (yes, Ubuntu is the most used distro...)... Too much closed to my taste...

Flatpak is great for all distros as well, but compared to AppImage it requires installation...

But this is just my point of view, naturally...

@maverick74 commented on GitHub (May 22, 2022): > AppImage, Snap, Flatpak, which one should be? Each one has their followers. I see what you mean... But AppImages has their good points: it does not need to be installed (we can mail it, share it caring it in a pen drive) and it works in all Linux distros. Snap is Ubuntu specific (yes, Ubuntu is the most used distro...)... Too much closed to my taste... Flatpak is great for all distros as well, but compared to AppImage it requires installation... But this is just my point of view, naturally...
Author
Owner

@fluffynuts commented on GitHub (May 22, 2022):

yeah the real win of AppImage is portability, along with "work anywhere"

however, I'm not making any demands 😅 just that AppImage would be aces. I don't expect official support for less-mainstream distros like Gentoo, but AppImage would serve everyone

@fluffynuts commented on GitHub (May 22, 2022): yeah the real win of AppImage is portability, along with "work anywhere" however, I'm not making any demands :sweat_smile: just that AppImage would be aces. I don't expect official support for less-mainstream distros like Gentoo, but AppImage would serve _everyone_
Author
Owner

@maverick74 commented on GitHub (May 25, 2022):

Maybe creating a RustDesk AppImage is as easy as mentioned in comment 1: https://github.com/signalapp/Signal-Desktop/issues/1758

Or maybe @probonopd could help :)

@maverick74 commented on GitHub (May 25, 2022): Maybe creating a RustDesk AppImage is as easy as mentioned in comment 1: https://github.com/signalapp/Signal-Desktop/issues/1758 Or maybe @probonopd could help :)
Author
Owner

@rustdesk commented on GitHub (May 25, 2022):

We are much complexer than singal, because we have to do a lot of system jobs.

@rustdesk commented on GitHub (May 25, 2022): We are much complexer than singal, because we have to do a lot of system jobs.
Author
Owner

@maverick74 commented on GitHub (May 25, 2022):

I see...
If you need help, i believe probonopd is the one to call then.

(Sorry for launching you into this issue @probonopd but an appimage of rustdesk would be extremely useful)

@maverick74 commented on GitHub (May 25, 2022): I see... If you need help, i believe probonopd is the one to call then. (Sorry for launching you into this issue @probonopd but an appimage of rustdesk would be extremely useful)
Author
Owner

@probonopd commented on GitHub (May 26, 2022):

Yes, let me know if you are running into any issues.

@probonopd commented on GitHub (May 26, 2022): Yes, let me know if you are running into any issues.
Author
Owner

@rustdesk commented on GitHub (May 26, 2022):

@Kingtous

@rustdesk commented on GitHub (May 26, 2022): @Kingtous
Author
Owner

@rustdesk commented on GitHub (May 26, 2022):

Yes, let me know if you are running into any issues.

Thanks

@rustdesk commented on GitHub (May 26, 2022): > Yes, let me know if you are running into any issues. Thanks
Author
Owner

@shuvashish76 commented on GitHub (May 28, 2022):

AppImage, Snap, Flatpak, which one should be? Each one has their followers.

Of course but unlike other packages AppImage is a community project & you could install without the need for a centralized store...

@shuvashish76 commented on GitHub (May 28, 2022): > AppImage, Snap, Flatpak, which one should be? Each one has their followers. Of course but unlike other packages [AppImage](https://github.com/AppImage/AppImageKit) is a community project & you could install without the need for a centralized store...
Author
Owner

@fluffynuts commented on GitHub (May 28, 2022):

indeed, this is the big win of AppImage - it's a portable app, no need for stores or sources or package management. Personally, I prefer something to come from my package manager (portage), but if it doesn't, something that's truly agnostic is a win for everyone.

@fluffynuts commented on GitHub (May 28, 2022): indeed, this is the big win of AppImage - it's a portable app, no need for stores or sources or package management. Personally, I _prefer_ something to come from my package manager (portage), but if it doesn't, something that's truly agnostic is a win for everyone.
Author
Owner

@bmcgonag commented on GitHub (May 29, 2022):

Just to pile on, I love AppImages as they are easy to download, take with me, move around, copy to other machines, and just run. No setting up snapd or flathub or anything. So for family who are just normal users, getting them to download and use an AppImage is far easier than getting them to install a deb, snap, or flatpak.

@bmcgonag commented on GitHub (May 29, 2022): Just to pile on, I love AppImages as they are easy to download, take with me, move around, copy to other machines, and just run. No setting up snapd or flathub or anything. So for family who are just normal users, getting them to download and use an AppImage is far easier than getting them to install a deb, snap, or flatpak.
Author
Owner

@JokerGermany commented on GitHub (May 31, 2022):

I like flatpak because updating is easy.

Without a ppa/flatpak i can only use it for smartphones...

@JokerGermany commented on GitHub (May 31, 2022): I like flatpak because updating is easy. Without a ppa/flatpak i can only use it for smartphones...
Author
Owner

@quazar-omega commented on GitHub (May 31, 2022):

Just throwing my two cents here, I think Appimage is cool and it would serve the purpose well, I also think that Flatpak is way more convenient in general as quite a bit of distros support it by default, its main selling points for me are:

  • direct integration with the system (without needing external tools)
  • easy to update
  • control over system access

Of course asking for two packages might be a tall order, I don't know how difficult it actually is, so if I had to choose, in the short term I would favour Appimage to get wide support out, then I would reconsider Flatpak later when I'm already comfortable with the former

@quazar-omega commented on GitHub (May 31, 2022): Just throwing my two cents here, I think Appimage is cool and it would serve the purpose well, I also think that Flatpak is way more convenient in general as quite a bit of distros [support it by default](https://en.wikipedia.org/wiki/Flatpak#Support), its main selling points for me are: - direct integration with the system (without needing external tools) - easy to update - control over system access Of course asking for two packages might be a tall order, I don't know how difficult it actually is, so if I had to choose, in the short term I would favour Appimage to get wide support out, then I would reconsider Flatpak later when I'm already comfortable with the former
Author
Owner

@maverick74 commented on GitHub (May 31, 2022):

I like flatpak because updating is easy.

Without a ppa/flatpak i can only use it for smartphones...

AppImage also supports auto-update as soon as new versions are available, however that's up to the software packager to deal with it.

@maverick74 commented on GitHub (May 31, 2022): > I like flatpak because updating is easy. > > Without a ppa/flatpak i can only use it for smartphones... AppImage also supports auto-update as soon as new versions are available, however that's up to the software packager to deal with it.
Author
Owner

@JokerGermany commented on GitHub (Jun 1, 2022):

AppImage also supports auto-update as soon as new versions are available, however that's up to the software packager to deal with it.

The AppImages i know let you download a new file which you have to grant execute rights and that is nothing which will be easy for my supported persons...

@JokerGermany commented on GitHub (Jun 1, 2022): > AppImage also supports auto-update as soon as new versions are available, however that's up to the software packager to deal with it. The AppImages i know let you download a new file which you have to grant execute rights and that is nothing which will be easy for my supported persons...
Author
Owner

@maverick74 commented on GitHub (Jun 1, 2022):

AppImage also supports auto-update as soon as new versions are available, however that's up to the software packager to deal with it.

The AppImages i know let you download a new file which you have to grant execute rights and that is nothing which will be easy for my supported persons...

in KDE Plasma, once you click on it, it will ask you if you want to grant them execution rights and remember it in the future (no more right clicks)...

Anyway if you prefer you also have the Appimage Launcher that gives you some extra features.

Appimages can also run in a sandbox...

A lot of other projects are also using it (Krita, Libreoffice, etc)

@maverick74 commented on GitHub (Jun 1, 2022): > > AppImage also supports auto-update as soon as new versions are available, however that's up to the software packager to deal with it. > > The AppImages i know let you download a new file which you have to grant execute rights and that is nothing which will be easy for my supported persons... in KDE Plasma, once you click on it, it will ask you if you want to grant them execution rights and remember it in the future (no more right clicks)... Anyway if you prefer you also have the Appimage Launcher that gives you some extra features. Appimages can also run in a sandbox... A lot of other projects are also using it (Krita, Libreoffice, etc)
Author
Owner

@UnixPhonez commented on GitHub (Jun 8, 2022):

AppImage, Snap, Flatpak, which one should be? Each one has their followers.

BTW, we have a snap one, though I have not pushed to store yet, and it requires manually connect something. https://github.com/rustdesk/rustdesk/tree/master/snap

flatpak and submit to flathub, there easy to update and will make your app open to thousands of users by default due to it's integration in many distros webstores

@UnixPhonez commented on GitHub (Jun 8, 2022): > AppImage, Snap, Flatpak, which one should be? Each one has their followers. > > BTW, we have a snap one, though I have not pushed to store yet, and it requires manually connect something. https://github.com/rustdesk/rustdesk/tree/master/snap flatpak and submit to flathub, there easy to update and will make your app open to thousands of users by default due to it's integration in many distros webstores
Author
Owner

@bmcgonag commented on GitHub (Jun 8, 2022):

I know they all have their followers, I only prefer AppImage because it allows you to take on a USB and run on any system. Portability is super useful with an app like this. Flat pack requires flat oak on the system, as does snap.

@bmcgonag commented on GitHub (Jun 8, 2022): I know they all have their followers, I only prefer AppImage because it allows you to take on a USB and run on any system. Portability is super useful with an app like this. Flat pack requires flat oak on the system, as does snap.
Author
Owner

@maverick74 commented on GitHub (Jun 9, 2022):

Not to mention that it's a lot easier to say to a less tech friend that he just needs to download and double click the appimage (instead of having to "install" additional software)

@maverick74 commented on GitHub (Jun 9, 2022): Not to mention that it's a lot easier to say to a less tech friend that he just needs to download and double click the appimage (instead of having to "install" additional software)
Author
Owner

@rustdesk commented on GitHub (Jun 9, 2022):

our appimage file built on ubuntu 18 has 60MB+ in size, 30MB+ on ubuntu 20.

@rustdesk commented on GitHub (Jun 9, 2022): our appimage file built on ubuntu 18 has 60MB+ in size, 30MB+ on ubuntu 20.
Author
Owner

@Kingtous commented on GitHub (Jun 9, 2022):

I found out that appimage-builder --generate command prefers to bundle whole deb dependencies' package (libxfixes for example) in 18.04, while it only bundles a shared library (/lib/x86_64-linux-gnu/libXfixes.so.3) in 20.04.

The history of AppImageBuilder.yml file can be found here, which contains both configurations on 20.04 and 18.04.

@Kingtous commented on GitHub (Jun 9, 2022): I found out that `appimage-builder --generate` command prefers to bundle whole deb dependencies' package (`libxfixes` for example) in `18.04`, while it only bundles a shared library (`/lib/x86_64-linux-gnu/libXfixes.so.3`) in `20.04`. The history of AppImageBuilder.yml file can be found [here](https://github.com/rustdesk/rustdesk/commits/master/appimage/AppImageBuilder.yml), which contains both configurations on 20.04 and 18.04.
Author
Owner

@rustdesk commented on GitHub (Jun 9, 2022):

@probonopd AppImage seems friendly to users, but not friendly to developers. We build rustdesk-18.appimage on Ubuntu 18 and rustdesk-20.appimage on Ubuntu 20.
rustdesk-20.appimage can start on Ubuntu 18, but fails to connect to X11.
rustdesk-18.appimage crashes on arch, rustdesk-20.appimage works fine.

@rustdesk commented on GitHub (Jun 9, 2022): @probonopd AppImage seems friendly to users, but not friendly to developers. We build rustdesk-18.appimage on Ubuntu 18 and rustdesk-20.appimage on Ubuntu 20. rustdesk-20.appimage can start on Ubuntu 18, but fails to connect to X11. rustdesk-18.appimage crashes on arch, rustdesk-20.appimage works fine.
Author
Owner

@JokerGermany commented on GitHub (Jun 9, 2022):

Not to mention that it's a lot easier to say to a less tech friend that he just needs to download and double click the appimage (instead of having to "install" additional software)

Then you have to tell him how to make it executable.
And when i look how to update linphone, then i hope rustdesk will make it better or will support to control very old versions with new versions...

@JokerGermany commented on GitHub (Jun 9, 2022): > Not to mention that it's a lot easier to say to a less tech friend that he just needs to download and double click the appimage (instead of having to "install" additional software) Then you have to tell him how to make it executable. And when i look how to update linphone, then i hope rustdesk will make it better or will support to control very old versions with new versions...
Author
Owner

@probonopd commented on GitHub (Jun 9, 2022):

@rustdesk since you are using appimage-builder, please report this at https://github.com/AppImageCrafters/appimage-builder/issues. Thanks!

@probonopd commented on GitHub (Jun 9, 2022): @rustdesk since you are using `appimage-builder`, please report this at https://github.com/AppImageCrafters/appimage-builder/issues. Thanks!
Author
Owner

@probonopd commented on GitHub (Jun 9, 2022):

Then you have to tell him how to make it executable.

Yes, easy:

image

Source:
https://discourse.appimage.org/t/how-to-run-an-appimage/80

@probonopd commented on GitHub (Jun 9, 2022): > Then you have to tell him how to make it executable. Yes, easy: ![image](https://aws1.discourse-cdn.com/standard10/uploads/appimage/optimized/1X/a4889c5cb8711d6845b58135080787d2f370af35_2_500x500.gif) Source: https://discourse.appimage.org/t/how-to-run-an-appimage/80
Author
Owner

@maverick74 commented on GitHub (Jun 9, 2022):

Then you have to tell him how to make it executable. And when i look how to update linphone, then i hope rustdesk will make it better or will support to control very old versions with new versions...

In Plasma I don't need that.
I download the appimage,
click on it,
it warns me (the first time) it will execute that file and after I press OK that's it.

Software is running!!!

@maverick74 commented on GitHub (Jun 9, 2022): > Then you have to tell him how to make it executable. And when i look how to update linphone, then i hope rustdesk will make it better or will support to control very old versions with new versions... In Plasma I don't need that. I download the appimage, click on it, it warns me (the first time) it will execute that file and after I press OK that's it. Software is running!!!
Author
Owner

@dginovker commented on GitHub (Jun 12, 2022):

AppImage is amazing and I support everyone who wants it. Flatpak is a great choice too - I always go to Flathub.org to find my apps these days, since I know any app I find there will work on any distro no matter what. If RustDesk could add Flatpak support, that would be amazing!

@dginovker commented on GitHub (Jun 12, 2022): AppImage is amazing and I support everyone who wants it. Flatpak is a great choice too - I always go to [Flathub.org](https://flathub.org/home) to find my apps these days, since I know any app I find there will work on any distro no matter what. If RustDesk could add Flatpak support, that would be amazing!
Author
Owner

@rustdesk commented on GitHub (Jun 12, 2022):

Try out this https://github.com/rustdesk/rustdesk/releases/download/tmp/RustDesk-1.1.10-x86_64_1804.AppImage please, let me know please if it crashes on your distro.

@rustdesk commented on GitHub (Jun 12, 2022): Try out this https://github.com/rustdesk/rustdesk/releases/download/tmp/RustDesk-1.1.10-x86_64_1804.AppImage please, let me know please if it crashes on your distro.
Author
Owner

@shuvashish76 commented on GitHub (Jun 12, 2022):

If RustDesk could add Flatpak support, that would be amazing!

Let's not mixup everything this issue was specifically created for AppImage support :)
Please comment on #459 for Flatpak support.

Thanks

@shuvashish76 commented on GitHub (Jun 12, 2022): > If RustDesk could add Flatpak support, that would be amazing! Let's not mixup everything this issue was specifically created for AppImage support :) Please comment on #459 for Flatpak support. Thanks
Author
Owner

@fluffynuts commented on GitHub (Jun 12, 2022):

Starts up on my machine - I'll test actual usage tomorrow. Thanks so much for working on this.

@fluffynuts commented on GitHub (Jun 12, 2022): Starts up on my machine - I'll test actual usage tomorrow. Thanks so much for working on this.
Author
Owner

@bmcgonag commented on GitHub (Jun 12, 2022):

Just test the latest appimage based on 1804.

I'm using

  • Kubuntu 22.04

Connected to:

  • Windows 10 64 Bit desktop - SUCCESS
  • Windows 10 64 Bit VM - SUCCESS
  • Kubuntu 22.04 (separate machine) - SUCCESS

Working quite well. Thank you so much for making the appimage. It's awesome!

@bmcgonag commented on GitHub (Jun 12, 2022): Just test the latest appimage based on 1804. I'm using - Kubuntu 22.04 Connected to: - Windows 10 64 Bit desktop - SUCCESS - Windows 10 64 Bit VM - SUCCESS - Kubuntu 22.04 (separate machine) - SUCCESS Working quite well. Thank you so much for making the appimage. It's awesome!
Author
Owner

@UnixPhonez commented on GitHub (Jun 12, 2022):

Try out this https://github.com/rustdesk/rustdesk/releases/download/tmp/RustDesk-1.1.10-x86_64_1804.AppImage please, let me know please if it crashes on your distro.

Just tested the latest appimage

System is Fedora Linux 36 (Workstation Edition)
Specs:
64-bit
Gnome 42.2
Windowing X11
Lenovo ThinkPad T14s Gen 1
AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16
AMD RENOIR

It's completely broken doesn't run but installs

@UnixPhonez commented on GitHub (Jun 12, 2022): > Try out this https://github.com/rustdesk/rustdesk/releases/download/tmp/RustDesk-1.1.10-x86_64_1804.AppImage please, let me know please if it crashes on your distro. Just tested the latest appimage System is Fedora Linux 36 (Workstation Edition) Specs: 64-bit Gnome 42.2 Windowing X11 Lenovo ThinkPad T14s Gen 1 AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16 AMD RENOIR It's completely **broken** doesn't run but installs
Author
Owner

@Kingtous commented on GitHub (Jun 12, 2022):

Could you please try to execute AppImage from the console? Is it show a core-dumped or libnsl.so not found?

@Kingtous commented on GitHub (Jun 12, 2022): > Could you please try to execute AppImage from the console? Is it show a `core-dumped` or `libnsl.so` not found?
Author
Owner

@UnixPhonez commented on GitHub (Jun 12, 2022):

none technical here, how can this be done?

@UnixPhonez commented on GitHub (Jun 12, 2022): none technical here, how can this be done?
Author
Owner

@Kingtous commented on GitHub (Jun 12, 2022):

none technical here, how can this be done?

Open your terminal, cd /path/to/rustdesk.AppImage, then ./rustdesk.AppImage to execute it. I try fedora 36 workstation in virtual machine too. I found errors described below:

  1. After a fresh install of fedora 36, I execute the AppImage from the console to show logs. I found the system is missing libnsl package (The package is not included in Ubuntu 18.04 and it's related to glibc).
  2. Then I install libnsl from the console using yum. libnsl issue resolved, but I get a new error: core dumped. stack trace shows it's a libglib-2.0.so exception. It's confusing.
(gdb) bt
#0  0x00007ffff1851fc1 in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007ffff185305c in g_log_default_handler () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff18532e2 in g_logv () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff185343f in g_log () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ffff210e4f9 in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007ffff210eb5c in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x00007ffff211297b in g_settings_get_enum () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x00007ffff5494edf in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#8  0x00007ffff5496148 in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#9  0x00007ffff549072e in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#10 0x00007ffff5435d5d in gdk_display_manager_open_display () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#11 0x00007ffff702f69a in gtk_init_check () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x00007ffff702f6c9 in gtk_init () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#13 0x00005555554d1a9d in ?? ()
#14 0x00005555554be0e3 in ?? ()
#15 0x00005555554d5bcc in main ()
@Kingtous commented on GitHub (Jun 12, 2022): > none technical here, how can this be done? Open your terminal, `cd /path/to/rustdesk.AppImage`, then `./rustdesk.AppImage` to execute it. I try fedora 36 workstation in virtual machine too. I found errors described below: 1. After a fresh install of fedora 36, I execute the AppImage from the console to show logs. I found the system is missing `libnsl` package (The package is not included in Ubuntu 18.04 and **it's related to glibc**). 2. Then I install libnsl from the console using `yum`. `libnsl` issue resolved, but I get a new error: `core dumped`. stack trace shows it's a `libglib-2.0.so` exception. It's confusing. ``` (gdb) bt #0 0x00007ffff1851fc1 in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007ffff185305c in g_log_default_handler () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ffff18532e2 in g_logv () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff185343f in g_log () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007ffff210e4f9 in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x00007ffff210eb5c in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x00007ffff211297b in g_settings_get_enum () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x00007ffff5494edf in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x00007ffff5496148 in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x00007ffff549072e in ?? () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #10 0x00007ffff5435d5d in gdk_display_manager_open_display () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #11 0x00007ffff702f69a in gtk_init_check () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #12 0x00007ffff702f6c9 in gtk_init () from /tmp/.mount_RustDeu7cpf2//usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #13 0x00005555554d1a9d in ?? () #14 0x00005555554be0e3 in ?? () #15 0x00005555554d5bcc in main () ```
Author
Owner

@Kingtous commented on GitHub (Jun 12, 2022):

Try out this https://github.com/rustdesk/rustdesk/releases/download/tmp/RustDesk-1.1.10-x86_64_1804.AppImage please, let me know please if it crashes on your distro.

Just tested the latest appimage

System is Fedora Linux 36 (Workstation Edition) Specs: 64-bit Gnome 42.2 Windowing X11 Lenovo ThinkPad T14s Gen 1 AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16 AMD RENOIR

It's completely broken doesn't run but installs

Are you using wayland? I tried GNOME xorg and successfuly opened rustdesk.
image

You can switch to GNOME xorg on login screen.
image

@Kingtous commented on GitHub (Jun 12, 2022): > > Try out this https://github.com/rustdesk/rustdesk/releases/download/tmp/RustDesk-1.1.10-x86_64_1804.AppImage please, let me know please if it crashes on your distro. > > Just tested the latest appimage > > System is Fedora Linux 36 (Workstation Edition) Specs: 64-bit Gnome 42.2 Windowing X11 Lenovo ThinkPad T14s Gen 1 AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16 AMD RENOIR > > It's completely **broken** doesn't run but installs Are you using wayland? I tried `GNOME xorg` and successfuly opened `rustdesk`. ![image](https://user-images.githubusercontent.com/39793325/173265300-957b88c3-f26d-4de0-adba-154dbed149d2.png) You can switch to `GNOME xorg` on login screen. ![image](https://user-images.githubusercontent.com/39793325/173265381-934d6cfa-402f-4eef-8999-12fa82bc54c5.png)
Author
Owner

@rustdesk commented on GitHub (Jun 12, 2022):

Looks like we are facing the same problem as OBS. No wonder OBS refused AppImage.

@rustdesk commented on GitHub (Jun 12, 2022): Looks like we are facing the same problem as OBS. No wonder OBS refused AppImage.
Author
Owner

@UnixPhonez commented on GitHub (Jun 12, 2022):

Flatpak it is

@UnixPhonez commented on GitHub (Jun 12, 2022): Flatpak it is
Author
Owner

@fluffynuts commented on GitHub (Jun 13, 2022):

Works great between Windows 11 and Gentoo (KDE) (though there's a little lag when connecting from Gentoo to Windows that isn't there when I go the other way around).

Is there a way to run to the systray? IE run on startup, minimize to tray?

@fluffynuts commented on GitHub (Jun 13, 2022): Works great between Windows 11 and Gentoo (KDE) (though there's a little lag when connecting from Gentoo to Windows that isn't there when I go the other way around). Is there a way to run to the systray? IE run on startup, minimize to tray?
Author
Owner

@maverick74 commented on GitHub (Jun 16, 2022):

Looks like we are facing the same problem as OBS. No wonder OBS refused AppImage.

What's OBS problem? Is that Wayland problem already mentioned at #56 ?

@maverick74 commented on GitHub (Jun 16, 2022): > Looks like we are facing the same problem as OBS. No wonder OBS refused AppImage. What's OBS problem? Is that Wayland problem already mentioned at #56 ?
Author
Owner

@maverick74 commented on GitHub (Jun 20, 2022):

@rustdesk I can confirm this is working like a charm in KDE neon <-> Windows 10 21H2

I just needed a double-click on the appimage file and "off it goes"! Working great. (already being useful!)

I'm on Xorg, however. Can you confirm that the OBS problem you mentioned is "that" Wayland issue?

@maverick74 commented on GitHub (Jun 20, 2022): @rustdesk I can confirm this is working like a charm in KDE neon <-> Windows 10 21H2 I just needed a double-click on the appimage file and "off it goes"! Working great. (already being useful!) I'm on Xorg, however. Can you confirm that the OBS problem you mentioned is "that" Wayland issue?
Author
Owner

@rustdesk commented on GitHub (Jun 20, 2022):

Anyway, we have made our efforts and stated our issues above, https://github.com/rustdesk/rustdesk/tree/master/appimage, https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1160419094, https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1151399825, we also provided an appimage file with not good compatibility. We pause working on it for the time being, because we have to move on. We do not refuse any enthusiats continue working on it. Looking forward to your understanding. BTW, we are also looking for flatpak contributors. https://twitter.com/rustdesk/status/1536299884097449984?t=_SAKDWLrQjvGAV4TWBfVqA&s=19

@rustdesk commented on GitHub (Jun 20, 2022): Anyway, we have made our efforts and stated our issues above, https://github.com/rustdesk/rustdesk/tree/master/appimage, https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1160419094, https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1151399825, we also provided an appimage file with not good compatibility. We pause working on it for the time being, because we have to move on. We do not refuse any enthusiats continue working on it. Looking forward to your understanding. BTW, we are also looking for flatpak contributors. https://twitter.com/rustdesk/status/1536299884097449984?t=_SAKDWLrQjvGAV4TWBfVqA&s=19
Author
Owner

@rustdesk commented on GitHub (Jun 20, 2022):

Looking for appimage contributors.
https://twitter.com/rustdesk/status/1538869207554588672?t=CPKpMIVFLF6loGszQB1WAA&s=19

@rustdesk commented on GitHub (Jun 20, 2022): Looking for appimage contributors. https://twitter.com/rustdesk/status/1538869207554588672?t=CPKpMIVFLF6loGszQB1WAA&s=19
Author
Owner

@Kingtous commented on GitHub (Jun 20, 2022):

We have also opened an issue and described the problems in appimage-builder issues, waiting for reply.
It seems not an issue in the source code of rustdesk, which causes crash on fedora(for example).

@Kingtous commented on GitHub (Jun 20, 2022): We have also opened an issue and described the problems [in appimage-builder issues](https://github.com/AppImageCrafters/appimage-builder/issues/243#issuecomment-1155838504), waiting for reply. It seems not an issue in the source code of `rustdesk`, which causes crash on fedora(for example).
Author
Owner

@rustdesk commented on GitHub (Jul 10, 2022):

Because of no responses, we are not going to support AppImage officially because of its big compatibility issues. AppImage is a very thin wrapper, it requires developer to do a lot of tricks to solve compatibility issues on various distro and versions, and we do not know how to do. Instead, we will test Flatpak.

@rustdesk commented on GitHub (Jul 10, 2022): Because of no responses, we are not going to support AppImage officially because of its big compatibility issues. AppImage is a very thin wrapper, it requires developer to do a lot of tricks to solve compatibility issues on various distro and versions, and we do not know how to do. Instead, we will test Flatpak.
Author
Owner

@fluffynuts commented on GitHub (Jul 11, 2022):

that's a pity - AppImage worked great on Gentoo & required no supporting installation. Could I ask that it be "unofficially supported"? IE script out the process for generating it, make it part of your release cycle with a YMMV flag?

@fluffynuts commented on GitHub (Jul 11, 2022): that's a pity - AppImage worked great on Gentoo & required no supporting installation. Could I ask that it be "unofficially supported"? IE script out the process for generating it, make it part of your release cycle with a YMMV flag?
Author
Owner

@maverick74 commented on GitHub (Jul 11, 2022):

I can also report it worked great here as well.

It was really awesome to be able to remote access my desktop so easily.

@rustdesk Is all your problems reported on https://github.com/AppImageCrafters/appimage-builder/issues/243 ???

I want to keep an eye on the issue!!!

Also @rustdesk, if the problems mentioned are solved would you reconsider adding support?

@maverick74 commented on GitHub (Jul 11, 2022): I can also report it worked great here as well. It was really awesome to be able to remote access my desktop so easily. @rustdesk Is all your problems reported on https://github.com/AppImageCrafters/appimage-builder/issues/243 ??? I want to keep an eye on the issue!!! Also @rustdesk, if the problems mentioned are solved would you reconsider adding support?
Author
Owner

@rustdesk commented on GitHub (Jul 11, 2022):

reconsider

Yes if compatibility issues solved.

@rustdesk commented on GitHub (Jul 11, 2022): > reconsider Yes if compatibility issues solved.
Author
Owner

@maverick74 commented on GitHub (Jul 11, 2022):

@rustdesk OK, and those problems are reported at 243, right?

@maverick74 commented on GitHub (Jul 11, 2022): @rustdesk OK, and those problems are reported at 243, right?
Author
Owner

@rustdesk commented on GitHub (Jul 11, 2022):

Also https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1151399825, I think you will see more issues if you dive into.

@rustdesk commented on GitHub (Jul 11, 2022): Also https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1151399825, I think you will see more issues if you dive into.
Author
Owner

@maverick74 commented on GitHub (Jul 11, 2022):

Also #577 (comment), I think you will see more issues if you dive into.

Ok, I've made a comment on 243 mentioning that.

(I'm sorry for being such a PITA, but i really want to keep an eye on this issue. FlatPack is great and ultimately it's enough to solve our problems but... appimage is tremendously useful and handy to "take everywhere"!)

@maverick74 commented on GitHub (Jul 11, 2022): > Also [#577 (comment)](https://github.com/rustdesk/rustdesk/issues/577#issuecomment-1151399825), I think you will see more issues if you dive into. Ok, I've made a comment on 243 mentioning that. (I'm sorry for being such a PITA, but i **_really_** want to keep an eye on this issue. FlatPack is great and ultimately it's enough to solve our problems but... appimage is tremendously useful and handy to "take everywhere"!)
Author
Owner

@rustdesk commented on GitHub (Jul 26, 2022):

@maverick74 any progress?

@rustdesk commented on GitHub (Jul 26, 2022): @maverick74 any progress?
Author
Owner

@maverick74 commented on GitHub (Jul 27, 2022):

Not that I know of... Unfortunately.
I'm not tied to coding however so maybe something is happening in the background

@maverick74 commented on GitHub (Jul 27, 2022): Not that I know of... Unfortunately. I'm not tied to coding however so maybe something is happening in the background
Author
Owner

@cooperbang commented on GitHub (Aug 10, 2022):

./RustDesk-1.1.10-x86_64_1804.AppImage

-> /tmp/.mount_RustDeJm6xZn//usr/bin/rustdesk: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

Seems that the RustDesk AppImage doesn´t include libnsl.so.1 so it doesn´t run on Fedora Linux (libnsl.so.1 isn´t part of glibc since Fedora 28).

I think the libc6:amd64 Package should be included in https://github.com/rustdesk/rustdesk/blob/master/appimage/AppImageBuilder.yml to fix it.

@cooperbang commented on GitHub (Aug 10, 2022): `./RustDesk-1.1.10-x86_64_1804.AppImage` -> `/tmp/.mount_RustDeJm6xZn//usr/bin/rustdesk: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory` Seems that the RustDesk AppImage doesn´t include libnsl.so.1 so it doesn´t run on Fedora Linux (libnsl.so.1 isn´t part of glibc since Fedora 28). I think the libc6:amd64 Package should be included in https://github.com/rustdesk/rustdesk/blob/master/appimage/AppImageBuilder.yml to fix it.
Author
Owner

@Kingtous commented on GitHub (Aug 10, 2022):

./RustDesk-1.1.10-x86_64_1804.AppImage

-> /tmp/.mount_RustDeJm6xZn//usr/bin/rustdesk: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

Seems that the RustDesk AppImage doesn´t include libnsl.so.1 so it doesn´t run on Fedora Linux (libnsl.so.1 isn´t part of glibc since Fedora 28).

I think the libc6:amd64 Package should be included in https://github.com/rustdesk/rustdesk/blob/master/appimage/AppImageBuilder.yml to fix it.

Thanks for the guide to fix libnsl.so.1 issue. There is also runtime issue found on Fedora, waiting for reply. issue 243 from appimage-builder, seems there are several issues need fixing to make rustdesk appimage run on Fedora.

@Kingtous commented on GitHub (Aug 10, 2022): > `./RustDesk-1.1.10-x86_64_1804.AppImage` > > -> `/tmp/.mount_RustDeJm6xZn//usr/bin/rustdesk: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory` > > Seems that the RustDesk AppImage doesn´t include libnsl.so.1 so it doesn´t run on Fedora Linux (libnsl.so.1 isn´t part of glibc since Fedora 28). > > I think the libc6:amd64 Package should be included in https://github.com/rustdesk/rustdesk/blob/master/appimage/AppImageBuilder.yml to fix it. Thanks for the guide to fix `libnsl.so.1` issue. There is also runtime issue found on Fedora, waiting for reply. [issue 243 from appimage-builder](https://github.com/AppImageCrafters/appimage-builder/issues/243), seems there are several issues need fixing to make rustdesk appimage run on Fedora.
Author
Owner

@cooperbang commented on GitHub (Aug 10, 2022):

Maybe the other issues are related to missing wayland support?

Look here: https://github.com/rustdesk/rustdesk/issues/56

Does the AppImage run on Wayland if you start it with GDK_BACKEND=x11?

-> GDK_BACKEND=x11 ./RustDesk-1.1.10-x86_64_1804.AppImage

@cooperbang commented on GitHub (Aug 10, 2022): Maybe the other issues are related to missing wayland support? Look here: https://github.com/rustdesk/rustdesk/issues/56 Does the AppImage run on Wayland if you start it with GDK_BACKEND=x11? -> `GDK_BACKEND=x11 ./RustDesk-1.1.10-x86_64_1804.AppImage`
Author
Owner

@andy5995 commented on GitHub (Feb 9, 2023):

I maintain the 0ad appimage. The Atlas map editor uses gtk3. There haven't been any reports of problems with it yet.

To bundle gtk, I use the linuxdeploy gtk plugin

@andy5995 commented on GitHub (Feb 9, 2023): I maintain the [0ad appimage](https://github.com/0ad-matters/0ad-appimage/). The Atlas map editor uses gtk3. There haven't been any reports of problems with it yet. To bundle gtk, I use the [linuxdeploy gtk plugin](https://github.com/linuxdeploy/linuxdeploy-plugin-gtk)
Author
Owner

@norayr commented on GitHub (Mar 22, 2023):

i second this.
i was asked to install rustdesk, and apparently it has so many dependencies that if my distribution does not support it, i just cannot build it.

omg, and vcpkg depends on visual studio, which i won't install! i have my minimalistic system.

appimage would allow any user to just run it. this is must have.

@norayr commented on GitHub (Mar 22, 2023): i second this. i was asked to install rustdesk, and apparently it has so many dependencies that if my distribution does not support it, i just cannot build it. omg, and vcpkg depends on visual studio, which i won't install! i have my minimalistic system. appimage would allow any user to just run it. this is must have.
Author
Owner

@rustdesk commented on GitHub (Mar 22, 2023):

https://github.com/rustdesk/rustdesk/releases/tag/nightly

@rustdesk commented on GitHub (Mar 22, 2023): https://github.com/rustdesk/rustdesk/releases/tag/nightly
Author
Owner

@norayr commented on GitHub (Mar 22, 2023):

omg thank you, somehow i missed it!

alas, right now it doesn't run on my wayland free system:

$ /home/smth/bin/appimages/rustdesk-1.2.0-x86_64.AppImage
/tmp/.mount_rustdeLkNW3N/usr/lib/rustdesk/rustdesk: error while loading shared libraries: libwayland-cursor.so.0: cannot open shared object file: No such file or directory

let me see if i can overcome this easily. not sure.

@norayr commented on GitHub (Mar 22, 2023): omg thank you, somehow i missed it! alas, right now it doesn't run on my wayland free system: ``` $ /home/smth/bin/appimages/rustdesk-1.2.0-x86_64.AppImage /tmp/.mount_rustdeLkNW3N/usr/lib/rustdesk/rustdesk: error while loading shared libraries: libwayland-cursor.so.0: cannot open shared object file: No such file or directory ``` let me see if i can overcome this easily. not sure.
Author
Owner

@norayr commented on GitHub (Mar 22, 2023):

i mean it would be great if the appimage just contained everything required to start it.

@norayr commented on GitHub (Mar 22, 2023): i mean it would be great if the appimage just contained everything required to start it.
Author
Owner

@norayr commented on GitHub (Mar 22, 2023):

i installed wayland (emerge wayland) and now i have this:

[2023-03-22 17:01:15] $ /home/smth/bin/appimages/rustdesk-1.2.0-x86_64.AppImage
load librustdesk.so failed
flutter: launch args: []
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to load dynamic library 'librustdesk.so': libpulse-simple.so.0: cannot open shared object file: No such file or directory
#0      _open (dart:ffi-patch/ffi_dynamic_library_patch.dart:11)
#1      new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:22)
#2      PlatformFFI.init (package:flutter_hbb/models/native_model.dart:150)
#3      initEnv (package:flutter_hbb/main.dart:108)
#4      runMainApp (package:flutter_hbb/main.dart:121)
#5      main (package:flutter_hbb/main.dart:102)
<asynchronous suspension>

@norayr commented on GitHub (Mar 22, 2023): i installed wayland (emerge wayland) and now i have this: ``` [2023-03-22 17:01:15] $ /home/smth/bin/appimages/rustdesk-1.2.0-x86_64.AppImage load librustdesk.so failed flutter: launch args: [] [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to load dynamic library 'librustdesk.so': libpulse-simple.so.0: cannot open shared object file: No such file or directory #0 _open (dart:ffi-patch/ffi_dynamic_library_patch.dart:11) #1 new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:22) #2 PlatformFFI.init (package:flutter_hbb/models/native_model.dart:150) #3 initEnv (package:flutter_hbb/main.dart:108) #4 runMainApp (package:flutter_hbb/main.dart:121) #5 main (package:flutter_hbb/main.dart:102) <asynchronous suspension> ```
Author
Owner

@norayr commented on GitHub (Mar 22, 2023):

i believe it'll be solved if you include more stuff (libs?) in the appimage.

@norayr commented on GitHub (Mar 22, 2023): i believe it'll be solved if you include more stuff (libs?) in the appimage.
Author
Owner

@norayr commented on GitHub (Mar 22, 2023):

and thank you for the fast reply and attention.

@norayr commented on GitHub (Mar 22, 2023): and thank you for the fast reply and attention.
Author
Owner

@norayr commented on GitHub (Mar 29, 2023):

ok i guess this is better? with today's build i get:

*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
Aborted

i guess redhat's comment here is relevant (and not only for redhat like systems):

It's the responsibility of application vendors to make sure alternatives are available in their code (such as using epoll/libevents) to select() what's limited by the FD_SETSIZE in order to make their application more flexible and robust.
@norayr commented on GitHub (Mar 29, 2023): ok i guess this is better? with today's build i get: ``` *** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated Aborted ``` i guess [redhat's comment here](https://access.redhat.com/solutions/488623) is relevant (and not only for redhat like systems): ``` It's the responsibility of application vendors to make sure alternatives are available in their code (such as using epoll/libevents) to select() what's limited by the FD_SETSIZE in order to make their application more flexible and robust. ```
Author
Owner

@norayr commented on GitHub (Mar 29, 2023):

omg, i ran it again and it seems to run.

yes it runs!

@norayr commented on GitHub (Mar 29, 2023): omg, i ran it again and it seems to run. yes it runs!
Author
Owner

@norayr commented on GitHub (Mar 29, 2023):

interesting, it was not able to connect to the relay server from my linux machine, but rustdesk that runs in windows vm that runs on my machine was able to connect.

@norayr commented on GitHub (Mar 29, 2023): interesting, it was not able to connect to the relay server from my linux machine, but rustdesk that runs in windows vm that runs on my machine was able to connect.
Author
Owner

@norayr commented on GitHub (Jun 8, 2023):

i downloaded latest nightly and every time i run it i have

*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
Aborted
@norayr commented on GitHub (Jun 8, 2023): i downloaded latest nightly and every time i run it i have ``` *** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated Aborted ```
Author
Owner

@rustdesk commented on GitHub (May 2, 2024):

@probonopd Apploglize for bothering you again. I have a silly question, I have search around, but failed to get answer.

In rustdesk, we need to call itself to spawn a new process when there is a connection. But with AppImage, rustdesk can not spawn new process of itself. I have a experiment as below, may be it is the reason.

image

I guess I can use APPIMAGE env to start the process, but this way is too slow.

Do you have any suggestion about this? ARGV0 can work?

https://github.com/AppImage/AppImageKit/issues/1100

@rustdesk commented on GitHub (May 2, 2024): @probonopd Apploglize for bothering you again. I have a silly question, I have search around, but failed to get answer. In rustdesk, we need to call itself to spawn a new process when there is a connection. But with AppImage, rustdesk can not spawn new process of itself. I have a experiment as below, may be it is the reason. ![image](https://github.com/rustdesk/rustdesk/assets/71636191/d80c0df9-733c-492a-bfb2-d07883df00ad) I guess I can use APPIMAGE env to start the process, but this way is too slow. Do you have any suggestion about this? ARGV0 can work? https://github.com/AppImage/AppImageKit/issues/1100
Author
Owner

@probonopd commented on GitHub (May 2, 2024):

In rustdesk, we need to call itself to spawn a new process when there is a connection.

When that happens, is the original process still running until the user quits the application?
The AppImage runtime unmounts the AppImage as soon as the originally launched process (AppRun) exits.

@probonopd commented on GitHub (May 2, 2024): > In rustdesk, we need to call itself to spawn a new process when there is a connection. When that happens, is the original process still running until the user quits the application? The AppImage runtime unmounts the AppImage as soon as the originally launched process (AppRun) exits.
Author
Owner

@rustdesk commented on GitHub (May 2, 2024):

Yes, the original process still keep running. It is ok to kill the new spawned process when AppRun exits.

@rustdesk commented on GitHub (May 2, 2024): Yes, the original process still keep running. It is ok to kill the new spawned process when AppRun exits.
Author
Owner

@probonopd commented on GitHub (May 2, 2024):

How are you spawning the process? Try to execute AppRun (manually) for a second time from the mounted AppImage - does that work?

@probonopd commented on GitHub (May 2, 2024): How are you spawning the process? Try to execute `AppRun` (manually) for a second time from the mounted AppImage - does that work?
Author
Owner

@rustdesk commented on GitHub (May 2, 2024):

How are you spawning the process?

It is called like this
image

Try to execute AppRun (manually) for a second time from the mounted AppImage - does that work?

I am looking for a solution like this, could you give me a hint of how to do this ? I really do not want to use APPIMAGE env to mount again to run.

@rustdesk commented on GitHub (May 2, 2024): > How are you spawning the process? It is called like this ![image](https://github.com/rustdesk/rustdesk/assets/71636191/ab5efd93-f729-4665-a888-85f0f3b05e37) > Try to execute `AppRun` (manually) for a second time from the mounted AppImage - does that work? I am looking for a solution like this, could you give me a hint of how to do this ? I really do not want to use `APPIMAGE` env to mount again to run.
Author
Owner

@rustdesk commented on GitHub (May 2, 2024):

@probonopd I have figured out the problem, it is my mistake. Thank you very much.

@rustdesk commented on GitHub (May 2, 2024): @probonopd I have figured out the problem, it is my mistake. Thank you very much.
Author
Owner

@probonopd commented on GitHub (May 2, 2024):

Glad you found a solution. Happy to help!

@probonopd commented on GitHub (May 2, 2024): Glad you found a solution. Happy to help!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rustdesk-rustdesk#414
No description provided.