xorg issueshttps://gitlab.freedesktop.org/groups/xorg/-/issues2020-08-03T12:30:41Zhttps://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/116Regression in 1.6.102020-08-03T12:30:41ZYichao YuRegression in 1.6.10Introduced by https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488 .
In particular, https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488#261ec56ec4e...Introduced by https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488 .
In particular, https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488#261ec56ec4e63167dfb89d70a34c54b7af676a80_264_268 and https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/388b303c62aa35a245f1704211a023440ad2c488#261ec56ec4e63167dfb89d70a34c54b7af676a80_371_381.
For both lines, `data_len` is the readable data length in bytes. However, the LHS uses the result data type (`XIMStyle` and `XIMHotKeyTrigger`) instead of the read data type (`CARD32` and 3x `CARD32`), i.e.
```patch
diff --git a/modules/im/ximcp/imRmAttr.c b/modules/im/ximcp/imRmAttr.c
index 2491908e..10be5619 100644
--- a/modules/im/ximcp/imRmAttr.c
+++ b/modules/im/ximcp/imRmAttr.c
@@ -265,7 +265,7 @@ _XimAttributeToValue(
if (num > (USHRT_MAX / sizeof(XIMStyle)))
return False;
- if ((sizeof(num) + (num * sizeof(XIMStyle))) > data_len)
+ if ((sizeof(num) + (num * sizeof(CARD32))) > data_len)
return False;
alloc_len = sizeof(XIMStyles) + sizeof(XIMStyle) * num;
if (alloc_len < sizeof(XIMStyles))
@@ -379,7 +379,7 @@ _XimAttributeToValue(
if (num > (UINT_MAX / sizeof(XIMHotKeyTrigger)))
return False;
- if ((sizeof(num) + (num * sizeof(XIMHotKeyTrigger))) > data_len)
+ if ((sizeof(num) + (num * 3 * sizeof(CARD32))) > data_len)
return False;
alloc_len = sizeof(XIMHotKeyTriggers)
+ sizeof(XIMHotKeyTrigger) * num;
```
------
As a side note, I believe the correct version for the `sizeof(num)` is `2 * sizeof(CARD16)` since this is the offset in `data` the array of data starts.https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/16WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()2020-07-01T16:03:42ZBugzilla Migration UserWARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#109628)](https://bugs.freedesktop.org/show_bug.cgi?id=109628)**
## Description
I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U and ex...## Submitted by Rafał Miłecki
Assigned to **Default DRI bug account**
**[Link to original bug (#109628)](https://bugs.freedesktop.org/show_bug.cgi?id=109628)**
## Description
I use HP EliteBook 745 G5 with Ryzen 5 PRO 2500U and external monitor BenQ GW2260.<br>
<br>
Today after taking ~10 minutes break amdgpu had some problems with enabling my external monitor back (after putting it in sleep mode or something). It took it about half a minute I think.<br>
<br>
I checked dmesg immediately and found there a WARNING:<br>
[65984.999696] WARNING: CPU: 6 PID: 2081 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high+0x25/0x260 [amdgpu]<br>
<br>
I suspect it may be related to the issue I'm reporting.<br>
<br>
So far I was using kernels 4.19 and 4.20 (for the last 2 months) and never saw it. A day ago I've switched to the kernel 5.0.0-rc6. It may be either:<br>
1. A regression<br>
2. A very rare bughttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1018Massive screen corruption with the modesetting driver (works with amdgpu)2020-11-04T19:36:18ZAndrew Nowa Ammerlaanandrewammerlaan@gentoo.orgMassive screen corruption with the modesetting driver (works with amdgpu)My monitors:
- Ancient 1440x900 monitor (PLE1900WS DP-1-5) connected with VGA to iGPU (Intel UHD Graphics 630)
- Less ancient 1600x900 monitor (Samsung SyncMaster HDMI-1-3) connected with DVI-D to iGPU (Intel UHD Graphics 630)
- Prima...My monitors:
- Ancient 1440x900 monitor (PLE1900WS DP-1-5) connected with VGA to iGPU (Intel UHD Graphics 630)
- Less ancient 1600x900 monitor (Samsung SyncMaster HDMI-1-3) connected with DVI-D to iGPU (Intel UHD Graphics 630)
- Primary: 1920x1080 monitor (PL2288H DVI-D-0) connected with DVI-D to dGPU (AMD RX 590)
- Slightly ancient Sony TV 1360x768 (HDMI-A-0) connected with HDMI to dGPU (AMD RX 590)
Using the modesetting driver I get this on DP-1-5:
![image](/uploads/5296a99d3fdd2407cf51e50e5c1d48cd/image.png)
While it works just fine with the amdgpu driver (I have a different issue with the amdgpu driver, which is why I was trying the modesetting driver instead: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/11 )
- This happens only if the monitor is set to certain resolutions; it happens with 1440x900 (highest) but not with 1280x1024 or 1290x960.
- It happens both with PRIME Sync on and off.
- It does not occur if the Intel card is set as the default GPU with `xrandr --setprovideroutputsource`.
- Nor does it occur if DP-1-5 is connected with a (passive) HDMI-->VGA adapter to the dGPU instead.
- The cursor is not effected by the screen corruption, everything else is though.
- This happens both after log-in into KDE Plasma, and before log-in in SDDM.
This worked fine before I switched out my Nvidia card for the AMD card. Prime Sync was enabled, Nvidia was set as the renderer. Monitor configuration was identical. Intel card was using the modesetting driver.
Here's my Xorg log: [Xorg.0.log](/uploads/02ce13799d9a9d045e80066223199e43/Xorg.0.log)
- linux-5.6.7-gentoo
- mesa-20.0.5
- xorg-server-1.20.8
- xorg-drivers-1.20-r2
@daenzer over at amdgpu suggested that it might be a pitch and/or tiling parameter mismatch
Please let me know if any more information is needed.https://gitlab.freedesktop.org/xorg/xserver/-/issues/936Meson: input thread is unconditionally disabled2021-04-09T11:24:51ZAlexander PatrakovMeson: input thread is unconditionally disabledIf one builds xorg-server 1.20.4 with Meson (as e.g. Arch Linux does), the input thread and therefore silken mouse ends up being disabled due to the following issues:
1. Meson sets HAVE_INPUTTHREAD, while the rest of the code uses the I...If one builds xorg-server 1.20.4 with Meson (as e.g. Arch Linux does), the input thread and therefore silken mouse ends up being disabled due to the following issues:
1. Meson sets HAVE_INPUTTHREAD, while the rest of the code uses the INPUTTHREAD macro.
2. Detection of HAVE_PTHREAD_SETNAME_NP_WITH_TID is missing (fixed in master by c20e7b5e2222c0cae2a487264748fa5db711e6e4).
3. Detection whether to build with -pthread and link to -lpthreads is missing.xserver-21.1https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/104Add compose sequences for acute-accented Cyrillic vowels2020-04-25T19:30:35ZTristan MillerAdd compose sequences for acute-accented Cyrillic vowelsThe acute accent is commonly used to mark syllable stress in dictionaries, encyclopedias, and language learning materials for Russian and some other Cyrillic-script languages. The accent is placed over the vowel of the syllable with pri...The acute accent is commonly used to mark syllable stress in dictionaries, encyclopedias, and language learning materials for Russian and some other Cyrillic-script languages. The accent is placed over the vowel of the syllable with primary stress. (See for example the Russian editions of Wikipedia and Wiktionary, or virtually any printed Russian dictionary or printed textbook for learning Russian.) However, libX11 is missing such compose sequences for many Cyrillic vowels, which makes it difficult to compose lexicographic or language learning material. One can always create a custom `$HOME/.XCompose`, but this is not easy, particularly for users that are not technically inclined. It would be better if these compose sequences were available system-wide by default.
Among vowels used in Russian, the current libX11 compose sequences cover а, у, о, е, and и, but not э, ы, я, or ю. (The vowel ё is not covered either, but at least in Russian it is always stressed and so never marked.) Other languages, such as Ukrainian, have further vowels that I know sometimes take acute accents. However, I lack detailed and comprehensive knowledge of all such languages (that is, what vowels they use, and whether or not it is common practice for them to be marked with an acute accent in pedagogical and lexicographic sources) and so have not checked whether their compose sequences are also missing.
I will prepare and submit a merge request that covers at least Russian; if it is accepted then perhaps this issue can be left open in the event that someone wants to contribute the necessary sequences for Ukrainian and other Cyrillic-alphabet languages.
Note: This issue was previously reported for XKB, first as [Bug 2793](https://bugs.freedesktop.org/show_bug.cgi?id=2793) on the old Bugzilla and then as [Issue 184](https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/184) here on GitLab. In those bugs the consensus was that this is a libX11 issue, not an XKB issue.https://gitlab.freedesktop.org/xorg/xserver/-/issues/893libglvnd versions GL/GLES/GLX/EGL libraries differently than mesa2019-10-09T19:44:20ZMarvin Schmidtlibglvnd versions GL/GLES/GLX/EGL libraries differently than mesaWhen using `mesa` with `libglvnd` support, `mesa` will no longer install the `gl`, `glx`, `egl` pkg-config files but instead let `libglvnd` provide them. `libglvnd` maintainers decided to change the versioning as it was mesa-specific pre...When using `mesa` with `libglvnd` support, `mesa` will no longer install the `gl`, `glx`, `egl` pkg-config files but instead let `libglvnd` provide them. `libglvnd` maintainers decided to change the versioning as it was mesa-specific previously. Now the libraries have versions of the API they expose[1].
This causes problems when building the X server:
```
checking for glproto >= 1.4.17 gl >= 9.2.0... no
configure: error: Package requirements (glproto >= 1.4.17 gl >= 9.2.0) were not met:
Requested 'gl >= 9.2.0' but version of gl is 1.2
```
I would provide a patch but I assume it's not as easy as lowering the version? I wonder if `mesa` should adopt the API based versioning as well. It's pretty unfortunate that there are now two providers of the same libraries with different version schemes :-/
[1] https://github.com/NVIDIA/libglvnd/commit/0dfaea2bcb7cdcc785f95e244223bd004a2d7fbahttps://gitlab.freedesktop.org/xorg/lib/libxkbfile/-/issues/6xorg-libxkbfile: missing uninitializer for `struct _XkbRF_VarDefs`2024-03-18T01:31:06ZBugzilla Migration Userxorg-libxkbfile: missing uninitializer for `struct _XkbRF_VarDefs`## Submitted by Sergey Mironov
Assigned to **X.Org Security**
**[Link to original bug (#110696)](https://bugs.freedesktop.org/show_bug.cgi?id=110696)**
## Description
Hi. We use `XkbRF_GetNamesProp` function to get layout properti...## Submitted by Sergey Mironov
Assigned to **X.Org Security**
**[Link to original bug (#110696)](https://bugs.freedesktop.org/show_bug.cgi?id=110696)**
## Description
Hi. We use `XkbRF_GetNamesProp` function to get layout properties. Unfortunately, it looks like the structure filled by the function needs special deinitializer, since you use `malloc` to allocate string pointers. AFAIK no deinitializer is provided currently. Could you please provide one?
Ref: https://github.com/ierton/xkb-switch/pull/30https://gitlab.freedesktop.org/xorg/xserver/-/issues/703XWayland does not support scaling2023-05-26T14:33:36ZBugzilla Migration UserXWayland does not support scaling## Submitted by Maciej Piechotka
Assigned to **Wayland bug list**
**[Link to original bug (#101193)](https://bugs.freedesktop.org/show_bug.cgi?id=101193)**
## Description
Original bug https://bugzilla.gnome.org/show_bug.cgi?id=781...## Submitted by Maciej Piechotka
Assigned to **Wayland bug list**
**[Link to original bug (#101193)](https://bugs.freedesktop.org/show_bug.cgi?id=101193)**
## Description
Original bug https://bugzilla.gnome.org/show_bug.cgi?id=781068
Currently XWayland provides single resolution via XRandR. This makes hard to play games if engine does not handle full resolution for whatever reason.
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=93315https://gitlab.freedesktop.org/xorg/xserver/-/issues/266XKB settings lost after suspend/resume / not taken into account for new keyboard2023-12-07T22:30:24ZBugzilla Migration UserXKB settings lost after suspend/resume / not taken into account for new keyboard## Submitted by Vincent Lefevre
Assigned to **Xorg Project Team**
**[Link to original bug (#71168)](https://bugs.freedesktop.org/show_bug.cgi?id=71168)**
## Description
I have personal XKB settings. From my .initrc file:
xkbcom...## Submitted by Vincent Lefevre
Assigned to **Xorg Project Team**
**[Link to original bug (#71168)](https://bugs.freedesktop.org/show_bug.cgi?id=71168)**
## Description
I have personal XKB settings. From my .initrc file:
xkbcomp -w0 -I$HOME/.xkb -R$HOME/.xkb keymap/custom $DISPLAY
Most often they are lost after suspend/resume on my DELL Latitude E6400 laptop. Moreover when I plug-in a USB keyboard, these settings are not taken into account for this keyboard (the laptop keyboard remains unaffected).
After resume, I can run
xkbcomp -w0 -I$HOME/.xkb -R$HOME/.xkb keymap/custom $DISPLAY
again without quitting the X session, but some running X clients do not take all new settings into account (problem with modifier keys?).
I originally reported the bug on:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633849
where you can find additional details.
Version: githttps://gitlab.freedesktop.org/xorg/xserver/-/issues/211LIBGL_ALWAYS_INDIRECT=1 causes all opengl programms to crash on second frame2020-02-06T17:03:45ZBugzilla Migration UserLIBGL_ALWAYS_INDIRECT=1 causes all opengl programms to crash on second frame## Submitted by dip..@..il.com
Assigned to **Xorg Project Team**
**[Link to original bug (#99555)](https://bugs.freedesktop.org/show_bug.cgi?id=99555)**
## Description
LIBGL_ALWAYS_INDIRECT=1 glxgears
fails on latest git on r600 ...## Submitted by dip..@..il.com
Assigned to **Xorg Project Team**
**[Link to original bug (#99555)](https://bugs.freedesktop.org/show_bug.cgi?id=99555)**
## Description
LIBGL_ALWAYS_INDIRECT=1 glxgears
fails on latest git on r600 with:
X Error of failed request: 255
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 1 (X_GLXRender)
Serial number of failed request: 42
Current serial number in output stream: 164
After rendering one frame. this is on a ATI HD5850. This is 100% repeatable and occures with every opengl app. Direct Rendering works fine.
Indirect rendering works with the vesa x11 driver and llvmpipe. xf86-video-ati versus xf86-video-modestetting both fail.
Version: gitAdam Jacksonajax@nwnk.netAdam Jacksonajax@nwnk.nethttps://gitlab.freedesktop.org/xorg/xserver/-/issues/97Failed to compile FS: 0:11(2): error: `colord0 undeclared2020-01-13T22:19:22ZBugzilla Migration UserFailed to compile FS: 0:11(2): error: `colord0 undeclared## Submitted by Tomasz Paweł Gajc
Assigned to **Xorg Project Team**
**[Link to original bug (#108354)](https://bugs.freedesktop.org/show_bug.cgi?id=108354)**
## Description
Hi,
i've found and not usual issue with LxQt and openbox...## Submitted by Tomasz Paweł Gajc
Assigned to **Xorg Project Team**
**[Link to original bug (#108354)](https://bugs.freedesktop.org/show_bug.cgi?id=108354)**
## Description
Hi,
i've found and not usual issue with LxQt and openbox as window manager in VirtualBox environment.
First LxQt starts and loads up, then starting qterminal or any other app immediately crashes x11-server-1.20.1.
I've found in Xorg.log.0 this:
Failed to compile FS: 0:11(2): error: `colord0 undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type error
0:11(2): error: `color1` undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type error
[ 702.919] Program source:
#ifdef GL_ES
precision medium float
#endif
#define ATLAS_DIM_INV 0.00097656250000000
varying vec2 glyph_pos;
uniform sampler2D sampler;
uniform sampler2D atlas;
void main() {
vec4 mask = texture2D(atlas, glyph_pos);
vec source = texture2D(sampler, vec2(0.5));
color0 = source * mask;
color1 = source.a * mask;
}
[ 702.919] (EE)
Fatal server error:
[ 702.919] GLSL compile failure
There is a potential patch.
http://ant.spdns.eu/color0_1_undefined.patch
Environment:
OpenMandriva Lx 4.0 alpha
ISO can be downloaded here
https://abf.openmandriva.org/platforms/cooker/products/50/product_build_lists/2260https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/36Use-after-free in XUnregisterIMInstantiateCallback causes wrong behavior or c...2021-06-03T23:35:36ZBugzilla Migration UserUse-after-free in XUnregisterIMInstantiateCallback causes wrong behavior or crash## Submitted by Dmitry Antipov
Assigned to **Xorg Project Team**
**[Link to original bug (#81338)](https://bugs.freedesktop.org/show_bug.cgi?id=81338)**
## Description
Created attachment 102761
proposal fix
I was unable to create...## Submitted by Dmitry Antipov
Assigned to **Xorg Project Team**
**[Link to original bug (#81338)](https://bugs.freedesktop.org/show_bug.cgi?id=81338)**
## Description
Created attachment 102761
proposal fix
I was unable to create small and isolated example, so the only way to reproduce this bug is to run GNU Emacs with multiple X servers (Xnest is OK too). So steps to reproduce are:
1. Compile Emacs with Lucid toolkit (--with-x-toolkit=lucid) and internal checking enabled (--enable-checking).
2. Run Xnest on :1
3. Run Emacs with:
emacs -Q --eval '(let ((f (selected-frame))) (make-frame-on-display ":1.0") (delete-frame f))'
4. See assertion failure at xterm.c:8006 while checking the value returned from XUnregisterIMInstantiateCallback.
Running under Valgrind (see http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17975#17) shows a use-after-free error.
Proposal fix is attached.
**Attachment 102761**, "proposal fix":
[lcd-core-modifiers.patch](/uploads/317d032699a68aeaa0d5096c58878f39/lcd-core-modifiers.patch)
Version: 7.7 (2012.06)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1623Regression caused by "dix: when disabling a master, float disabled slaved dev...2024-01-30T17:23:27ZSalvatore BonaccorsoRegression caused by "dix: when disabling a master, float disabled slaved devices too"While preparing updates in Debian for the recent security fixes we noticed
a regression caused by the fixes for CVE-2024-21886 specifically bisected
to https://gitlab.freedesktop.org/xorg/xserver/-/commit/26769aa71fcbe0a8403b7fb13b7c9010...While preparing updates in Debian for the recent security fixes we noticed
a regression caused by the fixes for CVE-2024-21886 specifically bisected
to https://gitlab.freedesktop.org/xorg/xserver/-/commit/26769aa71fcbe0a8403b7fb13b7c9010cc07c3a8
Running
```
Xvfb :10 & sleep 2; DISPLAY=:10 xdpyinfo >/dev/null
```
results in a leak
```
1 XSELINUXs still allocated at reset
SCREEN: 0 objects of 304 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 88 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 144 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 48 bytes = 0 total bytes 0 private allocs
PIXMAP: 0 objects of 16 bytes = 0 total bytes 0 private allocs
GC: 0 objects of 16 bytes = 0 total bytes 0 private allocs
CURSOR: 1 objects of 8 bytes = 8 total bytes 0 private allocs
TOTAL: 1 objects, 8 bytes, 0 allocs
1 CURSORs still allocated at reset
CURSOR: 1 objects of 8 bytes = 8 total bytes 0 private allocs
TOTAL: 1 objects, 8 bytes, 0 allocs
1 CURSOR_BITSs still allocated at reset
TOTAL: 0 objects, 0 bytes, 0 allocs
```
as found by @jcristau.
Reported for tracking in Downstream Debian at: https://bugs.debian.org/1061110https://gitlab.freedesktop.org/xorg/xserver/-/issues/1580Feature request: allow to choose GL or GL ES API on Glamor loading2023-11-02T10:22:17ZKonstantinFeature request: allow to choose GL or GL ES API on Glamor loadingI think it is good to add command-line switch and environment variable to XWayland to allow loading OpenGL ES (similar to Xephyr).
Also it can be good to allow Xorg load straightly OpenGL ES (without trying OpenGL) as Xorg.conf option.I think it is good to add command-line switch and environment variable to XWayland to allow loading OpenGL ES (similar to Xephyr).
Also it can be good to allow Xorg load straightly OpenGL ES (without trying OpenGL) as Xorg.conf option.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1558AutoRepeat setting wrong repeat rate2023-11-02T01:20:45ZJoey HoltzmanAutoRepeat setting wrong repeat rateThe "AutoRepeat" rate for a keyboard sets the wrong repeat rate. For example, if I have `Option "AutoRepeat" "150 40"`, this sets the delay rate to 150 (correct) and the repeat rate to 25. I can verify this by viewing the output of `xset...The "AutoRepeat" rate for a keyboard sets the wrong repeat rate. For example, if I have `Option "AutoRepeat" "150 40"`, this sets the delay rate to 150 (correct) and the repeat rate to 25. I can verify this by viewing the output of `xset q`: `auto repeat delay: 150 repeat rate: 25`.
Here is the log output, which shows the correct numbers:
```
[ 15968.600] (**) Option "xkb_options" "caps:none"
[ 15968.601] (**) Option "AutoRepeat" "150 40"
[ 15968.601] (**) AutoRepeat: 150 40
```
Here is my `/etc/X11/xorg.conf.d/99-keyboard.conf`:
```
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbOptions" "caps:none"
Option "AutoRepeat" "150 40"
EndSection
```
Another configuration could possibly be affecting this, but it is strange that it every time I change the repeat rate, the actual repeat rate set is different (ex. using 50 instead of 40 changes the actual repeat rate to 20).
I'd be happy to submit a fix for this if I figure out what is going on.https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/69Steam's system information triggers crash2023-05-12T15:48:39ZSantiago TabaresSteam's system information triggers crashWhen using steam's system information tool the system crashes after a few seconds.
I crashes on 6.3.0, 6.1.26 on both kwin_x11 and kwin_wayland. However on 5.15.109 it works fine.
My notebook has amd+nvidia using prime but there are ot...When using steam's system information tool the system crashes after a few seconds.
I crashes on 6.3.0, 6.1.26 on both kwin_x11 and kwin_wayland. However on 5.15.109 it works fine.
My notebook has amd+nvidia using prime but there are other reports in valve, mesa and manjaro forums.
https://github.com/ValveSoftware/steam-for-linux/issues/9267
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8636
https://forum.manjaro.org/t/steam-native-getting-system-information-crashes-the-gpu-driver/131748/4
System information
```
System:
Kernel: 6.3.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.3-x86_64
root=UUID=9e8a1329-5938-4b09-8479-cbfdb008bacd rw rootflags=subvol=@ quiet
udev.log_priority=3 nvidia-drm.modeset=1
Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_wayland vt: 2
dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 82JU v: Legion 5 15ACH6H
CPU:
Info: model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000C
Graphics:
Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
status: current (as of 2023-05) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1,
DP-2, HDMI-A-1, eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2560 class-ID: 0300
Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: none
bus-ID: 06:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 40.0 C
Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,amdgpu display-ID: 0
Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (renoir LLVM
15.0.7 DRM 3.52 6.3.0-1-MANJARO) direct-render: Yes
```
journalctl -p err -b -1 --no-pager
```
Journal file /var/log/journal/f78631a4a95946c789aa2ca77170c8a4/user-1000@0005fb7feaefdf0a-e49a055ebdd0a34a.journal~ is truncated, ignoring file.
may 12 11:29:16 santiago-82ju kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
may 12 11:29:16 santiago-82ju kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
may 12 11:29:16 santiago-82ju systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
may 12 11:29:16 santiago-82ju systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
may 12 11:29:17 santiago-82ju kernel:
may 12 11:29:19 santiago-82ju bluetoothd[673]: src/plugin.c:plugin_init() Failed to init vcp plugin
may 12 11:29:19 santiago-82ju bluetoothd[673]: src/plugin.c:plugin_init() Failed to init mcp plugin
may 12 11:29:19 santiago-82ju bluetoothd[673]: src/plugin.c:plugin_init() Failed to init bap plugin
may 12 11:29:19 santiago-82ju bluetoothd[673]: Failed to set mode: Blocked through rfkill (0x12)
may 12 11:29:19 santiago-82ju sddm[743]: Failed to read display number from pipe
may 12 11:29:25 santiago-82ju bluetoothd[673]: Failed to set mode: Blocked through rfkill (0x12)
may 12 11:29:28 santiago-82ju wpa_supplicant[895]: bgscan simple: Failed to enable signal strength monitoring
may 12 11:30:46 santiago-82ju systemd-coredump[3317]: [🡕] Process 3311 (i386-linux-gnu-) of user 1000 dumped core.
Stack trace of thread 3311:
#0 0x00000000f5f9b3cf n/a (libnvidia-glcore.so.530.41.03 + 0x19ed3cf)
#1 0x00000000f5f1fa0d n/a (libnvidia-glcore.so.530.41.03 + 0x1971a0d)
#2 0x00000000f5f21fb3 n/a (libnvidia-glcore.so.530.41.03 + 0x1973fb3)
#3 0x00000000f5f231af n/a (libnvidia-glcore.so.530.41.03 + 0x19751af)
#4 0x00000000f766ae35 n/a (libGLX_nvidia.so.0 + 0x94e35)
#5 0x00000000f7c09680 n/a (libvulkan.so.1 + 0x27680)
#6 0x00000000e7772c57 n/a (/home/santiago/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so + 0x15c57)
ELF object binary architecture: Intel 80386
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32790, for process i386-linux-gnu- pid 3327 thread i386-linux:cs0 pid 3328)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: in page starting at address 0x0000800100768000 from IH client 0x12 (VMC)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00143851
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: VCN (0x1c)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x1
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x5
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: RW: 0x1
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32790, for process i386-linux-gnu- pid 3327 thread i386-linux:cs0 pid 3328)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: in page starting at address 0x0000800100769000 from IH client 0x12 (VMC)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0)
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MORE_FAULTS: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: WALKER_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: PERMISSION_FAULTS: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: MAPPING_ERROR: 0x0
may 12 11:30:46 santiago-82ju kernel: amdgpu 0000:06:00.0: amdgpu: RW: 0x0
may 12 11:30:47 santiago-82ju systemd-coredump[3934]: [🡕] Process 3928 (x86_64-linux-gn) of user 1000 dumped core.
Stack trace of thread 3928:
#0 0x00007f63fda28dd8 n/a (libnvidia-glcore.so.530.41.03 + 0x1990dd8)
#1 0x00007f63fd9a9d3f n/a (libnvidia-glcore.so.530.41.03 + 0x1911d3f)
#2 0x00007f63fd9ac675 n/a (libnvidia-glcore.so.530.41.03 + 0x1914675)
#3 0x00007f63fd9ad2fb n/a (libnvidia-glcore.so.530.41.03 + 0x19152fb)
#4 0x00007f6400b768f0 n/a (libGLX_nvidia.so.0 + 0x9c8f0)
#5 0x00007f64013acc06 n/a (libvulkan.so.1 + 0x23c06)
#6 0x00007f63ffe95257 n/a (/home/santiago/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so + 0x19257)
ELF object binary architecture: AMD x86-64
may 12 11:30:50 santiago-82ju systemd-coredump[5333]: [🡕] Process 5327 (i386-linux-gnu-) of user 1000 dumped core.
Stack trace of thread 5327:
#0 0x00000000f5c4e3cf n/a (/run/host/usr/lib32/libnvidia-glcore.so.530.41.03 + 0x19ed3cf)
ELF object binary architecture: Intel 80386
may 12 11:30:51 santiago-82ju systemd-coredump[6496]: [🡕] Process 6490 (x86_64-linux-gn) of user 1000 dumped core.
Stack trace of thread 6490:
#0 0x00007f7fb6828dd8 n/a (/run/host/usr/lib/libnvidia-glcore.so.530.41.03 + 0x1990dd8)
ELF object binary architecture: AMD x86-64
may 12 11:30:53 santiago-82ju systemd-coredump[7649]: [🡕] Process 7643 (i386-linux-gnu-) of user 1000 dumped core.
Stack trace of thread 7643:
#0 0x00000000f5cfb3cf n/a (/run/host/usr/lib32/libnvidia-glcore.so.530.41.03 + 0x19ed3cf)
ELF object binary architecture: Intel 80386
may 12 11:30:54 santiago-82ju systemd-coredump[8613]: [🡕] Process 8607 (x86_64-linux-gn) of user 1000 dumped core.
Stack trace of thread 8607:
#0 0x00007f2bd4628dd8 n/a (/run/host/usr/lib/libnvidia-glcore.so.530.41.03 + 0x1990dd8)
ELF object binary architecture: AMD x86-64
may 12 11:33:39 santiago-82ju systemd-logind[677]: Failed to start autovt@tty2.service: Transaction for getty@tty2.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
```https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/57Improve manpage regarding the new custom acceleration profile2023-04-25T22:47:54ZDenilson Sá MaiaImprove manpage regarding the new custom acceleration profileCommits f94a8edb0edcca8af53b3994d23735df6a5974f1 and 484b6a7f3ffb2641c8c35043145be4e5eca26112 added a new custom acceleration profile. They also included some entries to the `libinput.4` manpage. However, there are still a few issues in ...Commits f94a8edb0edcca8af53b3994d23735df6a5974f1 and 484b6a7f3ffb2641c8c35043145be4e5eca26112 added a new custom acceleration profile. They also included some entries to the `libinput.4` manpage. However, there are still a few issues in the manpage:
* The new Xorg configuration entries (`Option "…"`) were documented, but the corresponding libinput runtime properties are still not documented:
* [ ] `libinput Accel Profile Enabled` now has 3 values instead of 2.
* [ ] `libinput Accel Profile Enabled Default` now has 3 values instead of 2.
* [ ] `libinput Accel Profiles Available` now has 3 values instead of 2.
* [ ] `libinput Accel Custom Fallback Points` is undocumented
* [ ] `libinput Accel Custom Fallback Step` is undocumented
* [ ] `libinput Accel Custom Motion Points` is undocumented
* [ ] `libinput Accel Custom Motion Step` is undocumented
* [ ] `libinput Accel Custom Scroll Points` is undocumented
* [ ] `libinput Accel Custom Scroll Step` is undocumented
* [ ] The current manpage literally says *“see the libinput documentation”* several times. Well, the manpage IS documentation, and telling the reader to read the documentation that the user is already reading is not helpful. So, either fully document it at the manpage, or [point to the other location where the rest of the documentation can be found](https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html).
* [ ] Since there are now more options related to the custom acceleration than other acceleration options, it is easier to group them together and describe them all at once, like this:
```
[…]
.TP 7
.BI "Option \*qAccelSpeed\*q \*q" float \*q
Sets the pointer acceleration speed within the range [-1, 1].
This only applies to the flat or adaptive profile.
.TP 7
.BI "Option \*qAccelPointsFallback\*q \*q" string \*q
.TQ
.BI "Option \*qAccelPointsMotion\*q \*q" string \*q
.TQ
.BI "Option \*qAccelPointsScroll\*q \*q" string \*q
Sets the points of the Fallback/Motion/Scroll acceleration functions.
The string must be a space-separated list of floating point non-negative numbers, e.g.
"0.0 1.0 2.4 2.5".
This only applies to the custom profile.
.TP 7
.BI "Option \*qAccelStepFallback\*q \*q" float \*q
.TQ
.BI "Option \*qAccelStepMotion\*q \*q" float \*q
.TQ
.BI "Option \*qAccelStepScroll\*q \*q" float \*q
Sets the step between the points of the Fallback/Motion/Scroll acceleration functions.
When a step of 0.0 is provided, libinput's default Fallback acceleration function is used.
This only applies to the custom profile.
.TP 7
.BI "Option \*qButtonMapping\*q \*q" string \*q
[…]
```
which renders like:
![screenshot of the terminal, showing the manpage for the above snippet](/uploads/11e715e4c1c7e9a488e1f17bd8d719d7/image.png)
Since @whot and @Yinon worked on the feature, they are the people with most knowledge about the new options, and I think they should improve/fix the manpage.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1512[regression] xwayland 23.0.99.901 prerelease - Keyboard Layout switching brok...2023-03-07T22:01:49ZMikhail Gavrilov[regression] xwayland 23.0.99.901 prerelease - Keyboard Layout switching broken at X11 clientsDownstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2173201
I try bisect this issue
```
❯ git bisect bad xwayland-23.0.99.901
You need to start by "git bisect start"
Do you want me to do it for you [Y/n]? y
status: waiting f...Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2173201
I try bisect this issue
```
❯ git bisect bad xwayland-23.0.99.901
You need to start by "git bisect start"
Do you want me to do it for you [Y/n]? y
status: waiting for both good and bad commits
status: waiting for good commit(s), bad commit known
❯ git bisect good xwayland-22.1.8
Bisecting: a merge base must be tested
[d1f26c3e7566ebb6178a855b08b0f06dec730fb5] xwayland: Raise the FD limit to the max
```
But stopped on first stage because build failed with error:
```
../render/picture.c:874:26: error: array subscript ‘union _SourcePict[0]’ is partly outside array bounds of ‘unsigned char[16]’ [-Werror=array-bounds=]
874 | pPicture->pSourcePict->type = SourcePictTypeSolidFill;
| ^~
../render/picture.c:868:45: note: object of size 16 allocated by ‘malloc’
868 | pPicture->pSourcePict = (SourcePictPtr) malloc(sizeof(PictSolidFill));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../render/picture.c: In function ‘CreateLinearGradientPicture’:
../render/picture.c:906:26: error: array subscript ‘union _SourcePict[0]’ is partly outside array bounds of ‘unsigned char[32]’ [-Werror=array-bounds=]
906 | pPicture->pSourcePict->linear.type = SourcePictTypeLinear;
| ^~
../render/picture.c:899:45: note: object of size 32 allocated by ‘malloc’
899 | pPicture->pSourcePict = (SourcePictPtr) malloc(sizeof(PictLinearGradient));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../render/picture.c: In function ‘CreateConicalGradientPicture’:
../render/picture.c:989:26: error: array subscript ‘union _SourcePict[0]’ is partly outside array bounds of ‘unsigned char[32]’ [-Werror=array-bounds=]
989 | pPicture->pSourcePict->conical.type = SourcePictTypeConical;
| ^~
../render/picture.c:982:45: note: object of size 32 allocated by ‘malloc’
982 | pPicture->pSourcePict = (SourcePictPtr) malloc(sizeof(PictConicalGradient));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
```
[build.log](/uploads/d313d0e0e08c1d6c1941752856b48914/build.log)xwayland-23.1.0https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/182sequence lost (0x20000 > 0x12320) in reply type 0xc!2023-03-06T11:18:20ZAlexander Jenischsequence lost (0x20000 > 0x12320) in reply type 0xc!Steam is spamming this when running from console. Rarely I see the following:
`Xlib: sequence lost (0x20000 > 0x106e3) in reply type 0x21!`
world/libx11 1.8.3-6 (from arch repos)Steam is spamming this when running from console. Rarely I see the following:
`Xlib: sequence lost (0x20000 > 0x106e3) in reply type 0x21!`
world/libx11 1.8.3-6 (from arch repos)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1426Plan for Xwayland 23.12023-03-23T08:21:39ZOlivier FourdanPlan for Xwayland 23.1It's that time of year already when we have to start to think about a new release of Xwayland.
There's been quite a few changes that already deserve a release, but there are also pending merge requests that we may want to consider befor...It's that time of year already when we have to start to think about a new release of Xwayland.
There's been quite a few changes that already deserve a release, but there are also pending merge requests that we may want to consider before a new yearly release.
The purpose of this is to list the things we *might* want to consider, it does not mean that everything listed here *must* be part of the new release though - we can decide to leave a pending merge request for later, and put a comment here on why we chose to do so.
Please note this is primarily intended to gather developer's feedback, it not meant as a poll for users to vote for their favorite fix/feature.
FWIW, I went quickly -i.e. I might have missed a few- through the list of MR for Xwayland and glamor and identified the following candidates:
- [x] [dix: switch scroll button emulation to multiples of increment](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1059)
- [x] [present: Send a PresentConfigureNotify event for destroyed windows](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1057)
- [x] [xwayland: Use {wl_,xdg-}output name for XRandR](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1056)
- [x] [xwayland: fix GBM on driver without explicit modifiers](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1054)
- [x] [glamor: Don't initialize on softpipe](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1033)
- [ ] [xwayland: Support CHERI/Morello by not storing pointers in uint64_t](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1008)
- [~] [Draft: Add EI support (based on @whot's branch)](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/975)
- [ ] [Implement DRI3 v1.3 and per-surface dmabuf feedback](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/969)
- [ ] [Use linux_dmabuf v4 when available to get the DRM device](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/968)
- [~] [Explicit GPU Synchronization for DRI3, Present, and Xwayland](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967)
- [ ] [glamor: supports GLES3 shaders](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/948)
- [ ] [xwayland: Detect gbm_bo_get_fd_for_plane at runtime](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/946)
- [~] [glamor: Use render node for glamor device path where possible](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/944)
- [ ] [xwayland: fix glamor es black windows](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/934)
- [ ] [glamor: fix for 8bit fonts and PointSize on GLES 2](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/924)
- [ ] [glamor cleanups](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/920)
- [ ] [glamor: fix mirrored glyphs on big-endian machines](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/919)
- [~] [glamor: add glamor EGL vendor](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/914)
- [ ] [glamor: use glEGLImageTargetTexture2DOES during copy to update image texture](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/898)
- [x] [Xwayland: Implement linux_dmabuf v4 feedback support](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/818)
- [~] [Draft: xwayland: Multi DPI support via global factor rescaling [updated using properties]](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733)
- [ ] [glamor: Fix xRGB->ARGB composite in certain cases](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/732)
- [ ] [xwayland: Implement wp_tearing_control_v1](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/665)
- [ ] [glamor: Fix rendering of pixmap textures backed by EGLImageKHR image](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/568)
- [~] [glamor: Require and use GL_ARB_sampler_objects](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/506)
- [~] [glamor: Learn about GL_EXT_blend_func_extended](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/505)
- [x] [XWayland high-resolution scroll wheel support](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/118)
Xwayland hi-res scroll support support would be interesting, as it would fix an historical discrepancy between compositors that causes spurious scroll events with some compositors (such as sway or kwin). Also related, we have a regression in master currently that was [discovered when that change was backported in the stable branch](https://gitlab.freedesktop.org/xorg/xserver/-/issues/1392) and [reverted in the stable branch only](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/988) - Should we also revert commit e37eeb7a in the master branch?
/cc @daenzer @whot @ajax @anholt
PS: I also created a milestone %"xwayland-23.1.0" for this purposexwayland-23.1.0