@Ygor6889 , Igor, is your video card also from intel? I just solved the problem on the Latitude E6410. I created the /etc/X11/xorg.conf.d/20-intel.conf file with the following content:
$ cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
EndSection
Then I restarted the system and Ubuntu Mate stopped crashing!
I saw someone on this post reporting a similar problem:
opened 02:46PM - 27 Sep 22 UTC
bug
### What Operating System(s) are you seeing this problem on?
Linux X11
### Whi… ch Wayland compositor or X11 Window manager(s) are you using?
i3 (Regolith)
### WezTerm version
20220924-194137-47a15153
### Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
### Describe the bug
Trying to launch Wezterm leads to immediate crash
### To Reproduce
Just launch it, and it crashes
### Configuration
local wezterm = require 'wezterm'
local act = wezterm.action
return {
scrollback_lines = 3500,
enable_scroll_bar = true,
keys = {
-- Clears the scrollback and viewport, and then sends CTRL-L to ask the
-- shell to redraw its prompt
{
key = 'K',
mods = 'CTRL|SHIFT',
action = act.Multiple {
act.ClearScrollback 'ScrollbackAndViewport',
act.SendKey { key = 'L', mods = 'CTRL' },
},
},
},
harfbuzz_features = { 'calt=0', 'clig=0', 'liga=0' },
}
### Expected Behavior
Expected behavior is no fatal crash on launch
### Logs
10:39:30.846 ERROR env_bootstrap > panic at /__w/wezterm/wezterm/target/release/build/xcb-e9d7e40c68a49154/out/randr.rs:777:18 - !?
0: <unknown>
1: <unknown>
2: <unknown>
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: <unknown>
11: <unknown>
12: <unknown>
13: <unknown>
14: __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
15: __libc_start_main_impl
at ./csu/../csu/libc-start.c:392:3
16: <unknown>
thread 'main' panicked at 'internal error: entered unreachable code: Could not resolve randr Event with response_type 120 and first_event 89', /__w/wezterm/wezterm/target/release/build/xcb-e9d7e40c68a49154/out/randr.rs:777:18
stack backtrace:
0: 0x55f55d940f0d - <unknown>
1: 0x55f55d96aa7c - <unknown>
2: 0x55f55d9384c1 - <unknown>
3: 0x55f55d942c15 - <unknown>
4: 0x55f55d942936 - <unknown>
5: 0x55f55c6a8748 - <unknown>
6: 0x55f55d94325a - <unknown>
7: 0x55f55d943097 - <unknown>
8: 0x55f55d9413c4 - <unknown>
9: 0x55f55d942dc9 - <unknown>
10: 0x55f55c3131e3 - <unknown>
11: 0x55f55cf2a441 - <unknown>
12: 0x55f55cf29483 - <unknown>
13: 0x55f55ce43bbc - <unknown>
14: 0x55f55c3a370d - <unknown>
15: 0x55f55c411b33 - <unknown>
16: 0x55f55c46ce79 - <unknown>
17: 0x55f55d930a1e - <unknown>
18: 0x55f55c3a8f82 - <unknown>
19: 0x7fa2aa85dd90 - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
20: 0x7fa2aa85de40 - __libc_start_main_impl
at ./csu/../csu/libc-start.c:392:3
21: 0x55f55c313945 - <unknown>
22: 0x0 - <unknown>
rhett@thelappy:~$
### Anything else?
_No response_
And then I followed what was in the 6.1 section of the ArchLinux Wiki:
https://wiki.archlinux.org/title/intel_graphics#Tearing
3 Likes