Chrome Remote Desktop and Garuda

I am very new to Garuda and Linux in general but I wanted to share something that I stumbled across today. Let me first say that I am not sure whether this is a bug or an appropriate behavior that I just did not expect to see...

I installed Chrome Remote Desktop (from the AUR) to my Dr4Gonized installation using the following guide How to Install chrome-remote-desktop on Arch · Victor's Blog . Everything was looking okay through this process. Well, when I rebooted and tested with a CRD session, I could not see any of my icons, panel, or dock from the guest computer. So I rebooted my computer. When it fully started, I could not see my icons, panel, or dock on my host computer. I went round and round with it and I almost reinstalled Garuda on the host but I shut off my guest computer and rebooted my host. When the host garuda machine fully rebooted, my icons, panel, and dock fired back up!

So the only thing that corrects this anomaly for me, is to kill the CRD session on the guest machine, log out of the host, and then come back in. Maybe lots of folks have the answer to this and I am just being a noob, but maybe this info can be useful to someone who reads it.

Regards,

Jeff

First, nobody uses an outdated post from 2 Apr, 2020 .

Why you use proprietary software?

It would be nice if you post your garuda-inxi, too.

2 Likes

SGS,

Thank you for the response. I am not completely happy with CRD but it does work between my company-provided notebook pc that I have restrictions on by our company administrators and a windows machine at my home and this is the main reason why I use it (this activity is legal with the admin dept.). If there is another program that you recommend, I would like to try it. Here is my garuda-inxi

Regards,

Jeff

System:
Kernel: 5.17.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f07ccfee-40f0-4a31-9de0-a05752169b9c rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG Z490 TOMAHAWK (MS-7C80) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.A0
date: 10/19/2021
CPU:
Info: model: Intel Core i7-10700K bits: 64 type: MT MCP arch: Comet Lake
family: 6 model-id: 0xA5 (165) stepping: 5 microcode: 0xEE
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 799 high: 800 min/max: 800/5100 scaling:
driver: intel_pstate governor: powersave cores: 1: 799 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800
14: 800 15: 800 16: 800 bogomips: 121596
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
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: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Micro-Star MSI driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1
bus-ID: 01:00.0 chip-ID: 1002:67df class-ID: 0300
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.65x11.22")
s-diag: 735mm (28.92")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Viewteck GNV29CB built: 2020
res: 2560x1080 hz: 60 dpi: 96 gamma: 1.2 size: 680x288mm (26.77x11.34")
diag: 738mm (29.1") modes: max: 2560x1080 min: 720x400
OpenGL: renderer: AMD Radeon RX 570 Series (polaris10 LLVM 13.0.1 DRM
3.44 5.17.4-zen1-1-zen)
v: 4.6 Mesa 22.1.1 direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aaf0 class-ID: 0403
Sound Server-1: ALSA v: k5.17.4-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 16.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 4000 bus-ID: 03:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp3s0 state: down mac: <filter>
Device-3: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter
driver: rtl8821ae v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8812 class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek type: USB driver: btusb v: 0.8 bus-ID: 1-1:2
chip-ID: 0bda:a725 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 931.51 GiB used: 10.48 GiB (1.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7
temp: 40.9 C scheme: GPT
Partition:
ID-1: / raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 10.45 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 29.5 MiB (30.7%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 10.45 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-4: /var/log raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 10.45 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 10.45 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.54 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 27.8 C pch: 40.0 C mobo: N/A gpu: amdgpu
temp: 54.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 214
Info:
Processes: 352 Uptime: 16m wakeups: 0 Memory: 15.54 GiB
used: 2.73 GiB (17.6%) Init: systemd v: 251 tool: systemctl Compilers:
gcc: 12.1.0 Packages: pacman: 1137 lib: 291 Shell: fish v: 3.4.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.16
Garuda (2.6.3-2):
System install date:     2022-05-05
Last full system update: 2022-06-06 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

Something is odd about the timeline here. You have mentioned you have been rebooting during your troubleshooting and we can see you have pulled down an update today, but the fact that you are still on 5.17.4 makes it appear as though you have not rebooted this device in weeks.

Most of us have been running 5.18 for a couple weeks now, or nearly. A forum search for 5.17.4-zen reveals people running were running it all the way back in late April.

Are you describing troubleshooting that you did weeks ago? Or are you holding back your kernel for some reason? If you are updating and rebooting you should be on a newer kernel by now.

2 Likes

I am not willingly or knowingly holding back a kernel update (I admit I dont know how to do this). Is there a way I should do this manually? I did try to restore a snapper failsafe image today. Would that be why?

Yes, restoring a snapshot can bring you back to an earlier kernel. That update you pulled down today must have been large--cross your fingers when you reboot. :crossed_fingers:

I take it from the fact that you restored to a snapshot that something else is wrong with your system (besides the broken CRD environment)?

3 Likes

The reboot went fine, thankfully...

Yes. CRD's issues were why I restored the snapshot and that was prior to the post and prior to my consideration to perform a reinstallation. And I spoke too soon also, apparently. This is what I am seeing when my host machine is logged in and my guest machine 'rings in'

Here is my Android screenshot of the Garuda host. No panel or dock:

And here is my updated garuda-inxi

System:
Kernel: 5.18.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f07ccfee-40f0-4a31-9de0-a05752169b9c rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG Z490 TOMAHAWK (MS-7C80) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.A0
date: 10/19/2021
CPU:
Info: model: Intel Core i7-10700K bits: 64 type: MT MCP arch: Comet Lake
family: 6 model-id: 0xA5 (165) stepping: 5 microcode: 0xF0
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1299 high: 4206 min/max: 800/5100 scaling:
driver: intel_pstate governor: powersave cores: 1: 2412 2: 4206 3: 800
4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 3767 12: 801
13: 800 14: 800 15: 800 16: 800 bogomips: 121596
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
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: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Micro-Star MSI driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1
bus-ID: 01:00.0 chip-ID: 1002:67df class-ID: 0300
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.65x11.22")
s-diag: 735mm (28.92")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Viewteck GNV29CB built: 2020
res: 2560x1080 hz: 60 dpi: 96 gamma: 1.2 size: 680x288mm (26.77x11.34")
diag: 738mm (29.1") modes: max: 2560x1080 min: 720x400
OpenGL: renderer: AMD Radeon RX 570 Series (polaris10 LLVM 13.0.1 DRM
3.46 5.18.1-zen1-1-zen)
v: 4.6 Mesa 22.1.1 direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aaf0 class-ID: 0403
Sound Server-1: ALSA v: k5.18.1-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 16.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 4000 bus-ID: 03:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp3s0 state: down mac: <filter>
Device-3: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter
driver: rtl8821ae v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8812 class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek type: USB driver: btusb v: 0.8 bus-ID: 1-1:2
chip-ID: 0bda:a725 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 931.51 GiB used: 19.93 GiB (2.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7
temp: 40.9 C scheme: GPT
Partition:
ID-1: / raw-size: 296.1 GiB size: 296.1 GiB (100.00%) used: 19.9 GiB (6.7%)
fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 29.5 MiB (30.7%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 19.9 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-4: /var/log raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 19.9 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 296.1 GiB size: 296.1 GiB (100.00%)
used: 19.9 GiB (6.7%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.54 GiB used: 1.8 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 27.8 C pch: 41.0 C mobo: N/A gpu: amdgpu
temp: 55.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 474
Info:
Processes: 380 Uptime: 5m wakeups: 0 Memory: 15.54 GiB
used: 2.39 GiB (15.4%) Init: systemd v: 251 tool: systemctl Compilers:
gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1488 lib: 356 Shell: fish
v: 3.4.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.16
Garuda (2.6.3-2):
System install date:     2022-06-06
Last full system update: 2022-06-06
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

And the guest machine will timeout in CRD whenever the host garuda machine is not logged into to it's computer session.

I am sorry I did not test this thoroughly prior to my post. I thought the post would be helpful. I guess not...

Thanks Guys

Restore with garuda-assistant.

BTW, we trust you, no picture needed.

1 Like

It does appear that there is something where they would normally show, so is this due to CRD not supporting the blur or other compositing feature in use by the desktop?

2 Likes

Why not trying with the compositor disabled at all?

2 Likes

I'm sorry for the delayed response. The background is lucid and not blurred.

Thanks SGS. I will do as you suggest...

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.