xorg issueshttps://gitlab.freedesktop.org/groups/xorg/-/issues2022-12-12T19:09:35Zhttps://gitlab.freedesktop.org/xorg/util/makedepend/-/issues/2makedepend: error: out of space: increase MAXFILES2022-12-12T19:09:35ZDaniel Zorychtamakedepend: error: out of space: increase MAXFILESHello.
I found that last update of makedepend program made some regression. New version during execution returns error code: out of space: increase MAXFILES.
[dnx-rtos-os-fail.zip](/uploads/b5657da2714018f36aecb235160778ff/dnx-rtos-os-...Hello.
I found that last update of makedepend program made some regression. New version during execution returns error code: out of space: increase MAXFILES.
[dnx-rtos-os-fail.zip](/uploads/b5657da2714018f36aecb235160778ff/dnx-rtos-os-fail.zip)
In the attachment there is part of my project (very simplified). To run test you need to extract archive. In the project's root directory just enter: "make".
Makefile runs only dependencies application (makedepend). In version 1.0.6 the makedepend program does not return any error, in version 1.0.7 does.
The result of the command is a file with argument list passed to the makedepend - makedepend.args. In both versions of makedepend file is the same. The strange is that the number of files does not exceed 4096 or even 256 files.
This code I have tested on two computers with openSUSE. Before update everything was working ok, after update not.
Working version of makdepend: 1.0.6
Not working version of makedepend: 1.0.7
Error visible in terminal:
/usr/bin/makedepend: error: out of space: increase MAXFILES
Best Regards,
Danielhttps://gitlab.freedesktop.org/xorg/lib/libxft/-/issues/17libxft-2.3.7: Bold fonts in urxvt missing leftmost pixels2022-11-27T22:48:06ZPeter Kästlelibxft-2.3.7: Bold fonts in urxvt missing leftmost pixels98e27ba4b2c3a4825a3497cd481992374a9c9e98 introduces a bug, which causes bold fonts to miss leftmost pixels in urxvt with .Xdefaults setting:
urxvt*font: xft:MiscFixed:autohint=true:antialias=false:pixelsize=10
Please see the bold "b":
2...98e27ba4b2c3a4825a3497cd481992374a9c9e98 introduces a bug, which causes bold fonts to miss leftmost pixels in urxvt with .Xdefaults setting:
urxvt*font: xft:MiscFixed:autohint=true:antialias=false:pixelsize=10
Please see the bold "b":
2.3.6 (good):![with_libxft-2.3.6](/uploads/3d8ef53f11ca53e8b1e73ec3f86360d6/with_libxft-2.3.6.png)
2.3.7 (left pixels missing): ![with_libxft-2.3.7](/uploads/a887c976f10f6a42cfb128fc0840228d/with_libxft-2.3.7.png)Thomas E. DickeyThomas E. Dickeyhttps://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/168libx11 1.8.2 causes firefox to freeze when highlighting text2023-03-08T16:15:27Zrockybulwinklelibx11 1.8.2 causes firefox to freeze when highlighting textMy platform is Arch Linux, running KDE, X11, Nvidia GPU.
I am getting intermittent freezes in firefox. It appears to happen when I highlight text. When it does happen, firefox becomes completely unresponsive. I haven't observed it happe...My platform is Arch Linux, running KDE, X11, Nvidia GPU.
I am getting intermittent freezes in firefox. It appears to happen when I highlight text. When it does happen, firefox becomes completely unresponsive. I haven't observed it happening in other applications, but I also don't highlight nearly as often in other applications.
I've narrowed down the package that causes the issue to Arch Linux's upgrade from libx11 1.8.1 to 1.8.2.
Initially a bug was opened in firefox, documented here: https://bugzilla.mozilla.org/show_bug.cgi?id=1800903https://gitlab.freedesktop.org/xorg/app/quartz-wm/-/issues/13xquartz can't display matlab2023-01-04T23:41:01Zcqwang2018xquartz can't display matlabHi, When I ssh to Linux server using xquartz, it will present a "black screen Matlab window", but for gedit is normal. do you have some suggestions?Hi, When I ssh to Linux server using xquartz, it will present a "black screen Matlab window", but for gedit is normal. do you have some suggestions?https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/167Em dash missing from WM_NAME with libx11-1.8.22022-12-10T14:31:17ZDan SeminaraEm dash missing from WM_NAME with libx11-1.8.2Firefox's window title generally looks like "Web Page Title — Mozilla Firefox", but after upgrading libx11 from 1.8.1 to 1.8.2, it now looks like "Web Page Title Mozilla Firefox". The em dash that was previously in the title is somehow ...Firefox's window title generally looks like "Web Page Title — Mozilla Firefox", but after upgrading libx11 from 1.8.1 to 1.8.2, it now looks like "Web Page Title Mozilla Firefox". The em dash that was previously in the title is somehow getting dropped.
Reproduced on Arch Linux with XMonad 0.17.1.
Attached is a video showing the problem.
[simplescreenrecorder-2022-11-16_22.03.25.mkv](/uploads/4e6cdd74c567cbeae11304429716f6a4/simplescreenrecorder-2022-11-16_22.03.25.mkv)https://gitlab.freedesktop.org/xorg/lib/libxft/-/issues/16Stack gets smashed in fonts with colors when calling XftGlyphRender2022-11-15T00:34:22ZscoreStack gets smashed in fonts with colors when calling XftGlyphRenderI encountered this issue in rxvt-unicode by setting the font to `xft:Source Code Pro:pixelsize=20:antialias=false,xft:IPA Gothic`, making the terminal fullscreen on a 1440p monitor (resulting in 196 columns, lower values seem not to trig...I encountered this issue in rxvt-unicode by setting the font to `xft:Source Code Pro:pixelsize=20:antialias=false,xft:IPA Gothic`, making the terminal fullscreen on a 1440p monitor (resulting in 196 columns, lower values seem not to trigger the bug), viewing the iptables-extensions man page and scrolling to the bottom. At some point, the terminal crashes and the traceback is a little unclear, but I found in GDB that by the time `_XftCompositeText` is called, `elts` == `elts_local` and yet `nelt` is 130 (indicating that 130 elements were written to an array of size 128).
It seems the cause was introduced in commit 6a08279e:
```diff
@@ -335,7 +362,7 @@ XftGlyphSpecRender (Display *dpy,
}
elts = elts_local;
- if (nelt > NUM_ELT_LOCAL)
+ if (!font->info.color && nelt > NUM_ELT_LOCAL)
{
elts = AllocGlyphElt8Array (nelt);
if (!elts)
```
This looks to my eye like it might be a typo of `font->info.color || nelt > NUM_ELT_LOCAL` (as `nelt` exceeding `NUM_ELT_LOCAL` indicates that we expect to exceed the bounds of the array, and that should always be grounds for allocating a larger one), but I don't know nearly enough about the code to understand why the condition includes `color`, so it might even have been included in error.
The problem was encountered in version 2.3.6 and reproduced in the git version at de4592a18bba0bfc88232f6f4ecad7c2fa5e616eThomas E. DickeyThomas E. Dickeyhttps://gitlab.freedesktop.org/xorg/lib/libxaw3d/-/issues/5Build failure with upcoming Clang 16 (-Wincompatible-function-pointer-types)2023-05-13T00:41:54ZSam JamesBuild failure with upcoming Clang 16 (-Wincompatible-function-pointer-types)Clang 16 will make -Wincompatible-function-pointer-types an error by default.
You can emulate this error using:
GCC via -Werror=incompatible-pointer-types (GCC lacks a more specific
warning for just func. ptrs)
Clang <16 via -Wer...Clang 16 will make -Wincompatible-function-pointer-types an error by default.
You can emulate this error using:
GCC via -Werror=incompatible-pointer-types (GCC lacks a more specific
warning for just func. ptrs)
Clang <16 via -Werror=incompatible-function-pointer-types
Originally reported downstream in Gentoo at https://bugs.gentoo.org/880969.
Full build log: https://bugs.gentoo.org/attachment.cgi?id=831315 (bzip2'd).
Error:
```
libtool: compile: clang -DHAVE_CONFIG_H -I. -I.. -I../include -DXAW_INTERNATIONALIZATION -DXAW_GRAY_BLKWHT_STIPPLES -DXAW_ARROW_SCROLLBARS -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wimplicit -Wnonnull -Winit-self -Wmain -Wmissing-braces -Wsequence-point -Wreturn-type -Wtrigraphs -Warray-bounds -Wwrite-strings -Waddress -Wint-to-pointer-cast -Wpointer-to-int-cast -fno-strict-aliasing -pipe -march=native -fno-diagnostics-color -O2 -Werror=implicit-function-declaration -Werror=implicit-int -c MenuButton.c -fPIC -DPIC -o .libs/MenuButton.o
XawIm.c:1376:6: error: incompatible function pointer types passing
'void (Widget)' (aka 'void (struct _WidgetRec *)') to parameter of type
'XtEventHandler' (aka 'void (*)(struct _WidgetRec *, void *, union _XEvent
*, char *)') [-Werror,-Wincompatible-function-pointer-types]
XawVendorShellExtResize, (XtPointer)NULL );
^~~~~~~~~~~~~~~~~~~~~~~
/usr/include/X11/Intrinsic.h:840:31: note: passing argument to parameter here
XtEventHandler /* proc */,
^
1 warning and 1 error generated.
[...]
```https://gitlab.freedesktop.org/xorg/lib/libxft/-/issues/15XftFontLoadGlyphs for mono font returns wrong info in extents from XftTextExt...2022-11-27T22:44:20ZScott McdermottXftFontLoadGlyphs for mono font returns wrong info in extents from XftTextExtentsUtf8 for variable chars`XftTextExtentsUtf8()` is returning `xOff` member of `extents` with seemingly the wrong value when variable fonts are in use, in particular when ligatures are present in the monospace font. `xOff` seems to be populated with the largest ...`XftTextExtentsUtf8()` is returning `xOff` member of `extents` with seemingly the wrong value when variable fonts are in use, in particular when ligatures are present in the monospace font. `xOff` seems to be populated with the largest width of any character present, and some ligatures (like for `<=>`) are 3x the "normal" character size. This causes terminals like `st` which rely on xOff extent value to render the fonts with huge inter-glyph spaces (ie unusable), and `urxvt` to reject the font.
This happens for me with Inconsolata font, the old version works fine, but using Inconsolata 3 (which is a variable font with ligatures), it has massive spaces between chars.
(https://fonts.google.com/download?family=Inconsolata and extract just `Inconsolata-VariableFont_wdth,wght.ttf`)
Github issue for background here: https://github.com/googlefonts/Inconsolata/issues/42
in [this comment on that bug](https://github.com/googlefonts/Inconsolata/issues/42#issuecomment-791452847), a fix was offered, which still seems to work with the master `libxft` branch:
``` diff
diff --git a/src/xftglyphs.c b/src/xftglyphs.c
index 7f89e24..3a3dfd2 100644
--- a/src/xftglyphs.c
+++ b/src/xftglyphs.c
@@ -847,11 +847,11 @@ XftFontLoadGlyphs (Display *dpy,
if (font->info.load_flags & FT_LOAD_VERTICAL_LAYOUT)
{
xftg->metrics.xOff = 0;
- xftg->metrics.yOff = (short)(-font->public.max_advance_width);
+ xftg->metrics.yOff = (short)(-TRUNC(ROUND(glyphslot->advance.y)));
}
else
{
- xftg->metrics.xOff = (short)(font->public.max_advance_width);
+ xftg->metrics.xOff = (short)(TRUNC(ROUND(glyphslot->advance.x)));
xftg->metrics.yOff = 0;
}
}
```
As this seems to fix the issue, if it is the right fix, could you please apply? Thanks.
P.S. original patch author @JasonBrownDeveloper had used `advance.x` for both, which I assumed was a typo.Thomas E. DickeyThomas E. Dickeyhttps://gitlab.freedesktop.org/xorg/lib/libxcb-errors/-/issues/1License questions2022-11-08T17:52:47ZwerdahiasLicense questionsI'm in the process of packaging libxcb-errors for debian. I have some questions regarding the license on the files under m4/.
As far as I am concerned `ax_compare_version.m4` is licensed under the included license.
Neither `xcb_util_com...I'm in the process of packaging libxcb-errors for debian. I have some questions regarding the license on the files under m4/.
As far as I am concerned `ax_compare_version.m4` is licensed under the included license.
Neither `xcb_util_common.m4` nor `xcb_util_common_with_include_path.m4` contain any license notice nor is there a license for them in the upstream repo.
Please clarify how they are licensed.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1403Xwayland: segfault when trying to run gamescope2022-11-07T11:11:18ZMike Yuanme@yhndnzj.comXwayland: segfault when trying to run gamescopeWhen trying to use [gamescope](https://github.com/Plagman/gamescope) to start a game, `Xwayland` in the outer space (in my case running on sway) segfaults. I've tried both `22.1.4` and `22.1.5` but no luck.
Backtrace at https://fars.ee/...When trying to use [gamescope](https://github.com/Plagman/gamescope) to start a game, `Xwayland` in the outer space (in my case running on sway) segfaults. I've tried both `22.1.4` and `22.1.5` but no luck.
Backtrace at https://fars.ee/8Pzwhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1402Back-and-forth wheel events not reaching XWayland window after using touchpad...2023-01-26T09:06:56ZhexchainBack-and-forth wheel events not reaching XWayland window after using touchpad to scrollIt seems that on a laptop, XWayland windows cannot see back-and-forth mouse wheel events after using the touchpad to scroll.
My test method:
1. Use the touchpad to perform some scroll motion
2. Open a terminal and run `xev | grep --line...It seems that on a laptop, XWayland windows cannot see back-and-forth mouse wheel events after using the touchpad to scroll.
My test method:
1. Use the touchpad to perform some scroll motion
2. Open a terminal and run `xev | grep --line-buffered -E '^ButtonPress'`
3. Open another terminal and run `sudo stdbuf -oL libinput debug-events --device /dev/input/event19 | grep 'POINTER_SCROLL_WHEEL'`
4. Position the cursor inside the xev window and move the wheel back and forth for only 1 "tick", repeatedly
libinput recording: [wheel-recording.yaml](/uploads/8dedfa389d392b1e1fb11886992fd89a/wheel-recording.yaml)
It can be observed that `libinput debug-events` reports multiple wheel events, while `xev` sees none, or only one.
With `xinput test-xi2 2` I had some interesting discoveries:
- On a fresh log-in, when scrolling the mouse wheel, the `valuators` of a Motion event looks like "3: 4.00", where the value does not have a decimal part. At this point, there are accompanying ButtonPress/Release events.
- After some touchpad scroll motion this value is no longer an integer, and this issue starts to happen.
This is on Arch Linux, with KDE Plasma 5.26.2 and XWayland 22.1.5.https://gitlab.freedesktop.org/xorg/xserver/-/issues/140022.1.4: Fake keyboard inputs are transferred from the recently closed xwaylan...2022-11-03T09:03:57Zkenji amano22.1.4: Fake keyboard inputs are transferred from the recently closed xwayland window.If I pressed enter to exit an X terminal, when I enter an X terminal again while the focus is on a wayland window, enter key would be pressed repetitively.
This broke my terminal.If I pressed enter to exit an X terminal, when I enter an X terminal again while the focus is on a wayland window, enter key would be pressed repetitively.
This broke my terminal.https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/166Dead key combos for Catalan L·, dotless j, and capital B with stroke have no ...2023-03-05T16:28:27Zjmcwilliams403Dead key combos for Catalan L·, dotless j, and capital B with stroke have no Multi_key counterpartsThe following three existing `<dead_abovedot>` sequences would be easy additions for `<Multi_key> <period> ...` sequences:<br>
```
<dead_abovedot> <j> : "ȷ" U0237 # LATIN SMALL LETTER DOTLESS J
<dead_abovedot> <L> : "Ŀ" U013F # LATIN CAP...The following three existing `<dead_abovedot>` sequences would be easy additions for `<Multi_key> <period> ...` sequences:<br>
```
<dead_abovedot> <j> : "ȷ" U0237 # LATIN SMALL LETTER DOTLESS J
<dead_abovedot> <L> : "Ŀ" U013F # LATIN CAPITAL LETTER L WITH MIDDLE DOT
<dead_abovedot> <l> : "ŀ" U0140 # LATIN SMALL LETTER L WITH MIDDLE DOT
```
Furthermore, there exists `<Multi_key> <slash> <b> : "ƀ"` but no capital counterpart aside from the following `<dead_stroke>` sequence:<br>
```
<dead_stroke> <B> : "Ƀ" U0243 # LATIN CAPITAL LETTER B WITH STROKE
```
As a side note, the following `<Multi_key>` sequences for characters with a comma below should probably be moved to their respective Unicode block:<br>
```
<Multi_key> <semicolon> <S> : "Ș" U0218 # LATIN CAPITAL LETTER S WITH COMMA BELOW
<Multi_key> <S> <semicolon> : "Ș" U0218 # LATIN CAPITAL LETTER S WITH COMMA BELOW
...
<Multi_key> <semicolon> <s> : "ș" U0219 # LATIN SMALL LETTER S WITH COMMA BELOW
<Multi_key> <s> <semicolon> : "ș" U0219 # LATIN SMALL LETTER S WITH COMMA BELOW
...
<Multi_key> <semicolon> <T> : "Ț" U021A # LATIN CAPITAL LETTER T WITH COMMA BELOW
<Multi_key> <T> <semicolon> : "Ț" U021A # LATIN CAPITAL LETTER T WITH COMMA BELOW
...
<Multi_key> <semicolon> <t> : "ț" U021B # LATIN SMALL LETTER T WITH COMMA BELOW
<Multi_key> <t> <semicolon> : "ț" U021B # LATIN SMALL LETTER T WITH COMMA BELOW
```https://gitlab.freedesktop.org/xorg/app/setxkbmap/-/issues/10alt-shift toggles keymap when part of a shortcut2022-11-03T11:07:58ZAvid Seekeralt-shift toggles keymap when part of a shortcutSetting
```
setxkbmap "ara,us" -option grp:alt_shift_toggle
```
causes all shortcuts of the form `alt+shift+[anykey]` to break.
Earliest notice of this issue is from [2016 SE post](https://unix.stackexchange.com/questions/265038/alt-shi...Setting
```
setxkbmap "ara,us" -option grp:alt_shift_toggle
```
causes all shortcuts of the form `alt+shift+[anykey]` to break.
Earliest notice of this issue is from [2016 SE post](https://unix.stackexchange.com/questions/265038/alt-shift-toggles-keymap-when-part-of-a-shortcut).https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/58Screen flickering/tearing on MSI Bravo 15 AMD Ryzen 7 4800H 15.6" 16GB A4DDR-...2022-10-31T11:01:21ZAdvait CScreen flickering/tearing on MSI Bravo 15 AMD Ryzen 7 4800H 15.6" 16GB A4DDR-212IN laptopUbuntu 22.04 Gnome Wayland. I'm experiencing screen flickering/tearing on my MSI Bravo 15 AMD Ryzen 7 4800H 15.6" 16GB A4DDR-212IN laptop. The laptop is about 15 months old and the problem started about 2 weeks ago. The problem does not ...Ubuntu 22.04 Gnome Wayland. I'm experiencing screen flickering/tearing on my MSI Bravo 15 AMD Ryzen 7 4800H 15.6" 16GB A4DDR-212IN laptop. The laptop is about 15 months old and the problem started about 2 weeks ago. The problem does not appear on my HDMI connected external monitor. The problem persists when I switch to Xorg. The problem persists when I boot from an Ubuntu 22.04 USB ISO stik. The problem persists when I switch to another user. prime-select = on demand. Ubuntu is up-to-date.
Let me know if you need any other info. How do I fix this issue? Thanks.
![2022_10_25_Screen_problem__lasted_about_2min_then_cleared](/uploads/a6331ae8e66467ea4bf7626d671b2348/2022_10_25_Screen_problem__lasted_about_2min_then_cleared.jpg)
`advait@advait-Bravo-15-A4DDR:~$ inxi -Fxz
System:
Kernel: 5.15.0-52-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
Desktop: GNOME 42.4 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
Type: Laptop System: Micro-Star product: Bravo 15 A4DDR v: REV:1.0
serial: <superuser required>
Mobo: Micro-Star model: MS-16WK v: REV:1.0 serial: <superuser required>
UEFI: American Megatrends v: E16WKAMS.110 date: 10/29/2020
Battery:
ID-1: BAT1 charge: 51.8 Wh (97.9%) condition: 52.9/51.3 Wh (103.0%)
volts: 12.8 min: 11.4 model: MSI Corp. MS-16WK status: Full
CPU:
Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 8 MiB
Speed (MHz): avg: 1404 high: 1528 min/max: 1400/2900 boost: enabled
cores: 1: 1528 2: 1397 3: 1397 4: 1397 5: 1397 6: 1396 7: 1390 8: 1396
9: 1397 10: 1397 11: 1397 12: 1397 13: 1397 14: 1397 15: 1397 16: 1398
bogomips: 92621
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
vendor: Micro-Star MSI driver: amdgpu v: kernel bus-ID: 03:00.0
Device-2: AMD Renoir vendor: Micro-Star MSI driver: amdgpu v: kernel
bus-ID: 08:00.0
Device-3: Chicony USB 2.0 Webcam Device type: USB driver: uvcvideo
bus-ID: 1-4:2
Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
compositor: gnome-shell driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
resolution: 1920x1080~144Hz
OpenGL: renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.42 5.15.0-52-generic)
v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
Device-1: AMD Navi 10 HDMI Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 03:00.1
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
vendor: Micro-Star MSI driver: N/A bus-ID: 08:00.5
Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 08:00.6
Sound Server-1: ALSA v: k5.15.0-52-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 04:00.0
IF: wlp4s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: f000 bus-ID: 05:00.0
IF: enp5s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-3:2
Report: hciconfig ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 7.74 TiB used: 4.1 TiB (52.9%)
ID-1: /dev/nvme0n1 vendor: Seagate model: FireCuda 520 SSD ZP2000GM30002
size: 1.82 TiB temp: 33.9 C
ID-2: /dev/nvme1n1 vendor: Kingston model: OM8PCP3512F-AI1
size: 476.94 GiB temp: 33.9 C
ID-3: /dev/sda type: USB model: USB Hard Drive size: 1.82 TiB
ID-4: /dev/sdb type: USB vendor: Lenovo model: USB Hard Drive
size: 1.82 TiB
ID-5: /dev/sdc type: USB vendor: Seagate model: BUP Slim size: 1.82 TiB
Partition:
ID-1: / size: 1.79 TiB used: 1.35 TiB (75.6%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 4 KiB (0.0%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 62.0 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: amdgpu temp: 43.0 C fan: 65535 device: amdgpu temp: 41.0 C
Info:
Processes: 449 Uptime: 2h 50m Memory: 38.58 GiB used: 6.43 GiB (16.7%)
Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2951 Shell: Bash
v: 5.1.16 inxi: 3.3.13
advait@advait-Bravo-15-A4DDR:~$`
(next)
`advait@advait-Bravo-15-A4DDR:~$ sudo lshw -c display
[sudo] password for advait:
*-display
description: Display controller
product: Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
version: c1
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:104 memory:d0000000-dfffffff memory:e0000000-e01fffff memory:fe400000-fe47ffff memory:fe480000-fe49ffff
*-display
description: VGA compatible controller
product: Renoir
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:08:00.0
logical name: /dev/fb0
version: c6
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi msix vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
resources: irq:51 memory:b0000000-bfffffff memory:c0000000-c01fffff ioport:e000(size=256) memory:fe300000-fe37ffff memory:c0000-dffff
advait@advait-Bravo-15-A4DDR:~$`https://gitlab.freedesktop.org/xorg/xserver/-/issues/1399[Regression] 1-second lag in closing XWayland menus2022-10-27T18:05:59ZJohn Lindgren[Regression] 1-second lag in closing XWayland menusSince updating xwayland from 22.1.3 to 22.1.4, there is approximately a one-second lag from the time an XWayland menu item is selected until the menu closes. This leads to user confusion as to whether the menu selection took effect or n...Since updating xwayland from 22.1.3 to 22.1.4, there is approximately a one-second lag from the time an XWayland menu item is selected until the menu closes. This leads to user confusion as to whether the menu selection took effect or not, since there is no visual response until one second later.
With 22.1.3, menus close more-or-less instantly.
Bisecting the regression leads to commit to 9e4b7948df5a9a67632bb606150ec171b5519672.
Using:
- Arch Linux
- wlroots master as of today (commit bc416ed7524381dd768a829e1a19a40d114a6123)
- labwc master as of today (commit deb658b672fbf4810de33fb66c973aec20a3ebc6)
Please let me know if there are any other details I can provide.
/cc @ofourdanhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1398Xwayland 22.1.4 is sending random inputs to some application (i.e., Kitty ter...2022-10-25T08:35:35ZD3vil0p3rXwayland 22.1.4 is sending random inputs to some application (i.e., Kitty terminal)<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS an...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
<!--
Provide at least the following information:
* Your OS and version
* Affected Mutter version
* Does this issue appear in XOrg and/or Wayland
-->
* archlinux Kernel: 6.0.2-arch1-1 arch: x86_64 bits with GNOME v: 42.5
* Xwayland 22.1.4
* Issue appearing in Wayland
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
In a clean Arch Linux, GNOME Wayland (with Xwayland) I used Kitty by using `linux_display_server x11` in `kitty.conf` because to retrieve some elements of it like the top bar themed with the system theme, and top bar with the "close", "maximize", "reduce to icon" buttons. It always worked until yesterday.
Yesterday, I noted that, in this new clean fully upgraded machine, when I opened a new kitty terminal, it started to press automatically "CTRL+C" keyboard button and the prompt shell in Kitty terminal goes down indefinitely due to the "Enter" key pressing:
![image](/uploads/ee0d584420e1cfa6c7b05a61a5a0f097/image.png)
Then, if I move the cursor of the mouse on Visual Studio Code, the cursor continues to go down also there, until I don't stop by `CTRL+C`.
This issue does not appear in not-new machines where `pacman -Syyu` has been executed, probably because packages that could break dependencies are not touched by upgrading.
According to the tests, if I downgrade `xorg-xwayland` to `22.1.3`, the Kitty and Code applications work correctly, because Xwayland 22.1.3 does not send these wrong inputs.
This issue seems related to another opened issue by a user some days ago: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1395
### Steps to reproduce
<!--
1. Step one
2. Step two
3. ...
-->
1. I downloaded the latest ISO of Arch Linux (archlinux-2022.10.01-x86_64.iso),
2. After the boot, I run `archinstall` for installing the system.
3. The system has been installed with a standard configuration. In the specific I selected GNOME as Desktop Environment
4. After the installation, I login on the installed Arch system. The version of GNOME is 42.5 with GNOME Wayland, and xorg-xwayland-22.1.4-1 package installed
5. Then, `sudo pacman -Syy kitty` by gnome-terminal
6. Then, always by gnome-terminal, and assuming all kitty windows are closed, I executed `kitty --config=NONE -o linux_display_server=x11 kitty +kitten show_key -m kitty` and I'm getting these inputs automatically:
![image](https://user-images.githubusercontent.com/83867734/197524620-2c178798-05e2-4b85-b392-51ded67eeb94.png)
Note: for reproducing this issue, you need to run `kitty` commands in a terminal different by Kitty terminal itself (here I used gnome-terminal) because it is assumed that the affected applications (in this case Kitty terminal) at the beginning don't have run processes. At the beginning, if you run kitty command, could happen that this weird behavior does not appear, so if it does not appear, close Kitty terminal and always by gnome-terminal, run again `kitty --config=NONE -o linux_display_server=x11 kitty +kitten show_key -m kitty`. For example, in my machine it started to behave in that strange way after the 3rd time I run that kitty command on gnome-terminal.
By a specific inspection, by running `kitty --debug-input --config=NONE -o linux_display_server=x11 kitty +kitten show_key -m kitty`, the logs show that these continuous weird inputs are coming from XKB. When I run the 1st and 2nd time this command in a terminal different from kitty (i.e., gnome-terminal), it seems to work fine. When I run the 3rd time the command above, the Kitty application window appears and closes immediately and the logs show:
```
Loading new XKB keymaps
Modifier indices alt: 0x3 super: 0x6 hyper: 0xffffffff meta: 0xffffffff numlock: 0x4 shift: 0x0 capslock: 0x1
Move x: 365.0 y: 253.0 grabbed: 0
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c mods: ctrl glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: PRESS mods: ctrl text: '' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent key as text to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent key as text to child
```
Starting from the 4th time we run the command above, Xwayland starts to send continuous weird `CTRL+C` input, and the logs of this are:
```
Loading new XKB keymaps
Modifier indices alt: 0x3 super: 0x6 hyper: 0xffffffff meta: 0xffffffff numlock: 0x4 shift: 0x0 capslock: 0x1
Move x: 365.0 y: 253.0 grabbed: 0
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: PRESS mods: none text: 'c' state: 0 sent key as text to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Move x: 415.0 y: 407.0 grabbed: 0
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c text: c mods: none glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: none text: 'c' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c mods: ctrl glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: ctrl text: '' state: 0 sent encoded key to child
Press xkb_keycode: 0x36 clean_sym: c composed_sym: c mods: ctrl glfw_key: 99 (c) xkb_key: 99 (c)
on_key_input: glfw key: 0x63 native_code: 0x63 action: REPEAT mods: ctrl text: '' state: 0 sent encoded key to child
<continues indefinitely>
```
### What did you expect to happen
<!--
What did you expect to do?
-->
Xwayland not sending weird key input to affected applications.
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
Here the discussion with Kitty developers: https://github.com/kovidgoyal/kitty/issues/5620
<!-- Do not remove the following line. -->https://gitlab.freedesktop.org/xorg/xserver/-/issues/1397Xwayland: Pressing Ctrl-D in an xterm to terminate it results in autorepeat o...2022-10-24T15:00:56ZStefan DirschXwayland: Pressing Ctrl-D in an xterm to terminate it results in autorepeat of 'd's in the next xterm that is being startedHow to reproduce
* Open a Wayland session
* Start Gnome terminal
* In the Gnome terminal start an 'xterm'
* This starts an xterm and Xwayland
* ps aux|grep Xwayland
* [...] /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /r...How to reproduce
* Open a Wayland session
* Start Gnome terminal
* In the Gnome terminal start an 'xterm'
* This starts an xterm and Xwayland
* ps aux|grep Xwayland
* [...] /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.I3QEU1 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7
* Terminate the xterm via "Ctrl-D"
* Start again an xterm
* See a never ending autorepeat of 'd's, i.e ddddddddddddddddd... in the new xterm
This is a regression of 22.1.4. Still worked with 22.1.3. I've bisected this and the culprit was
```
commit a1d14aa8c5afbae2f99aa68454d429aed5852b72
Author: Olivier Fourdan <ofourdan@redhat.com>
Date: Mon Oct 17 16:39:30 2022 +0200
xwayland: Clear the "xwl-window" tag on unrealize
Now that we keep the Wayland surface around for longer than the
xwl_window, we might get events for that surface after the X11 window
is unrealized.
Make sure we untag the Wayland surface when the Wayland surface is
delayed, to break the wl_surface/xwl_window relationship, so that events
for that surface are discarded by Xwayland.
Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
Fixes: e37f18ee9 - xwayland: Delay wl_surface destruction
```Olivier FourdanOlivier Fourdanhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1395Xwayland keyboard inputs get constantly repeated after closing an application2022-11-03T09:03:57ZRenan GuilhermeXwayland keyboard inputs get constantly repeated after closing an applicationSince upgrading to xwayland 22.1.4, I am having an issue where keys seem to get "stuck" in the Xwayland environment. I can consistently reproduce this problem using sway, [Dolphin](https://apps.kde.org/dolphin/) and [sxiv](https://github...Since upgrading to xwayland 22.1.4, I am having an issue where keys seem to get "stuck" in the Xwayland environment. I can consistently reproduce this problem using sway, [Dolphin](https://apps.kde.org/dolphin/) and [sxiv](https://github.com/muennich/sxiv), and visualize it using xev.
## How to reproduce:
1. Open Dolphin and xev
2. Through Dolphin, open an image file using sxiv
3. Press `q` to exit sxiv
4. Open an image file using sxiv again
5. Notice that sxiv immediately closes
6. Switch focus to xev
7. Notice that xev is being spammed with KeyPress and KeyRelease events for `q`
## Other notes
* I have bisected this issue to commit 71e8be4e3645bd9664b3f7a9f4d958272d604de4
* I can reproduce this issue in sway 1.7 and KDE Plasma 5.26.1, but not GNOME 42.5, which makes me think this might be related to #1392. I have attached a log I created following [these instructions](https://gitlab.freedesktop.org/xorg/xserver/-/issues/1392#note_1600992) in that issue, although I wasn't able to run any Xwayland applications using this wrapper.
[xwayland-32592.log](/uploads/af192e77709040113e2f5bcf748321cb/xwayland-32592.log)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1394Add a toggle of some kind for pasting the primary selection on middle click2024-01-06T01:27:56ZChristopherJTrentAdd a toggle of some kind for pasting the primary selection on middle clickBinding Middle-Click to pasting the primary selection is behavior that many Linux users have come to expect out of X11.
It's also extremely jarring to people transferring from other operating systems, and causes problems with many piece...Binding Middle-Click to pasting the primary selection is behavior that many Linux users have come to expect out of X11.
It's also extremely jarring to people transferring from other operating systems, and causes problems with many pieces of software which use middle click for other functionality; Firefox uses it for dozens of different operations, all of which can behave unpredictably when the primary selection is dumped into whatever text input might be active when the middle click event occurs.
It would be advantageous for users to have the option to, for example, place a line in their xorg.conf along the lines of MOUSE_3_PASTE=0 to disable that behavior without having to do janky hacks like clearing PRIMARY every time M3 is pressed, or disabling the middle mouse button entirely.