Obs-studio when adding a source GUI glitches out

My Google Foo has not helped me figure this out.

When adding a source to OBS Studio the menus glitch out when resizing menu items.
I would post a screen shot but it says because I am new I am not allowed.

I have tested this on different hardware and different Garuda DE's seems to only be a problem with Garuda flavors. Manjaro and EndeavourOS do not seem to suffer from this GUI glitch.

I have tried changing the OBS Studio Theme and that doesn't seem to help either.

Thank you in advanced for any help or ideas!

System:
  Kernel: 5.17.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=638028fd-ad4b-45ea-bb4a-dcdd8da652a1 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3
  Desktop: Cinnamon v: 5.2.7 tk: GTK v: 3.24.33 wm: muffin vt: 7
    dm: LightDM v: 1.30.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X570M Pro4 serial: <superuser required>
    UEFI: American Megatrends v: P3.70 date: 02/23/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 3589 high: 3594 min/max: 2200/4208 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3591 2: 3592
    3: 3587 4: 3589 5: 3584 6: 3591 7: 3593 8: 3581 9: 3591 10: 3588 11: 3594
    12: 3593 bogomips: 86242
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  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
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Retpolines, IBPB: conditional, STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP107GL [Quadro P400] driver: nvidia v: 515.43.04
    alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-05) arch: Pascal pcie: gen: 3 speed: 8 GT/s
    lanes: 16 bus-ID: 09:00.0 chip-ID: 10de:1cb3 class-ID: 0300
  Device-2: USB3.0 HD Audio Capture Video type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 5-1:2 chip-ID: eba4:7588
    class-ID: 0e02 serial: <filter>
  Device-3: A4Tech USB Live camera type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 5-3:4 chip-ID: 09da:2690 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 driver: X: loaded: nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
    s-diag: 1055mm (41.55")
  Monitor-1: DP-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 82
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  Monitor-2: DP-4 pos: right res: 1920x1080 hz: 60 dpi: 82
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.1
    chip-ID: 10de:0fb9 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: USB3.0 HD Audio Capture Video type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 5-1:2 chip-ID: eba4:7588
    class-ID: 0e02 serial: <filter>
  Device-4: A4Tech USB Live camera type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 5-3:4 chip-ID: 09da:2690 class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.17.7-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Drives:
  Local Storage: total: 1.36 TiB used: 590.84 GiB (42.3%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital
    model: WDS100T1X0E-00AFY0 size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 613000WD temp: 47.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
    model: WDS500G1X0E-00AFY0 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 613000WD temp: 46.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 182.14 GiB (39.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
  ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 182.14 GiB (39.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 182.14 GiB (39.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
    used: 182.14 GiB (39.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.54 GiB used: 149 MiB (0.9%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 44 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 34%
Info:
  Processes: 368 Uptime: 5d 5h 21m wakeups: 125 Memory: 15.54 GiB
  used: 3.67 GiB (23.6%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 12.1.0 Packages: pacman: 1495 lib: 353 Shell: fish v: 3.4.1
  default: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.16
Garuda (2.6.3-2):
  System install date:     2022-04-16
  Last full system update: 2022-05-20 ↻
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:            bluetooth-autoconnect.service

Welcome to the community @mexexcellentmike! :slightly_smiling_face:

Your post was edited to add code formatting to your terminal output. You can do this yourself next time by adding three tildes before and after the output
~~~
like this.
~~~

Were you also using Cinnamon on those?

The first thing that comes to mind would be try switching the kernel. I'm guessing Manjaro and EndeavorOS were not running the Zen kernel. Give the LTS kernel a shot:

Fully update the system:

garuda-update

Install the kernel and headers:

sudo pacman -S linux-lts linux-lts-headers

Reboot and select "advanced options" on the grub menu to select the new kernel, then fire up OBS and see how it goes.

3 Likes

BluishHumility,

Thank you for the quick Reply. I will try your suggestions let you know what I find.

Hi BluishHumility,

garuda-update and booting to LTS kernel unfortunately did not make any changes.

With Manjaro and EndeavourOS you are correct I was not running the Zen Kernel.

Thanks again for the suggestions.

Too bad! You never know when you might get lucky with an easy fix.

What version of OBS are you running now? If you are running obs-studio, perhaps you could try obs-studio-git (or vice-versa).

Do you happen to know if you are running the same NVIDIA driver on Garuda as you had on the other systems?

I'm trying to think what other differences could be specific to the Garuda installs like you mentioned...:thinking:...but then again that could be a red herring.

Hopefully someone with more OBS-related experience will chime in.

2 Likes

Or, downgrade to an older version of obs-studio.

3 Likes