Sway unexpectedly logs out with "i965: Failed to submit batchbuffer: Bad address" when focusing on signal-desktop
System information
System: Host: boluonao Kernel: 5.15.4-arch1-1 x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: sway 1.6.1 dm: N/A
Distro: Arch Linux
CPU: Info: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 19160
Speed: 913 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 913 2: 1546 3: 1696 4: 1587
Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus-ID: 00:02.0
chip-ID: 8086:0a16
Device-2: Microdia HP Webcam type: USB driver: uvcvideo bus-ID: 1-1.5:4 chip-ID: 0c45:6517
Display: wayland server: X.org 1.21.1.1 compositor: sway driver: loaded: intel unloaded: modesetting,vesa
alternate: fbdev resolution: <missing: xdpyinfo>
Message: Unable to show advanced data. Required tool glxinfo missing.
Describe the issue
Please see: https://github.com/swaywm/sway/issues/6685 Sway devs believe this might be a mesa issue and suggested opening a mesa bug
Sway might log out unexpectedly after a while (could be minutes or hours) when focusing on signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland
. This consistently happens only when using the Wayland backend, not on Xwayland.
Please describe what you are doing, what you expect and what you're seeing instead. How frequent is the issue? Is it a one time occurrence? Does it appear multiple times but randomly? Can you easily reproduce it?
Run signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland
for some time (it could be minutes or hours). Switching to it leads to Sway exiting unexpectedly. This doesn't happen if it is run in Xwayland mode, but it is otherwise consistent.
Log files as attachment