I was having a zoom call with my team members. When I turned on my screen share and selected a window that I want to share, people told me that I'm rapidly switching between my windows. However, I wasn't switching between windows and I didn't experience anything weird on my screen. My system is up to date and this is my first time making a zoom call on garuda linux. Is this a common issue? How do I fix it?
Hi there, welcome to the community.
I think that I felt same thing on KDE while recording the screen with most of screen recorders. This is just because high system demands of KDE.
So show your inxi, refer to Reporting bugs | Garuda Linux wiki
Also, try different DE. Using lightweight DE, like GNOME/XFCE/LXQT may solve the issue.
Hi, you can try to to deactivate the composer with ALT+Shift+F12 or change from Open GL3.1 to Xrender. I have the same problem with Lenovo ideapad 3.
Describe the problem
When I turn on my screen-share during a zoom call and select a window that I want to share, people on my call tell me that I'm rapidly switching between my windows. However, I am not switching between windows and I don't experience any window-switching on my screen.
OS: Garuda linux dragonized KDE
Status: up-to-date (last update: 03:00 4/29/2021)
inxi -Fxxxza output:
System: Kernel: 5.11.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.0 parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=61206066-bf86-4eca-a2ae-ba25a5ebf145 rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 loglevel=3 Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux Machine: Type: Laptop System: LENOVO product: 20UN0007US v: ThinkPad X1 Nano Gen 1 serial: <filter> Chassis: type: 10 serial: <filter> Mobo: LENOVO model: 20UN0007US v: SDK0J40697 WIN serial: <filter> UEFI: LENOVO v: N2TET61W (1.39 ) date: 02/08/2021 Battery: ID-1: BAT0 charge: 48.4 Wh (100.0%) condition: 48.4/48.2 Wh (100.3%) volts: 13.1 min: 11.6 model: Celxpert 5B10W13964 type: Li-poly serial: <filter> status: Full cycles: 3 Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master serial: <filter> charge: 100% (should be ignored) rechargeable: yes status: Discharging CPU: Info: Quad Core model: 11th Gen Intel Core i5-1130G7 bits: 64 type: MT MCP arch: Tiger Lake family: 6 model-id: 8C (140) stepping: 1 microcode: 6E cache: L2: 8 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28876 Speed: 2969 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 2969 2: 3865 3: 3395 4: 3962 5: 3672 6: 3716 7: 3947 8: 3758 Vulnerabilities: Type: itlb_multihit status: Not affected 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 and seccomp 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: Intel vendor: Lenovo driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:9a40 class-ID: 0300 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 3-4:3 chip-ID: 04f2:b6ea class-ID: fe01 serial: <filter> Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: intel unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1 Screen-1: 0 s-res: 2160x1350 s-dpi: 96 s-size: 571x357mm (22.5x14.1") s-diag: 673mm (26.5") Monitor-1: eDP1 res: 2160x1350 hz: 60 dpi: 196 size: 280x170mm (11.0x6.7") diag: 328mm (12.9") OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 21.0.3 direct render: Yes Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Lenovo driver: sof-audio-pci alternate: snd_hda_intel,snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:a0c8 class-ID: 0403 Sound Server-1: ALSA v: k5.11.16-zen1-1-zen running: yes Sound Server-2: sndio v: N/A running: no Sound Server-3: JACK v: 0.125.0 running: no Sound Server-4: PulseAudio v: 14.2 running: yes Sound Server-5: PipeWire v: 0.3.26 running: yes Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel port: 3000 bus-ID: 00:14.3 chip-ID: 8086:a0f0 class-ID: 0280 IF: wlp0s20f3 state: up mac: <filter> Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 3-10:4 chip-ID: 8087:0026 class-ID: e001 Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter> Drives: Local Storage: total: 476.94 GiB used: 58.9 GiB (12.3%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN530 SDBPMPZ-512G-1001 size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 21160001 temp: 44.9 C scheme: GPT Partition: ID-1: / raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 58.9 GiB (12.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2 ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 ID-3: /home raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 58.9 GiB (12.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2 ID-4: /var/log raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 58.9 GiB (12.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2 ID-5: /var/tmp raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 58.9 GiB (12.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2 Swap: Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100) ID-1: swap-1 type: zram size: 1.92 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram0 ID-2: swap-2 type: zram size: 1.92 GiB used: 256 KiB (0.0%) priority: 32767 dev: /dev/zram1 ID-3: swap-3 type: zram size: 1.92 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2 ID-4: swap-4 type: zram size: 1.92 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3 ID-5: swap-5 type: zram size: 1.92 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4 ID-6: swap-6 type: zram size: 1.92 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5 ID-7: swap-7 type: zram size: 1.92 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6 ID-8: swap-8 type: zram size: 1.92 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7 Sensors: System Temperatures: cpu: 44.0 C mobo: N/A Fan Speeds (RPM): cpu: 3370 Info: Processes: 328 Uptime: 2h 05m wakeups: 14433 Memory: 15.36 GiB used: 6.41 GiB (41.7%) Init: systemd v: 248 tool: systemctl Compilers: gcc: 10.2.0 clang: 11.1.0 Packages: pacman: 1349 lib: 300 Shell: fish v: 3.2.1 running-in: alacritty inxi: 3.3.04
@grmwmr do not cross post please.
@tbg I did not mean to cross post. I was asked to write a bug report by @Naman . Maybe I misunderstood his message and instead of writing my bug report as a comment to this post or edit the original question, I cross-posted it.
He was meaning to post it here.
@tbg my bad then. thanks for merging the post!
Gnome is more heavy weight. It might just by kwin but same issue also affects me just disable sync in compositing.
Well, in general, I agree. But as Garuda KDE ships Latte, KDE becomes heavier than GNOME.
But @grmwmr just give Gnome / LXQT a shot and see if it helps.
You should try what @MomirVig said, zoom (for linux is awful and) does not like the composer.
If you still want to use the composer during the zoom call (I do) then you should:
- disable blur background (workspace behavior -> desktop effects)
- disable show desktop ( workspace behavior -> screen edges)
even disabling that of al , I experienced a few times when I had to disable/re-enable composer to stop window blinking zoom issue.
I am totally unfamiliar with this type of situation as my computers are relatively decent spec.
What might be worth testing if your meetings are scheduled in advance at a set time is to configure a separate user account for these calls. Strip out all unnecessary things that might slow your system down on this different account.
Turn off your compositor and disable all desktop effects on this user account as well. I assume latte dock can also be enabled/disabled on a per user basis, so I would set this account up using the standard KDE bars rather than latte. This should save a ton of resources with all those things disabled.
As I say I've never had to do this before, so I can't say how well it will work for you. However, it might be worth creating a separate user account to see if this may help with your situation.
8 posts were split to a new topic: Cleaning a thread
@tbg Thanks! My laptop has decent specs. I don't think it was a compute issue. Using xfce as DE fixes this issue.
Thanks @Naman ! Appreciate the help. You were right. I didn't experience any issue when I switched to xfce.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.