Screen goes black whenever i exit fullscreen media

Hi guys, encountering my first real issue with what i think is the DE, whenever i go out of full screen on any form of video media, eg: YT vids, Discord vids or even exclusive fullscreen / fullscreen-borderless games, my screen goes black for a few seconds. No more than 4 seconds, but its starting to annoy me, as far as configurations go im all stock on the DE, only changed my wallpaper. Im running a RTX 4090, could this be an indication? Never troubleshooted on Linux yet, so not sure where to start with something like this.

What’s the output of:

inxi -FGxxz

And, have you tried to replicate this in both Wayland and X11 sessions?

I have not, i don’t quite know how to change sessions on KDE.

  Kernel: 6.9.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
  Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: EndeavourOS base: Arch Linux
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX X670E-A GAMING WIFI v: Rev 1.xx
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 1415
    date: 05/16/2023
  Info: 8-core model: AMD Ryzen 7 7800X3D bits: 64 type: MT MCP arch: Zen 4
    rev: 2 cache: L1: 512 KiB L2: 8 MiB L3: 96 MiB
  Speed (MHz): avg: 3027 high: 4849 min/max: 400/5050 cores: 1: 400 2: 3424
    3: 3229 4: 3662 5: 4658 6: 4465 7: 4838 8: 4849 9: 400 10: 400 11: 400
    12: 400 13: 3687 14: 4849 15: 3938 16: 4848 bogomips: 134460
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Device-1: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 555.58
    arch: Lovelace pcie: speed: 16 GT/s lanes: 16 ports: active: none off: DP-1
    empty: DP-2,DP-3,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2684
  Device-2: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel
    arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports: active: none
    empty: DP-4,HDMI-A-2,Writeback-1 bus-ID: 12:00.0 chip-ID: 1002:164e
    temp: 51.0 C
  Device-3: Logitech StreamCam
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 046d:0893
  Display: wayland server: v: with: Xwayland v: 24.1.0
    compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa dri: radeonsi
    gpu: nvidia,amdgpu display-ID: 0
  Monitor-1: DP-1 res: 3840x2160 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: radeonsi
    device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
    drv: nvidia x11: drv: zink inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
    display-ID: :1.0
  API: Vulkan v: 1.3.279 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2684
  Device-1: NVIDIA AD102 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22ba
  Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 12:00.1 chip-ID: 1002:1640
  Device-3: FIFINE Microphones Microphone
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-2:2 chip-ID: 3142:0686
  Device-4: Walmart AB13X Headset Adapter
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-3:3 chip-ID: 001f:0b21
  Device-5: Logitech StreamCam
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 046d:0893
  Device-6: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6:3 chip-ID: 0b05:1a52
  API: ALSA v: k6.9.7-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.2.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Foxconn driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 09:00.0 chip-ID: 14c3:0616
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-9:6 chip-ID: 0489:e0e2
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
  Local Storage: total: 3.64 TiB used: 139.17 GiB (3.7%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 4000GB
    size: 3.64 TiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 50.9 C
  ID-1: / size: 3.58 TiB used: 138.95 GiB (3.8%) fs: ext4 dev: /dev/nvme0n1p2
  Alert: No swap data was found.
  System Temperatures: cpu: 61.4 C mobo: 44.0 C gpu: amdgpu temp: 51.0 C
  Fan Speeds (rpm): N/A
  Memory: total: 32 GiB note: est. available: 30.49 GiB used: 8.4 GiB (27.5%)
  Processes: 402 Power: uptime: 1h 40m wakeups: 0 Init: systemd v: 256
    default: graphical
  Packages: pm: pacman pkgs: 1074 Compilers: gcc: 14.1.1 Shell: Bash
    v: 5.2.26 running-in: konsole inxi: 3.3.35

Follow the instructions below. Bascially, log out, select Plasma X11/Xorg, log in.

Once done, test it to see if the issue still occurs. If it doesn’t (it probably won’t), then you know it’s very likely a compatibility issue with Wayland and Nvidia.

If it does happen, then we can troubleshoot more.

Whether it still happens or not, please let us know.


Thank you very much for helping me with this! It seems that it was indeed the Wayland session that was causing this, I notice that my display configuration options are much more limited within an X11 session, is this by design? There is also a significant decrease in the overall “smoothness” of the DE, moving windows around for example isnt as smooth, even with the selected 240hz option.

For example, VRR / no adaptive sync or screen tearing options, I do recall reading somewhere a while back that Wayland was much worse on Nvidia cards, and only as of late has it somewhat improved.

Yes, Wayland and Nvidia can be great for some and terrible for others. Wayland brings in some improvements to working with or utilising graphic cards better, but again, because it’s currently hit or miss with Nvidia cards, you may not be able to use it as you want/expect.

It’s getting better, though, so check things out from time to time to see if the issue has been fixed. Specifically, check when you get nvidia, kernel, BIOS, Plasma, or Wayland updates.

Any of those five updates can make a difference, and apart from BIOS updates, you are likely to have multiple updates for them each week.

1 Like

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