xserver merge requestshttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests2024-01-17T05:04:49Zhttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1176Fix a double-free on syntax error without a new line.2024-01-17T05:04:49ZMatthieu HerrbFix a double-free on syntax error without a new line.$ echo "#foo\nfoo" > custom_config
$ X -config custom_config
will trigger the double free because the contents of
xf86_lex_val.str have been realloc()ed aready when
free is called in read.c:209.
This invalidates the pointer so that it ...$ echo "#foo\nfoo" > custom_config
$ X -config custom_config
will trigger the double free because the contents of
xf86_lex_val.str have been realloc()ed aready when
free is called in read.c:209.
This invalidates the pointer so that it doesn't get
free()d a second time.https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1129xfree86: Support Moore Threads GPU2023-06-26T08:35:18ZPeng Jinxfree86: Support Moore Threads GPUDuring testing Moore Threads GPU with ubuntu lightdm+gnome+xorg desktop environment, we found that it can load DDX with mtgpu_drv.so. But during screen locking, lightdm will start a new Xorg to display a greeter, this new Xorg would matc...During testing Moore Threads GPU with ubuntu lightdm+gnome+xorg desktop environment, we found that it can load DDX with mtgpu_drv.so. But during screen locking, lightdm will start a new Xorg to display a greeter, this new Xorg would match modesettings_drv.so instead of a correct one mtgpu_drv.so.
After debuging, we found the root cause is that xf86VideoPtrToDriverList function of Xorg is absent support for Moore Threads GPU.https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/997No longer leak FDs on VT switch.2023-12-17T19:04:23ZSpiky CaterpillarNo longer leak FDs on VT switch.On some systems, X will leak file descriptors when you switch VTs. If the system stays up long enough and you switch VTs enough, it will eventually lock up from fd exhaustion.
To demonstrate this on affected machines:
```
lsof -n |grep ...On some systems, X will leak file descriptors when you switch VTs. If the system stays up long enough and you switch VTs enough, it will eventually lock up from fd exhaustion.
To demonstrate this on affected machines:
```
lsof -n |grep -c /dev/dri/card0
control-alt-functionkey into another VT
control-alt-functionkey back to X
lsof -n | grep -c /dev/dri/card0
```
The number of fds leaked varies from system to system. I saw it on a Debian desktop with a Radeon
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM]
and a laptop with an Intel Corporation Core Processor Integrated Graphics Controller; another machine, with an nVidia card (though I don't remember the driver settings), doesn't show the bug.
The bug was originally patched by Chris Wilson in 2016, see
https://gitlab.freedesktop.org/xorg/xserver/-/issues/204https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/615Draft: xfree86/modes: Use per-screen monitor for all outputs by default2021-04-08T17:10:20ZOlivier CertnerDraft: xfree86/modes: Use per-screen monitor for all outputs by defaultPatch to implement the desired behavior (see issue #1140).
If there is interest in this MR, I'll follow up with the drivers. Indeed,
at least 'xf86-video-intel' may need to also be updated accordingly (see
'src/sna/sna_display.c', funct...Patch to implement the desired behavior (see issue #1140).
If there is interest in this MR, I'll follow up with the drivers. Indeed,
at least 'xf86-video-intel' may need to also be updated accordingly (see
'src/sna/sna_display.c', function 'sna_output_add', call to
'xf86OutputUseScreenMonitor'). Have not checked drivers besides 'xf86-video-intel',
'xf86-video-amdgpu', 'xf86-video-nouveau', 'xf86-video-nv' and
'xf86-video-vesa' at this point.https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/310glamor: xv: Fix sw cursor rendering issue2023-12-18T16:07:14ZJeffyChenjeffy.chen@rock-chips.comglamor: xv: Fix sw cursor rendering issueHi guys,
I've been reported seeing damage when using glamor xv + sw cursor. It seems like the under cursor area stop updating.
This is because when reporting damage, the misprite swcursor will try to remove cursor by restoring the unde...Hi guys,
I've been reported seeing damage when using glamor xv + sw cursor. It seems like the under cursor area stop updating.
This is because when reporting damage, the misprite swcursor will try to remove cursor by restoring the under cursor area, and that will override the previous draw.