Screen share issue on Streaming Apps

Issues & Assistance
1

Here is the Information

System:
Kernel: 6.3.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=945d5778-e926-4d38-b368-0906a3eb7dd5 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.9 wm: kwin_x11 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: A320M-S2H v: N/A serial: N/A
Mobo: Gigabyte model: A320M-S2H-CF v: x.x serial: N/A
UEFI: American Megatrends v: F53 date: 01/05/2021
CPU:
Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics socket: AM4
bits: 64 type: MCP arch: Zen level: v3 note: check built: 2017-19
process: GF 14nm family: 0x17 (23) model-id: 0x11 (17) stepping: 0
microcode: 0x8101016
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
desc: 1x4 MiB
Speed (MHz): avg: 2550 high: 3500 min/max: 1600/3500 boost: enabled
base/boost: 3500/3700 scaling: driver: acpi-cpufreq governor: schedutil
volts: 1.4 V ext-clock: 100 MHz cores: 1: 3500 2: 1600 3: 3500 4: 1600
bogomips: 27947
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]
vendor: Gigabyte driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 07:00.0
chip-ID: 1002:15dd class-ID: 0300 temp: 48.0 C
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: 24HC1QR serial: <filter>
built: 2020 res: 1920x1080 hz: 120 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 600mm (23.6") ratio: 16:9, 15:9
modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.2 renderer: AMD Radeon Vega 8 Graphics
(raven LLVM 15.0.7 DRM 3.52 6.3.6-zen1-1-zen) direct-render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 07:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.3.6-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.71 status: n/a (root, process) 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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp6s0 state: down mac: <filter>
IF-ID-1: enp7s0f3u2 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
Device-1: OPPO RMX2027 driver: rndis_host v: kernel type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:4 chip-ID: 22d9:276a
class-ID: 0a00 serial: <filter>
Report: bt-service: enabled,stopped note: tool can't run
Drives:
Local Storage: total: 585 GiB used: 162.77 GiB (27.8%)
ID-1: /dev/sda maj-min: 8:0 model: SSD 128GB size: 119.24 GiB block-size:
physical: 512 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: XKR temp: 40 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 153d 7h cycles: 1644
read: 3.9 MiB written: 4.4 MiB
ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT3500SC 6
CTB5029G21Y034 size: 465.76 GiB block-size: physical: 512 B logical: 512 B
sata: 2.6 speed: 3.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: A52B temp: 41 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 163d 16h cycles: 2516
Partition:
ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.4 GiB (24.7%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.4 GiB (24.7%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.4 GiB (24.7%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
used: 29.4 GiB (24.7%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 13.59 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.8 C mobo: N/A gpu: amdgpu temp: 47.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 253 Uptime: 6m wakeups: 0 Memory: available: 13.59 GiB
used: 2.34 GiB (17.2%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 1659 libs: 502 tools: octopi,paru Shell: garuda-inxi (sudo)
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
System install date:     2023-06-11
Last full system update: 2023-06-11
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

i was unable to shere my application screen via discord and telegram and most propebly all streaming apps the option was only have that is i need to shere the whole screen of my desktop but when i boot into live usb this problem does't happens and in side the bootable media i can shere my all screen and windows idk what is happenig after update that i cun't shere my application screen here is some screenshots of the related ishu

telegram
telegram1383Ă—916 79.9 KB

discord
discord528Ă—637 24.9 KB

And when i use wayland session it works perfectly but only with help of pipewire also discord is the same as x11 there

Here is the logs of discord from app data

LOGS-appdata

And Here is the logs of discord from Terminal

LOGS

Here is the logs of Telegram From Appdata

LOGS-appdata

And Here is the logs of Telegram from Terminal

LOGS

Here is the my System Config

  1. GTK_MODULES=canberra-gtk-module:appmenu-gtk-module
  2. GTK_USE_PORTAL=1
  3. HOME=/home/alex
  4. JOURNAL_STREAM=8:24612
  5. HG=/usr/bin/hg
  6. KDE_APPLICATIONS_AS_SCOPE=1
  7. KDE_SESSION_VERSION=5
  8. INVOCATION_ID=ddab3d53fe104bc69e71e32216f117f8
  9. KONSOLE_VERSION=230402
  10. STARSHIP_SHELL=fish
  11. KONSOLE_DBUS_SERVICE=:1.131
  12. LANGUAGE=
  13. LC_IDENTIFICATION=en_IN
  14. SHELL=/bin/bash
  15. XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
  16. SHLVL=1
  17. XDG_SEAT=seat0
  18. TERM=xterm-256color
  19. DESKTOP_SESSION=plasma
  20. XCURSOR_SIZE=24
  21. XDG_SESSION_TYPE=x11
  22. XDG_VTNR=1
  23. PROFILEHOME=
  24. STARSHIP_SESSION_KEY=1201418730504957
  25. USER=alex
  26. PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/usr/lib/jvm/default/bin:/usr/bin
  27. /site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
  28. MANPAGER=sh -c 'col -bx | bat -l man -p'
  29. SHELL_SESSION_ID=07fa0285314649799f56d1c833a2bb53
  30. VISUAL=kate
  31. LANG=en_IN
  32. KDE_SESSION_UID=1000
  33. AMD_VULKAN_ICD=RADV
  34. SYSTEMD_EXEC_PID=1229
  35. BROWSER=firedragon
  36. DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
  37. SSH_ASKPASS=/usr/bin/ksshaskpass
  38. XAUTHORITY=/home/alex/.Xauthority
  39. SSH_ASKPASS_REQUIRE=prefer
  40. QT_AUTO_SCREEN_SCALE_FACTOR=0
  41. COLORFGBG=15;0
  42. LC_NUMERIC=en_IN
  43. MOTD_SHOWN=pam
  44. LC_NAME=en_IN
  45. COLORTERM=truecolor
  46. DEBUGINFOD_URLS=https://debuginfod.archlinux.org
  47. XCURSOR_THEME=Sweet-cursors
  48. LOGNAME=alex
  49. XDG_SESSION_ID=1
  50. XDG_SESSION_CLASS=user
  51. PWD=/home/alex
  52. KONSOLE_DBUS_WINDOW=/Windows/1
  53. XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
  54. GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/alex/.gtkrc-2.0:/home/alex/.config/gtkrc-2.0
  55. XDG_SESSION_DESKTOP=KDE
  56. XDG_CURRENT_DESKTOP=KDE
  57. WINDOWID=4194317
  58. XDG_RUNTIME_DIR=/run/user/1000
  59. SESSION_MANAGER=local/alex:@/tmp/.ICE-unix/1164,unix/alex:/tmp/.ICE-unix/1164
  60. MANAGERPID=709
  61. LC_TIME=en_IN
  62. KDE_FULL_SESSION=true
  63. XDG_CONFIG_DIRS=/home/alex/.config/kdedefaults:/etc/xdg
  64. DISPLAY=:0
  65. MAIL=/var/spool/mail/alex
  66. LC_TELEPHONE=en_IN
  67. LC_ADDRESS=en_IN
  68. LC_PAPER=en_IN
  69. UBUNTU_MENUPROXY=1
  70. KONSOLE_DBUS_SESSION=/Sessions/1
  71. LC_MONETARY=en_IN
  72. EDITOR=/usr/bin/micro
  73. GTK_RC_FILES=/etc/gtk/gtkrc:/home/alex/.gtkrc:/home/alex/.config/gtkrc
  74. LC_MEASUREMENT=en_IN
2

your issue is quite strange. I have tried searching for your issue online but it seems people online have been only having issues using wayland to share screen rather than x11.

However, if wayland seems to work for you can totally go for it

sudo pacman -S plasma-wayland-session

will install the required support modules for wayland and then you can reboot and choose wayland on login.

3 Likes
3

but on wayland discord still the same cun't get the popup of pipe wire screen selection menu

4

Hmm :thinking: . Actually I am quite curious how did you test wayland “somewhat” works/solves your issue? Did you install the plasma-wayland-session support to switch between x11 and wayland to see which one works or did you go with a garuda wayfire or sway edition to confirm this?

I am asking because possibly this is just a case of missing dependencies available/preinstalled in other garuda versions and not the fault of display server itself.

Also what does this mean? what is pipe wire screen selection menu? pipe wire is a sound server and is installed in your system already.

1 Like
5

Just for future reference it’s can’t not cun’t :joy:

1 Like
7

its mean when i was in wayland the screen selection tab

8

i mean the window to select the screens

10

Did you reply without reading the message :disappointed:. Re-read it and provide appropriate information to each individual.

2 Likes
11

He has already been warned regarding that by me, Tushar and nico on telegram. He even received admin warn and yet pretends to be oblivious regarding this.

2 Likes
12

pipewire
pipewire1383Ă—994 77.2 KB

i mean this menu from wayland this comes only on wayland session

13

so why don’t you just use wayland, then?

This makes no sense to me (and it seems to any of us)… please try to explain what is still missing in wayland.

2 Likes
14

the problem is that sereen selection widow not comming on wayland sir on discord so on wayland discord is fully useless

15

The Arch Linux wiki says that for Discord, screen sharing doesn't work on Wayland:
https://wiki.archlinux.org/title/Discord#Screen_sharing_on_Wayland

However, it does provide alternatives like using Webcord, or use an OBS virtual camera. Read the wiki link for details.

Btw, you should really install Grammarly or something to help you out with your English spelling and grammar. Ishu and cun't are not real words :((

6 Likes
16

ok i think its fixed now

17

What did you do to fix it? Please go into full detail so that other people who find this topic can take the same steps.

4 Likes
18

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