Page 1 of 1
Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 12:24 am
by kd4e
I observed one version of RustDesk in Popular Apps in MXPI - with no version number.
A second version appears in Flatpaks - an older version 1.3.7.
I tried both and neither offers the 'gear' - where settings may be adjusted.
Is it possible to update the non-Flatpak one to the current 1.3.8 version, in MXPI, please?
Note: I'm using this on a Panasonic Toughbook Tablet FZ-G1 with MX v. 25.02.01mx23 (per "apt policy mx-system")
Thanks.
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 2:56 am
by Eadwine Rose
Moved to package requests.
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 3:13 am
by Stevo
It's not a request, they just are asking about rustdesk.
Note: I'm using this on a Panasonic Toughbook Tablet FZ-G1 with MX v. 25.02.01mx23 (per "apt policy mx-system")
That's just the version of the mx-system package, which is not related to the actual MX release. You get that in QSI, first section, as "Distro".
I don't know if MXPI gets their deb, but you can tell us with the result of "apt policy rustdesk". You can also manually download a deb or AppImage from
https://github.com/rustdesk/rustdesk/releases/tag/1.3.8
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 3:21 am
by Eadwine Rose
"Is it possible to update the non-Flatpak one to the current 1.3.8 version, in MXPI, please?"
I went off of that one.
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 7:08 am
by dolphin_oracle
the popular apps entry pulls from rustdesk directly. the intent is whatever their latest version is, but it does some website scraping to figure it out at download time.
the deb is downloaded and installed manually. hence no version info (most popular app entries do not have version info because repos are used until the entries are chosen, if used at all).
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 9:36 am
by kd4e
OK, thanks, that's very good to know!
I'm not sure, then, why it's not playing nicely with MX.
It works fine on my Android phone (using the Androind-alternative, GrapheneOS),
and on the RaspberryPi (using their 64bit recommended OS).
I'll try installing it, again ... perhaps it just didn't install cleanly.
Thanks.
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 12:31 pm
by Stevo
Maybe they left some dependency out of the deb, or it's only recommended. If you have the deb, what does "apt show rustdesk" show in the terminal? (Copypaste the output here, please)
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 6:03 pm
by fehlix
kd4e wrote: Mon Mar 24, 2025 12:24 am
I observed one version of RustDesk in Popular Apps in MXPI - with no version number.
Yes, as already indicated: means latest version available.
kd4e wrote: Mon Mar 24, 2025 12:24 am
Is it possible to update the non-Flatpak one to the current 1.3.8 version, in MXPI, please?
Also already mentioned: Not always but very often the package version relates 1-to-1 to the app version.
So in this case any of the installed deb package manager would give you the installed deb-package version.
Or as already mentioned on CLI:
would give
Code: Select all
apt show rustdesk
Package: rustdesk
Version: 1.3.8
Status: install ok installed
Priority: optional
Section: net
Maintainer: rustdesk <info@rustdesk.com>
Installed-Size: unknown
Depends: libgtk-3-0, libxcb-randr0, libxdo3, libxfixes3, libxcb-shape0, libxcb-xfixes0, libasound2, libsystemd0, curl, libva2, libva-drm2, libva-x11-2, libgstreamer-plugins-base1.0-0, libpam0g, gstreamer1.0-pipewire
Recommends: libayatana-appindicator3-1
Homepage: https://rustdesk.com
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: A remote control software.
Now to the question why it may behave not as you assumed it should:
You have opted to not provide QSI, so we may needlessly ask some further questions:
What would this command show:
In case it would not look like this:
Code: Select all
systemctl is-system-running
running
this would indicate, that the software you are trying to use, was made such
that it intentionally using (but unnecessarily) some nifty features (user "daemon" alike services)
only available when booting with systemd as init system.
And in case it would show "running" something else is out of order with your system.
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Mon Mar 24, 2025 6:54 pm
by kd4e
UPDATE: We solved the problem by tinkering with Onboard and RustDesk settings, as well as a RaspberryPi setting, to get everything to play nicely together.
Thanks.
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Wed May 07, 2025 4:23 pm
by kd4e
We're back to this problem ...
Note 1: Rustdesk v1.3.8 (QSI at bottom).
Note 2: I'm running Rustdesk as a Client on my MX Linux laptop. The Rustdesk Server is on a RaspberryPi 4b running their 64bit OS.
(Both are on the same network. Both are connected to the router via wired LAN.)
Rustdesk played nicely with Settings changed to Scale Adaptive and Codec AV1 set ... once.
(Settings were changed to try to get past the black screen.)
Now it keeps forcing Wayland - and producing a black screen (streaming audio works).
I installed gdm3 and created /etc/gdm and /etc/gdm/custom.conf
Then added "WaylandEnable=false" to custom.conf
Rebooted my MX Linux laptop and same problem.
LightDM is the default graphical login manager.
This is a non-systemD MX Linux and I understand that gdm prefers systemD.
What might I be missing, please?
Thanks!
Code: Select all
System:
Kernel: 6.14.5-1-liquorix-amd64 [6.14-7~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.14.5-1-liquorix-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.6_ahs_x64 Libretto May 19 2024 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Acer product: Aspire A315-24PT v: V1.11 serial: <superuser required>
Mobo: MDC model: Herbag_MDU v: V1.11 serial: <superuser required> UEFI: Insyde v: 1.11
date: 07/07/2023
Battery:
ID-1: BAT1 charge: 50.9 Wh (100.0%) condition: 50.9/47.8 Wh (106.4%) volts: 12.6 min: 11.2
model: LGC AP18C8K type: Li-ion serial: <filter> status: full
CPU:
Info: model: AMD Ryzen 5 7520U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
model-id: 0xA0 (160) stepping: 0 microcode: 0x8A00008
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1227 high: 2800 min/max: 900/2800 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 838 2: 900 3: 838 4: 900 5: 1397 6: 2800
7: 1047 8: 1100 bogomips: 44718
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP: always-on; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Mendocino vendor: Acer Incorporated ALI driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: HDMI-A-1 off: eDP-1 empty: DP-1,DP-2,Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:1506
class-ID: 0300 temp: 42.0 C
Device-2: Chicony ACER HD User Facing type: USB driver: uvcvideo bus-ID: 5-1:2
chip-ID: 04f2:b79c class-ID: fe01 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: xfwm v: 4.20.0
driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: primary model: Acer CB272U serial: <filter>
built: 2021 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 597x336mm (23.5x13.23")
diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
Monitor-2: eDP-1 mapped: eDP note: disabled model: ChiMei InnoLux 0x154c built: 2020
res: 1920x1080 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
modes: max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: AMD Radeon 610M (radeonsi raphael_mendocino
LLVM 15.0.6 DRM 3.61 6.14.5-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: AMD Rembrandt Radeon High Definition Audio vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1
chip-ID: 1002:1640 class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Acer Incorporated ALI
driver: snd_pci_acp6x v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt,
snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 03:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h/19h/1ah HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.14.5-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter vendor: Lite-On
driver: mt7921e v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 02:00.0
chip-ID: 14c3:7961 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 4-1.3:3
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Lite-On Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-2:2 chip-ID: 04ca:3802
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: N/A rfk-block: hardware: no
software: yes address: <filter>
Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
Local Storage: total: 476.94 GiB used: 76.46 GiB (16.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD PC SN740 SDDQNQD-512G-1014
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 73101100 temp: 29.9 C scheme: GPT
Partition:
ID-1: / raw-size: 476.69 GiB size: 468.13 GiB (98.21%) used: 76.46 GiB (16.3%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 49.0 C mobo: 40.0 C gpu: amdgpu temp: 41.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2361 pm: dpkg pkgs: 2356 libs: 1177 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 5
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Info:
Processes: 348 Uptime: 1h 2m wakeups: 3253 Memory: 14.87 GiB used: 4.7 GiB (31.6%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Wed May 07, 2025 7:34 pm
by kd4e
Would I be likely to break anything if I upgraded the v1.3.8 install (on my MX laptop) to v1.3.9 like this?
(In order to match versions with 1.3.9 on the Raspberry Pi.)
Code: Select all
wget https://github.com/rustdesk/rustdesk/releases/tag/nightly/rustdesk-1.3.9-x86_64.deb
sudo apt install -fy ./rustdesk-1.3.9-x86_64.deb
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Wed May 07, 2025 7:37 pm
by oops
Re: Which RustDesk in MXPI & Version Upgrade?
Posted: Wed May 07, 2025 7:44 pm
by kd4e
They are similar, like Teamview, and some others.
I had some problems with Anydesk and Rustdesk had been working well.
I'm hoping it's just the version mismatch.
(Their Nightly Build is at 1.4.x but the Raspberry Pi install via Pi-Apps is 1.3.9)
Re: Which RustDesk in MXPI & Version Upgrade? [Solved]
Posted: Thu May 08, 2025 10:43 am
by kd4e
UPDATE: I can connect (using Rustdesk Client) to another Pi, running Rustdesk v1.3.9, then connect to the Pi that's running the scanner software (using the Brave browser) - and it works correctly.
Very odd ...