Xwayland app is black after unlock in wayland

Dingisoul · 2023-12-25 09:15:07

Description

I have a issue regarding xorg-xwayland. My xwayland application appears entirely black after resuming (unlock) from idle mode. Conversely, other native Wayland applications display correctly. I'm using Sway as my window manager, Swaylock for locking my screen, and Swayidle for managing idle mode. Here are the versions of these applications:

extra/xorg-xwayland 23.2.3-1 (920.6 KiB 2.2 MiB) [xorg] (Installed)
extra/swayidle 1.8.0-1 (17.9 KiB 40.2 KiB) (Installed)
extra/swaylock 1.7.2-1 (31.4 KiB 90.3 KiB) (Installed)
aur/sway-im-git r7220.bf2b79b2845a-3 (+3 0.43) (Installed)

The following codes are my configuration's lines of idle in sway config file.

exec swayidle -w \
         timeout 300 'swaylock -f -c 000000' \ 
         timeout 600 'swaymsg "output * dpms off"' resume 'swaymsg "output * dpms on"' \
         before-sleep 'swaylock -f -c 000000'

Images

The image below illustrates what takes place
https://s3.bmp.ovh/imgs/2023/12/25/cd0c2dc41d6c1a49.png

Other

The recent occurrence of this issue, involving displaying black windows in xwayland apps after unlocking, surfaced about two weeks ago following a regular day's software update. Before it, there is similar issue: glitch in xwayland apps after unlocking which could be "slightly" solved using full screen to refresh the window.

Initially, I suspected that the problem might stem from insufficient space in the swap file compared to the available RAM. This could potentially lead to data loss in the memory when the system is locked. To address this issue, I increased the size of the swap file, making it larger than my memory. Despite this change, the black screen in xwayland apps persists black after unlocking.

To further investigate the problem, I read through related posts on the Arch Linux forum: https://bbs.archlinux.org/viewtopic.php?id=282162. However, the proposed solutions did not mitigate my issue.

I have been troubled by this question for a long time.

Thank you for addressing my issue. If you require more context or have suggestions on resolving this or where I should seek guidance, please kindly leave a comment

Best Regards,
Dingisoul

Mod edit: replaced oversized image with URL. Please read and follow the guidelines on posting images. -- WorMzy

Last edited by WorMzy (2024-01-02 18:54:29)

Dingisoul · 2023-12-31 07:04:45

I have found that in my journalctl has several lines related to the Xwayland

Dec 31 14:28:35 ArchLu kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:85dffffb, in Xwayland [1281]
Dec 31 14:28:35 ArchLu kernel: i915 0000:00:02.0: [drm] Xwayland[1281] context reset due to GPU hang
Dec 31 14:28:42 ArchLu kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:85dffffb, in Xwayland [1281]
Dec 31 14:28:42 ArchLu kernel: i915 0000:00:02.0: [drm] Xwayland[1281] context reset due to GPU hang
Dec 31 14:49:34 ArchLu kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:85dffffb, in Xwayland [1281]
Dec 31 14:49:34 ArchLu kernel: i915 0000:00:02.0: [drm] Xwayland[1281] context reset due to GPU hang

I find out it is related to the xf86-video-intel driver, I will keep following after remove it

Last edited by Dingisoul (2023-12-31 07:30:24)

Dingisoul · 2024-01-02 11:46:07

However, A new issue comes. The Intel integrated GPU hangs in idle mode and doesn't resume. Additionally, the external monitor shows only a backlight, with no content displayed.

The logs related to i915 driver.

Jan 02 19:03:09 ArchLu kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:85dffffb, in Xwayland [1292]
Jan 02 19:03:09 ArchLu kernel: i915 0000:00:02.0: [drm] Xwayland[1292] context reset due to GPU hang
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x00000000
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in Xwayland [1292]
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] Resetting chip for GuC failed to reset engine mask=0x1
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] Renderer[1638] context reset due to GPU hang
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] Xwayland[1292] context reset due to GPU hang
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.13.1
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Jan 02 19:03:18 ArchLu kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Jan 02 19:03:29 ArchLu kernel: Asynchronous wait on fence 0000:00:02.0:sway[1179]:2d55c6 timed out (hint:intel_atomic_commit_ready [i915])
Jan 02 19:03:29 ArchLu kernel: Asynchronous wait on fence 0000:00:02.0:sway[1179]:2d55c2 timed out (hint:intel_atomic_commit_ready [i915])

There is one section in arch wiki dedicated to this issue https://wiki.archlinux.org/title/Intel_ … tel_driver. However, it seems impact the performance, I'll consider trying it later if other solutions don't resolve the problem

I will update in this issue if there is update

Arch Linux

#1 2023-12-25 09:15:07