Random black screen during normal use (kwin_wayland)

Support Graphics & Display
,
1

Hi,

since the 26.0 update and the change from XOrg to Wayland I have random black screens. The open programs and input devices continue to work, but the screens are black. It happens randomly, sometimes when I use Firefox, sometimes when I’m gaming. Sometime multiple times a day and sometimes 1 or 2 days without. Only a restart of the computer helps.

Inside the journal I found many errors from kwin_wayland. Below is an snippet. The messages repeat themselves over thousands of lines (several thousand messages per second).

I tried the video-nvidia-575xx and video-nvidia-570xx driver, but the problem occurs with both.
Also a reinstall of Manjaro about 3 weeks ago didn’t solve the problem.

inxi --full --admin --filter --width 
System:
  Kernel: 6.18.8-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
    root=UUID=f283e832-e80d-4c20-abcb-24bc267d4cc0 rw quiet apparmor=1
    security=apparmor splash resume=UUID=ec802e12-2d56-485a-b112-38bb539ed882
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.5.5 tk: Qt v: N/A info: frameworks v: 6.22.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-F GAMING v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 6223 date: 03/22/2024
Battery:
  Device-1: wacom_battery_0 model: Wacom Intuos BT M serial: N/A charge: 100%
    status: discharging
CPU:
  Info: model: AMD Ryzen 5 5600 bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201211
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1750 min/max: 566/4471 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1750 2: 1750 3: 1750
    4: 1750 5: 1750 6: 1750 7: 1750 8: 1750 9: 1750 10: 1750 11: 1750 12: 1750
    bogomips: 83994
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: ASUSTeK driver: nvidia
    v: 570.211.01 alternate: nouveau,nova_core,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-11; EOL~2026-12-xx) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: DVI-D-1,HDMI-A-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 09:00.0
    chip-ID: 10de:1b80 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch d-rect: 3840x1080 display-ID: 0
  Monitor-1: DVI-D-1 pos: primary,left model: Asus VG248 serial: <filter>
    built: 2018 res: mode: 1920x1080 hz: 100 scale: 100% (1) dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  Monitor-2: HDMI-A-1 pos: right model: VU249CFE serial: <filter> built: 2023
    res: mode: 1920x1080 hz: 100 scale: 100% (1) dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.211.01
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
    memory: 7.81 GiB display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 1080 driver: nvidia v: 570.211.01
    device-ID: 10de:1b80 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 09:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASUSTeK 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: Logitech V20 portable speakers (USB powered)
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 5-2:3 chip-ID: 046d:0a04 class-ID: 0300
  API: ALSA v: k6.18.8-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 4.57 TiB used: 1.14 TiB (25.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 44.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD1003FZEX-00K3CA0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A01 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD1003FZEX-00K3CA0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A01 scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 vendor: Intenso model: SSD size: 953.87 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 4A0 scheme: GPT
Partition:
  ID-1: / raw-size: 944.77 GiB size: 928.87 GiB (98.32%) used: 67.72 GiB (7.3%)
    fs: ext4 dev: /dev/sdc2 maj-min: 8:34
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 328 KiB (0.1%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdc3 maj-min: 8:35
Sensors:
  System Temperatures: cpu: 35.0 C mobo: 32.0 C
  Fan Speeds (rpm): cpu: 0 case-1: 0 case-2: 0 case-3: 507
  Power: 12v: 11.97 5v: N/A 3.3v: N/A vbat: N/A
Info:
  Memory: total: 32 GiB available: 31.25 GiB used: 3.84 GiB (12.3%)
  Processes: 310 Power: uptime: 50m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Packages: 1413 pm: pacman pkgs: 1386 libs: 366 tools: pamac pm: flatpak
    pkgs: 27 Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.40
journalctl --boot=-1 --priority=3 --catalog --no-pager (Snippet) 
Feb 23 19:25:18 workbench kernel: NVRM: Xid (PCI:0000:09:00): 32, pid=1055, name=kwin_wayland, Channel ID 000000cc intr 00040000
Feb 23 19:25:18 workbench kernel: NVRM: Xid (PCI:0000:09:00): 32, pid=1055, name=kwin_wayland, Channel ID 000000cc intr 00040000
Feb 23 19:25:18 workbench kwin_wayland[1055]: Create Context failed "EGL_BAD_CONTEXT"
Feb 23 19:25:18 workbench kwin_wayland[1055]: QRhiGles2: Failed to create temporary context
Feb 23 19:25:18 workbench kwin_wayland[1055]: QRhiGles2: Context is lost.
Feb 23 19:25:18 workbench kwin_wayland[1055]: Failed to create RHI (backend 2)
Feb 23 19:25:18 workbench kwin_wayland[1055]: QQuickRenderControl: Failed to initialize QRhi
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not make egl context current! EGL_BAD_CONTEXT
Feb 23 19:25:18 workbench kwin_wayland[1055]: Libinput: event4  - Logitech G403 Prodigy Gaming Mouse: client bug: event processing lagging behind by 53ms, your system is too slow
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not make egl context current! EGL_BAD_CONTEXT
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not make egl context current! EGL_BAD_CONTEXT
Feb 23 19:25:18 workbench kwin_wayland[1055]: EglGbmLayerSurface::renderTestBuffer: failed to make opengl context current
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not make egl context current! EGL_BAD_CONTEXT
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not delete framebuffer because no context is current
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not delete texture because no context is current
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not delete framebuffer because no context is current
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not delete texture because no context is current
Feb 23 19:25:18 workbench kwin_wayland[1055]: Could not make egl context current! EGL_BAD_CONTEXT
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
Feb 23 19:25:18 workbench kwin_wayland[1055]: generating OpenGL texture handle failed
mhwd -li -d 
   NAME:        video-nvidia-570xx
   ATTACHED:    PCI
   VERSION:     2025.09.29
   INFO:        Closed source NVIDIA 570xx drivers for linux.
   PRIORITY:    5
   FREEDRIVER:  false
   DEPENDS:     -
   CONFLICTS:   video*nvidia* 
   CLASSIDS:    0300 0302 
   VENDORIDS:   10de
2

A few days ago the 580xx driver was added to the repositories, apparently Nvidia has been able to stabilise it, and @philm have added it to the repositories.

If you want to install it you will need to do so manually (optionally use the open variant)

sudo pacman -Syu linux618-nvidia-580xx[-open]
3

linux618-nvidia-580xx is not available … at least for stable branch.
linux618-nvidia-open is 590 and not compatible.
The 580 dkms drivers you showed here are also unavailable for me.

4

Same here, no 580 on stable, but there is nvidia-580xx-dkms on AUR if that is acceptable to you, you just need the kernel headers(linux-headers-meta) installed for dkms to work.

5

My mistake - accept my apology - they have not yet reached stable branch.

 $ mbn info linux618-nvidia-580xx -q
Branch         : unstable
Name           : linux618-nvidia-580xx
Version        : 580.126.18-1
Repository     : extra
Build Date     : Sun 22 Feb 2026 00:19:45 
Packager       : Mark Wagie <mark@manjaro.org>

So it is necessary to switch to unstable branch to take advantage.

sudo pacman-mirrors -aSunstable

Then sync the relevant package - the example uses pre-built modules for Linux 6.18

sudo pacman -Syu linux618-nvidia-580xx
6

No problem :slightly_smiling_face:

I think I will wait until it’s released in the stable branch. Currently, it is not a severe problem.
Or I try the dkms package from the AUR on the weekend. Thx @SamKook for the hint.

I will let you know what happened.

1 Like
7

I’ve been trying out the nvidia-580xx driver (580.142) in the stable branch for a few days now. Unfortunately, I can only say that the problem still exists. Until now two times black screen in different situations.

The 580xx-open driver I can’t get to work. The boot process ends with a black screen. Is there anything else to keep in mind here? Additional required packages etc.?

It’s a bit confusing that the drivers can’t be installed via mhwd or the Manjaro Settings Manager because there aren’t listed there.

8

You might want to check if the nvidia framebuffer is enabled :

sudo cat /sys/module/nvidia_drm/parameters/fbdev

The previous command should return Y if it is enabled.

Otherwise, the nvidia journal might show additional clues :

journalctl --reverse --grep=nvidia
1 Like