xorg issueshttps://gitlab.freedesktop.org/groups/xorg/-/issues2024-03-26T08:02:25Zhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1655Regression with GLAMOR in Xwayland 23.2.4 and master2024-03-26T08:02:25ZOlivier FourdanRegression with GLAMOR in Xwayland 23.2.4 and master# Summary
Issue was reported upstream initially in vim as https://github.com/vim/vim/issues/14233 and was pointed to me privately.
Visual glitches appear in `gvim` when running in Xwayland. The issue does not occur when GLAMOR is disab...# Summary
Issue was reported upstream initially in vim as https://github.com/vim/vim/issues/14233 and was pointed to me privately.
Visual glitches appear in `gvim` when running in Xwayland. The issue does not occur when GLAMOR is disabled or when running `gvim` on Wayland natively.
# Steps to reproduce
1. Start Weston (easier to reproduce, but affects all compositors the same)
2. Open a large file in `gvim` (aka vim-X11)
3. Select the whole text, press <kbd>U</kbd> (capital U) to put everything uppercase
4. Resize the `gvim` window, some portion of the window start to appear transparent
5. If step 4 did not trigger the issue, retry from step 3, using <kbd>u</kbd> to put everything lowercase
6. Repeat as needed
# Additional data
As it turns out, this is a regression in Xwayland that first appeared between xwayland 23.2.3 and 23.2.4.
A bisection in git pointed at the following commit:
```
2236e3fda2cbae61e87d679ce59fed8d5b0d08d is the first bad commit
commit 02236e3fda2cbae61e87d679ce59fed8d5b0d08d
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Fri Jan 5 18:31:11 2024 +0100
glamor: Don't override source alpha to 1.0 if it's used for blending
It caused an incorrect result of the blend operation.
Use glColorMask to prevent non-1.0 alpha channel values in a depth 32
pixmap backing an effective depth 24 window. For blending operations,
the expectation is that the destination drawable contains valid pixel
values, so the alpha channel should already be 1.0.
Fixes: d1f142891ef3 ("glamor: Ignore destination alpha as necessary for composite operation")
Issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/3104
(cherry picked from commit d1bbf82d72566e16e90800c77cf70fe5fc4ef2e8)
glamor/glamor_render.c | 28 +++++++++++++++++++++++++++-
1 file changed, 27 insertions(+), 1 deletion(-)
```
/cc @daenzer @vstinnerxwayland-24.1.0https://gitlab.freedesktop.org/xorg/xserver/-/issues/1651Plan for Xwayland 24.12024-03-21T13:31:04ZOlivier FourdanPlan for Xwayland 24.1We need to start planning for Xwayland 24.1 (actually, we're already quite late in the year).
So I went through the pending merge requests tagged as „Xwayland“ and put them into 3 categories, new features, structural changes or cleanup,...We need to start planning for Xwayland 24.1 (actually, we're already quite late in the year).
So I went through the pending merge requests tagged as „Xwayland“ and put them into 3 categories, new features, structural changes or cleanup, and bug fixes. Plus a forth one (because I can only count to 4 :wink: ).
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.
# New features:
- [ ] [Explicit GPU Synchronization for DRI3, Present, and Xwayland](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967)
- [~] [Implement DRI3 v1.3 and per-surface dmabuf feedback](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/969)
- [x] [xwayland: Add HiDPI support to Xwayland rootful](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1197)
- [ ] [xwayland/present: Redirect surface window as needed for page flips](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1300)
# Structural changes / cleanup:
- [~] [Use linux_dmabuf v4 when available to get the DRM device](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/968)
- [~] [xwayland/glamor: make wl_drm optional](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/996)
- [x] [xwayland: Move dmabuf code to its own source file](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1111)
- [x] [xwayland: Update lost focus on deactivation](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1213)
- [x] [xwayland/glamor/gbm: simplify render node check](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1237)
- [x] [xwayland: Drop EGLStream backend](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1386)
# Bug fixes:
- [x] [xwayland: correctly report PresentCompleteModeCopy](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1254)
- [~] [hw/xwayland: fix absolute and relative pointer event flags being flipped](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1391)
# Other:
- [~] [xwayland: Detect gbm_bo_get_fd_for_plane at runtime](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/946)
I already took the liberty to gray out those that I do not think we should consider, either because they have already been achieved through another merge request, or because I do not think they are relevant anymore.
There is one huge change which is the [explicit GPU Synchronization](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967) that I would like to see part of Xwayland 24.1 but it;s still pending on other merge requests (such as the protocol changes in both [xorgproto](https://gitlab.freedesktop.org/xorg/proto/xorgproto/-/merge_requests/59) and [wayland-protocols](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90)).
I also created a milestone %"xwayland-24.1.0" for this purpose.xwayland-24.1.0https://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/xserver/-/issues/1445xwayland 23.0.99.901 prerelease - build fails on musl libc2023-03-03T18:20:02Zpsykosexwayland 23.0.99.901 prerelease - build fails on musl libc```
In file included from ../hw/xwayland/xwayland-window-buffers.c:31:
../hw/xwayland/xwayland-window.h:54:5: error: unknown type name 'dev_t'
54 | dev_t drm_dev;
| ^~~~~
```
adding `#include <sys/types.h>` to `xwayland...```
In file included from ../hw/xwayland/xwayland-window-buffers.c:31:
../hw/xwayland/xwayland-window.h:54:5: error: unknown type name 'dev_t'
54 | dev_t drm_dev;
| ^~~~~
```
adding `#include <sys/types.h>` to `xwayland-window.h` works fine as a resolutionxwayland-23.1.0https://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.0https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275server 21.1: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (N...2022-03-21T22:04:17ZBłażej Szczygiełserver 21.1: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)Xserver crashes (NVIDIA 495.46) when compositor uses present extension. It happens on 21.1.2, not tested with previous versions.
Backtrace 1:
```
#0 0x0000000000000000 in ()
#1 0x000055a871063d7d in present_scmd_get_crtc (screen_priv...Xserver crashes (NVIDIA 495.46) when compositor uses present extension. It happens on 21.1.2, not tested with previous versions.
Backtrace 1:
```
#0 0x0000000000000000 in ()
#1 0x000055a871063d7d in present_scmd_get_crtc (screen_priv=0x55a872c82260, window=0x55a872e453e0) at ../xorg-server-21.1.2/present/present_scmd.c:161
#2 0x000055a8710607ee in present_get_crtc (window=0x55a872e453e0) at ../xorg-server-21.1.2/present/present.c:52
#3 0x000055a871064fc4 in present_scmd_pixmap (window=0x55a872e453e0, pixmap=0x55a872e6b9a0, serial=0, valid=0x0, update=0x55a872e6b980, x_off=0, y_off=0, target_crtc=0x0, wait_fence=0x0, idle_fence=0x0, options=0, target_window_msc=0, divisor=1, remainder=0, notifies=0x0, num_notifies=0) at ../xorg-server-21.1.2/present/present_scmd.c:699
#4 0x000055a871060cc3 in present_pixmap (window=0x55a872e453e0, pixmap=0x55a872e6b9a0, serial=0, valid=0x0, update=0x55a872e6b980, x_off=0, y_off=0, target_crtc=0x0, wait_fence=0x0, idle_fence=0x0, options=0, window_msc=0, divisor=1, remainder=0, notifies=0x0, num_notifies=0) at ../xorg-server-21.1.2/present/present.c:243
#5 0x000055a871062eb6 in proc_present_pixmap (client=0x55a872afb9f0) at ../xorg-server-21.1.2/present/present_request.c:146
#6 0x000055a8710632b8 in proc_present_dispatch (client=0x55a872afb9f0) at ../xorg-server-21.1.2/present/present_request.c:257
#7 0x000055a870fc8d9c in Dispatch () at ../xorg-server-21.1.2/dix/dispatch.c:551
#8 0x000055a870fd8191 in dix_main (argc=1, argv=0x7ffd346bead8, envp=0x7ffd346beae8) at ../xorg-server-21.1.2/dix/main.c:272
#9 0x000055a8711c1b27 in main (argc=1, argv=0x7ffd346bead8, envp=0x7ffd346beae8) at ../xorg-server-21.1.2/dix/stubmain.c:34
```
Backtrace 2:
```
#0 0x0000000000000000 in ()
#1 0x00005645b5362e98 in present_flush (window=0x5645b5bd7720) at ../xorg-server-21.1.2/present/present_scmd.c:199
#2 0x00005645b5360b5a in present_execute_copy (vblank=0x5645b5b77620, crtc_msc=58191) at ../xorg-server-21.1.2/present/present_execute.c:88
#3 0x00005645b5363d59 in present_execute (vblank=0x5645b5b77620, ust=969811316, crtc_msc=58191) at ../xorg-server-21.1.2/present/present_scmd.c:622
#4 0x00005645b536350f in present_event_notify (event_id=1, ust=969811316, msc=58191) at ../xorg-server-21.1.2/present/present_scmd.c:379
#5 0x00005645b5360ef0 in present_fake_notify (screen=0x5645b5df4a80, event_id=1) at ../xorg-server-21.1.2/present/present_fake.c:51
#6 0x00005645b5360f3d in present_fake_do_timer (timer=0x5645b5b77710, time=969811, arg=0x5645b5b776e0) at ../xorg-server-21.1.2/present/present_fake.c:61
#7 0x00005645b540ba75 in DoTimer (timer=0x5645b5b77710, now=969811) at ../xorg-server-21.1.2/os/WaitFor.c:276
#8 0x00005645b540bad9 in DoTimers (now=969811) at ../xorg-server-21.1.2/os/WaitFor.c:290
#9 0x00005645b540b7b5 in check_timers () at ../xorg-server-21.1.2/os/WaitFor.c:133
#10 0x00005645b540b84a in WaitForSomething (are_ready=0) at ../xorg-server-21.1.2/os/WaitFor.c:195
#11 0x00005645b52c7bc3 in Dispatch () at ../xorg-server-21.1.2/dix/dispatch.c:492
#12 0x00005645b52d7191 in dix_main (argc=1, argv=0x7ffe50f44968, envp=0x7ffe50f44978) at ../xorg-server-21.1.2/dix/main.c:272
#13 0x00005645b54c0b38 in main (argc=1, argv=0x7ffe50f44968, envp=0x7ffe50f44978) at ../xorg-server-21.1.2/dix/stubmain.c:34
```
---
Attached diff fixes the crash: [present-crash-fix.diff](/uploads/77b05c7b76be45e56447f37950be3092/present-crash-fix.diff)xserver-21.1.x-nexthttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1255touchscreen problem introduced on upgrade of xorg-server and xorg-server-comm...2023-11-20T00:30:53Zd-a-stouchscreen problem introduced on upgrade of xorg-server and xorg-server-common from 1.20.x to 21.1.xUntil recently, when using my touchscreen laptop with arch/xfce4, touching xfce4-panel plugins would cause the menus to open, and then I could choose items from the menu. For example activating a VPN network, or changing wifi connection....Until recently, when using my touchscreen laptop with arch/xfce4, touching xfce4-panel plugins would cause the menus to open, and then I could choose items from the menu. For example activating a VPN network, or changing wifi connection.
After upgrading these packages, this behavior stopped working with several of the plugins.
```
xorg-server (1.20.13-3 upgraded to 21.1.1-3)
xorg-server-common 1.20.13-3 upgraded to 21.1.1-3)
```
I've observed the problem with: pulseaudio, power manager, notifications, and anything in the status tray, most notably wifi and bluetooth. (Some other plugins, such as the clock, still work correctly.)
Now when I touch one of these plugins, the menu will open while my finger is touching the screen. But as soon as I remove my finger from the screen, the menu immediately closes. I can see the contents of the menu, but can't interact with them. Even if I try sliding my finger along the menu, while the menu stays open I'm unable to select anything, and as soon as I lift my finger from the screen the menu immediately closes.
Reverting these packages fixes the problem (the menus stay open on touch).
Here's a screen shot of one of the plugins/menus affected, for reference. After the upgrade, this power manager plugin will only stay open as long as the finger is actually touching the screen, and immediately closes when the finger is removed. Before package upgrade, touching the power icon caused the menu to toggle open (and stay open). A second touch would toggle the menu closed, or you could touch to change brightness or presentation mode, etc.
![Screenshot_2021-11-17_13-47-04](/uploads/feaf771ee3263db7ddefc089fe4b196d/Screenshot_2021-11-17_13-47-04.png)
I'm not sure if this would be a bug that has been introduced, or if it's caused by an API change that hasn't been implemented in the xfce4-panel project. Thanks in advance for any help!xserver-21.1.x-nexthttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1253Out of bounds memory read in ActivateGrabNoDelivery() in 21.1.12023-01-05T05:19:53ZMatthieu HerrbOut of bounds memory read in ActivateGrabNoDelivery() in 21.1.1Xorg 21.1.1 users on OpenBSD experience a crashes in ActivateGrabNoDelivery() in dix/events.c line 3876:
*grabinfo->sync.event = *real_event;
This seem to happen because 23a8b62d34344575f9df9d057fb74bfefa94a77b introduces a bad cas...Xorg 21.1.1 users on OpenBSD experience a crashes in ActivateGrabNoDelivery() in dix/events.c line 3876:
*grabinfo->sync.event = *real_event;
This seem to happen because 23a8b62d34344575f9df9d057fb74bfefa94a77b introduces a bad cast from a DeviceEvent* pointer to InternalEvent* pointer : *real_event is in fact smaller than InternalEvent and since OpenBSD's malloc is stricted than the default Linux one, reading past the DeviceEvent struct causes a segfault rather than just an out of bounds memory read.
So far I've not been able to figure out the proper fix. Maybe someone can help ?xserver-21.1.x-nexthttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1250xorg-server 21.1.1-2 causes artifacts in darktable2022-09-26T14:01:18Zmabodxorg-server 21.1.1-2 causes artifacts in darktableThis is for an up-to-date Arch Linux and AMD GPU (Radeon RX 5600 XT):
The xorg-server update to version 21.1.1-2 is causing an issue with darktable. darktable is then showing green squares as artifacts in the thumbnails.
https://github...This is for an up-to-date Arch Linux and AMD GPU (Radeon RX 5600 XT):
The xorg-server update to version 21.1.1-2 is causing an issue with darktable. darktable is then showing green squares as artifacts in the thumbnails.
https://github.com/darktable-org/darktable/issues/10386
Solution is to downgrade to the following packages from https://archive.archlinux.org/repos/2021/11/09/extra/os/x86_64/:
```
xf86-input-libinput-1.2.0-1-x86_64.pkg.tar.zst
xf86-input-vmmouse-13.1.0-5-x86_64.pkg.tar.zst
xf86-video-amdgpu-21.0.0-1-x86_64.pkg.tar.zst
xf86-video-ati-1 19.1.0-2-x86_64.pkg.tar.zst
xf86-video-fbdev-0.5.0-2-x86_64.pkg.tar.zst
xf86-video-intel-1 2.99.917+916+g31486f40-1-x86_64.pkg.tar.zst
xf86-video-vesa-2.5.0-1-x86_64.pkg.tar.zst
xf86-video-vmware-13.3.0-2-x86_64.pkg.tar.zst
xorg-server-1.20.13-3-x86_64.pkg.tar.zst
xorg-server-common-1.20.13-3-x86_64.pkg.tar.zst
xorg-xrdb-1.2.1-1-x86_64.pkg.tar.zst
```xserver-21.1.x-nexthttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1249Unable to load xkb keymap with custom xkb_types after upgrade to 21.12023-05-28T23:23:41ZLuke ArmsUnable to load xkb keymap with custom xkb_types after upgrade to 21.1I use a custom keymap to make modifiers and shortcuts more interchangeable with macOS, including an `xkb_type` called `COMMAND_OPTION`, which typically appears as the last type in the `.xkb` file produced by `xkbcomp` ([attached](/upload...I use a custom keymap to make modifiers and shortcuts more interchangeable with macOS, including an `xkb_type` called `COMMAND_OPTION`, which typically appears as the last type in the `.xkb` file produced by `xkbcomp` ([attached](/uploads/44513aaff5712d11ce81a4da9664fc5f/lk-macos-tenkeyless-full.xkb)).
For reference, here's the keymap description I use (it's a pretty standard US pc105 keymap with a few extras added):
```
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete+command_option" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+inet(evdev)+lk_platform+macos+tenkeyless" };
xkb_geometry { include "pc(pc105)" };
};
```
It stopped working after Arch Linux updated xorg-server to 21.1 and I believe it's related to de940e06 (`xkb: fix key type index check in _XkbSetMapChecks`). Here's the error emitted by `xkbcomp`:
```
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 135 (XKEYBOARD)
Minor opcode of failed request: 9 (XkbSetMap)
Value in failed request: 0x1571001c
Serial number of failed request: 124
Current serial number in output stream: 130
```
If I temporarily remove the symbols that reference `COMMAND_OPTION` from the keymap, it loads without issue, and if I subsequently load the full keymap, it loads successfully. It also works--in one operation--if I move `COMMAND_OPTION` to second-last place in the `xkb_types` list, presumably because I don't have any references to `FOUR_LEVEL_KEYPAD`, which is now last, elsewhere in my keymap. (I'm taking advantage of this as a workaround.)
It's not clear to me if this error relates to the index check implementation in `xkb.c` or the way keymaps are loaded by `xkbcomp`, so please let me know if I should file this elsewhere, but I figured it was an edge case worth reporting in case there are wider ramifications. (I realise my keymap might be invalid, too -- but given it's been working until now, it would be good to know how I broke it if so, and I'll plug the documentation gap as best I can.)xserver-21.1.x-nexthttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1248Unable to compile on Arch Linux - unknown type name ‘SHA1_CTX’2021-11-13T16:32:52ZAlex OleshkevichUnable to compile on Arch Linux - unknown type name ‘SHA1_CTX’I have the following issue during compilation:
```
[160/668] Compiling C object xkb/liblibxserver_xkb.a.p/xkbActions.c.o
../xorg-server-21.1.1/xkb/xkbActions.c: In function ‘_XkbFilterLockGroup’:
../xorg-server-21.1.1/xkb/xkbActions.c:40...I have the following issue during compilation:
```
[160/668] Compiling C object xkb/liblibxserver_xkb.a.p/xkbActions.c.o
../xorg-server-21.1.1/xkb/xkbActions.c: In function ‘_XkbFilterLockGroup’:
../xorg-server-21.1.1/xkb/xkbActions.c:406:29: warning: declaration of ‘filter’ shadows a parameter [-Wshadow]
406 | XkbFilterPtr filter = _XkbNextFreeFilter(xkbi);
| ^~~~~~
../xorg-server-21.1.1/xkb/xkbActions.c:374:34: note: shadowed declaration is here
374 | XkbFilterPtr filter, unsigned keycode, XkbAction *pAction)
| ~~~~~~~~~~~~~^~~~~~
[177/668] Compiling C object os/liblibxserver_os.a.p/rpcauth.c.o
In file included from ../xorg-server-21.1.1/os/rpcauth.c:47:
/usr/include/tirpc/rpc/rpc.h:83:12: warning: redundant redeclaration of ‘bindresvport’ [-Wredundant-decls]
83 | extern int bindresvport(int, struct sockaddr_in *);
| ^~~~~~~~~~~~
In file included from /usr/include/tirpc/rpc/rpc.h:40,
from ../xorg-server-21.1.1/os/rpcauth.c:47:
/usr/include/netinet/in.h:507:12: note: previous declaration of ‘bindresvport’ with type ‘int(int, struct sockaddr_in *)’
507 | extern int bindresvport (int __sockfd, struct sockaddr_in *__sock_in) __THROW;
| ^~~~~~~~~~~~
[188/668] Compiling C object os/liblibxserver_os.a.p/xsha1.c.o
FAILED: os/liblibxserver_os.a.p/xsha1.c.o
cc -Ios/liblibxserver_os.a.p -Ios -I../xorg-server-21.1.1/os -IXext -I../xorg-server-21.1.1/Xext -IXi -I../xorg-server-21.1.1/Xi -Icomposite -I../xorg-server-21.1.1/composite -Idamageext -I../xorg-server-21.1.1/damageext -Iexa -I../xorg-server-21.1.1/exa -Ifb -I../xorg-server-21.1.1/fb -Iglamor -I../xorg-server-21.1.1/glamor -Imi -I../xorg-server-21.1.1/mi -Imiext/damage -I../xorg-server-21.1.1/miext/damage -Imiext/shadow -I../xorg-server-21.1.1/miext/shadow -Imiext/sync -I../xorg-server-21.1.1/miext/sync -Idbe -I../xorg-server-21.1.1/dbe -Idri3 -I../xorg-server-21.1.1/dri3 -Iinclude -I../xorg-server-21.1.1/include -Ipresent -I../xorg-server-21.1.1/present -Irandr -I../xorg-server-21.1.1/randr -Irender -I../xorg-server-21.1.1/render -Ixfixes -I../xorg-server-21.1.1/xfixes -I/usr/include/X11/dri -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/tirpc -flto=auto -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -DHAVE_DIX_CONFIG_H -fno-strict-aliasing -fvisibility=hidden -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -march=x86-64 -mtune=generic -O2 -pipe -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fPIC -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -DCLIENTIDS -MD -MQ os/liblibxserver_os.a.p/xsha1.c.o -MF os/liblibxserver_os.a.p/xsha1.c.o.d -o os/liblibxserver_os.a.p/xsha1.c.o -c ../xorg-server-21.1.1/os/xsha1.c
../xorg-server-21.1.1/os/xsha1.c: In function ‘x_sha1_init’:
../xorg-server-21.1.1/os/xsha1.c:50:5: error: unknown type name ‘SHA1_CTX’
50 | SHA1_CTX *ctx = malloc(sizeof(*ctx));
| ^~~~~~~~
../xorg-server-21.1.1/os/xsha1.c:54:5: error: implicit declaration of function ‘SHA1Init’ [-Werror=implicit-function-declaration]
54 | SHA1Init(ctx);
| ^~~~~~~~
../xorg-server-21.1.1/os/xsha1.c:54:5: warning: nested extern declaration of ‘SHA1Init’ [-Wnested-externs]
../xorg-server-21.1.1/os/xsha1.c: In function ‘x_sha1_update’:
../xorg-server-21.1.1/os/xsha1.c:61:5: error: unknown type name ‘SHA1_CTX’
61 | SHA1_CTX *sha1_ctx = ctx;
| ^~~~~~~~
../xorg-server-21.1.1/os/xsha1.c:63:5: error: implicit declaration of function ‘SHA1Update’; did you mean ‘sha1_update’? [-Werror=implicit-function-declaration]
63 | SHA1Update(sha1_ctx, data, size);
| ^~~~~~~~~~
| sha1_update
../xorg-server-21.1.1/os/xsha1.c:63:5: warning: nested extern declaration of ‘SHA1Update’ [-Wnested-externs]
../xorg-server-21.1.1/os/xsha1.c: In function ‘x_sha1_final’:
../xorg-server-21.1.1/os/xsha1.c:70:5: error: unknown type name ‘SHA1_CTX’
70 | SHA1_CTX *sha1_ctx = ctx;
| ^~~~~~~~
../xorg-server-21.1.1/os/xsha1.c:72:5: error: implicit declaration of function ‘SHA1Final’ [-Werror=implicit-function-declaration]
72 | SHA1Final(result, sha1_ctx);
| ^~~~~~~~~
../xorg-server-21.1.1/os/xsha1.c:72:5: warning: nested extern declaration of ‘SHA1Final’ [-Wnested-externs]
cc1: some warnings being treated as errors
[193/668] Compiling C object os/liblibxserver_os.a.p/xstrans.c.o
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...
-> error making: xorg-server-bug865
```
I am installing patched xorg-server-bug865 using `yay`.
What do I miss here?
**Libs**
lib32-openssl 1:1.1.1.l-1
openssl 1.1.1.l-1
openssl-1.0 1.0.2.u-1
**AUR package**
https://aur.archlinux.org/packages/xorg-server-bug865/
**Build script**
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=xorg-server-bug865xserver-21.1.x-nexthttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1225"xwayland/glx: Enable sRGB fbconfigs" broke ~40% of VK-GL-CTS deqp_gles312022-03-21T22:04:17ZMichel Dänzer"xwayland/glx: Enable sRGB fbconfigs" broke ~40% of VK-GL-CTS deqp_gles31Unfortunately, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/664 broke a lot (almost 40%) of tests in the VK-GL-CTS `deqp_gles31` profile (both with llvmpipe and radeonsi on Navi 14).
Not sure it's directly related, but F...Unfortunately, https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/664 broke a lot (almost 40%) of tests in the VK-GL-CTS `deqp_gles31` profile (both with llvmpipe and radeonsi on Navi 14).
Not sure it's directly related, but FWIW, the first GLX visual listed by `glxinfo` is marked as sRGB capable with it.
Shall we revert it for now and try again later?
(Might also be nice to add something to CI which could have caught this)xwayland-22.1.0Adam Jacksonajax@nwnk.netAdam Jacksonajax@nwnk.nethttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1219Steam freezes in certain cases on XWayland2022-03-21T22:04:16ZSefa Eyeoglucontact@scrumplex.netSteam freezes in certain cases on XWayland# Description
Steam freezes in some cases running on XWayland. I can reproduce the issue by connecting a controller (DualShock 4 or Steam Controller). After Steam initializes the controller it just freezes. After some testing it seems to...# Description
Steam freezes in some cases running on XWayland. I can reproduce the issue by connecting a controller (DualShock 4 or Steam Controller). After Steam initializes the controller it just freezes. After some testing it seems to be an issue with XWayland, as I could bisect this issue to a commit.
# `git bisect log`
```
# bad: [d68b50ec032fe4f02bde817abfd30328ec96a11c] Fix compilation with windows.h from latest w32api
# good: [1dbb96ae48f1fa69752e71f25f03d2f733918ffb] Bump version for the Xwayland 21.1.2 release
git bisect start 'd68b50ec032fe4f02bde817abfd30328ec96a11c' 'xwayland-21.1.2'
# good: [c7730cfe5577ebde006d408f502766d8c3a73670] xwayland: Translate keyboard grabs on the root window
git bisect good c7730cfe5577ebde006d408f502766d8c3a73670
# good: [407a2234b32d9cb3fed2cc7e8069bb41b98e143f] test/xi2: Update tests for gesture event types
git bisect good 407a2234b32d9cb3fed2cc7e8069bb41b98e143f
# good: [b6d54b0f5d2fb3dc8a4b2812bfee94112c332256] present: Dispatch clear_window_flip via present_screen_priv hook
git bisect good b6d54b0f5d2fb3dc8a4b2812bfee94112c332256
# bad: [31d2ebca77fcabec81194ae6dcd724c699b1b513] xwayland/present: Drop target_msc member from struct xwl_present_event
git bisect bad 31d2ebca77fcabec81194ae6dcd724c699b1b513
# good: [0c0cbbc7cb4fa917a2b33494efb6dc03e5de9051] present: Remove present_wnmd_info_rec
git bisect good 0c0cbbc7cb4fa917a2b33494efb6dc03e5de9051
# good: [fc53e3c536b5a338c595b5724c7d0b4734e45871] xwaland/present: Drop flip_pending member of struct xwl_present_window
git bisect good fc53e3c536b5a338c595b5724c7d0b4734e45871
# bad: [f8c086b2145d1c9364e9b43ff4d796791d8af169] xwayland/present: Fold xwl_present_event_notify into its caller
git bisect bad f8c086b2145d1c9364e9b43ff4d796791d8af169
# bad: [4503c8d9ea7df5bda470501e638a730d91d718c9] xwayland/present: Fold xwl_present_idle_notify into its caller
git bisect bad 4503c8d9ea7df5bda470501e638a730d91d718c9
# bad: [b2a06e0700fa48c1e77fc687e6af39a4bb7c2ceb] xwayland/present: Drop sync_flip member of struct xwl_present_window
git bisect bad b2a06e0700fa48c1e77fc687e6af39a4bb7c2ceb
# first bad commit: [b2a06e0700fa48c1e77fc687e6af39a4bb7c2ceb] xwayland/present: Drop sync_flip member of struct xwl_present_window
```
First bad commit: b2a06e0700fa48c1e77fc687e6af39a4bb7c2ceb
# Reproduction
0. Run XWayland with b2a06e0700fa48c1e77fc687e6af39a4bb7c2ceb or later
1. Start Steam
2. Connect your controller (probably doesn't matter which one)
3. Observe how Steam freezes shortly after
I suspect that this issue occurs because of Steam trying to show a little popup informing about the controller's profile.
---
See https://github.com/ValveSoftware/steam-for-linux/issues/7992 for additional info and a video demonstration.xwayland-22.1.0https://gitlab.freedesktop.org/xorg/xserver/-/issues/1210Xwayland: GIMP foreground selection tool doesn't work properly with xwayland2021-10-18T12:17:44ZAlexXwayland: GIMP foreground selection tool doesn't work properly with xwaylandForeground selection tool doesn't work as it under Wayland. Instead of showing line that is being currently drawn, it shows a rectangle.
![Screenshot_from_2021-08-11_01-18-05](/uploads/a53ef6c18bf209070fe108cd94e9d317/Screenshot_from_202...Foreground selection tool doesn't work as it under Wayland. Instead of showing line that is being currently drawn, it shows a rectangle.
![Screenshot_from_2021-08-11_01-18-05](/uploads/a53ef6c18bf209070fe108cd94e9d317/Screenshot_from_2021-08-11_01-18-05.png)
This issue doesn't occur if GIMP is running under X.Org
![Untitled__1_](/uploads/32ccfd07f2d6b710201abc7fd774df6c/Untitled__1_.png)
This bug exists for quite some time (I think way over 3 months).
Doesn't seem to depend on hardware/drivers, as I had this issue both on Intel iGPU and AMD iGPU.
It also appears in multiple Linux distributions (openSUSE https://bugzilla.opensuse.org/show_bug.cgi?id=1189310 , Fedora https://gitlab.gnome.org/GNOME/gimp/-/issues/7013 ) and under different DEs (Gnome, KDE).xserver-21.1https://gitlab.freedesktop.org/xorg/xserver/-/issues/1193Xorg-server 21.0.99.2 crashes on intel Icelake and Tigerlake2022-03-21T22:04:17ZMark HerbertXorg-server 21.0.99.2 crashes on intel Icelake and TigerlakeDoes not start at all, segfault
Reverting "modesetting: Use GAMMA_LUT when available" allows the Xorg server to start.Does not start at all, segfault
Reverting "modesetting: Use GAMMA_LUT when available" allows the Xorg server to start.xserver-21.1https://gitlab.freedesktop.org/xorg/xserver/-/issues/1181Crash in __glXDisp_QueryServerString due to client==NULL since 5163fc8b on Wa...2021-12-22T02:32:59Zshoober420Crash in __glXDisp_QueryServerString due to client==NULL since 5163fc8b on Wayland (-fipa-pta+-flto=auto)As of this post on May 30th, there are 22 new commits today, and upon updating to git master when awaking today (i check for git master updates daily) Steam will not launch on my Wayland/Sway/Radeon machine. The error isn’t very interest...As of this post on May 30th, there are 22 new commits today, and upon updating to git master when awaking today (i check for git master updates daily) Steam will not launch on my Wayland/Sway/Radeon machine. The error isn’t very interesting, but i’ll post it anyway. My pure X11/Geforce machine needs reinstalled, but when I’m finished with that, i’ll see if Steam is broken on their as well.
```
@gentoo:~$ sh steamlaunch
/home/lokiju420_-/.local/share/Steam/steam.sh: line 117: VERSION_ID: unbound variable
Couldn't import apt, please install python3-apt or update steamdeps for your distribution.
/home/lokiju420_-/.local/share/Steam/steam.sh: line 117: VERSION_ID: unbound variable
Running Steam on gentoo 64-bit
STEAM_RUNTIME is disabled by the user
Can't find 'steam-runtime-check-requirements', continuing anyway
WARNING: Using default/fallback debugger launch
/home/lokiju420_-/.local/share/Steam/ubuntu12_32/steam
[2021-05-30 08:44:36] Startup - updater built May 27 2021 20:18:12
[2021-05-30 08:44:36] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
Installing breakpad exception handler for appid(steam)/version(1622157314)
XIO: fatal IO error 0 (Success) on X server ":0"
after 8 requests (8 known processed) with 2 events remaining.
```xwayland-22.1.0https://gitlab.freedesktop.org/xorg/xserver/-/issues/1164Excessive logging when async page flip fails2023-11-17T15:13:38ZPovilas KanapickasExcessive logging when async page flip failsThis bug has been extracted out of https://gitlab.freedesktop.org/xorg/xserver/-/issues/871.
As of recent Linux kernel with i915 and recent X master with modesetting driver, applications that request async flips will result in the follo...This bug has been extracted out of https://gitlab.freedesktop.org/xorg/xserver/-/issues/871.
As of recent Linux kernel with i915 and recent X master with modesetting driver, applications that request async flips will result in the following error in the logs for each async flip:
```
[ 4952.118] (WW) modeset(0): flip queue failed: Invalid argument
[ 4952.118] (WW) modeset(0): Present-flip: Queue flip on CRTC 0 failed: Invalid argument
[ 4952.123] (WW) modeset(0): flip queue failed: Invalid argument
[ 4952.123] (WW) modeset(0): Present-flip: Queue flip on CRTC 0 failed: Invalid argument
```
The root cause for failing flips seems to be that the hardware itself can't do async page flips with the modifiers that are being used on the particular CRTC. See https://github.com/torvalds/linux/blob/0f4498cef9f5cd18d7c6639a2a902ec1edc5be4e/drivers/gpu/drm/i915/display/intel_display.c#L12374.
Kernel prints the following error if drm debugging is enabled:
`[ 827.411096] i915 0000:00:02.0: [drm:intel_atomic_check [i915]] Linear memory/CCS does not support async flips`
It seems that there's not much we can do because there's no way to get the information on whether async flip will succeed on a particular CRTC, nor we can pass it to the applications via PresentQueryCapabilities request of the present extension (the capability may change dynamically if the modifiers change).
So at least we should not output logs for every failed async flip as that's will grow logs very fast.
Tested Linux 5.11.0 and 5.12.0-rc4, xserver d231ce2d9ce9644e77e8dbe8c5a23eeb11e85b55.xserver-21.1https://gitlab.freedesktop.org/xorg/xserver/-/issues/1146Xwayland: Cannot open "/var/lib/xkbserver-1.xkm" to write keyboard description2021-03-17T09:37:17ZTomasz Paweł GajcXwayland: Cannot open "/var/lib/xkbserver-1.xkm" to write keyboard descriptionXwayland-21.0.99.902 compiled with meson with options
-Dxkb_dir="%{_datadir}/X11/xkb"
-Dxkb_output_dir="%{_localstatedir}/lib/xkb"
I cannot log in with Plasma-wayland as i got below errors. Ofcourse xserver is compiled without xwaylan...Xwayland-21.0.99.902 compiled with meson with options
-Dxkb_dir="%{_datadir}/X11/xkb"
-Dxkb_output_dir="%{_localstatedir}/lib/xkb"
I cannot log in with Plasma-wayland as i got below errors. Ofcourse xserver is compiled without xwayland.
```
No backend specified through command line argument, trying auto resolution
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Initializing property "rotation" failed
kwin_wayland_drm: Could not find edid for connector 0x22274a0 36
kwin_wayland_drm: Could not find a fitting mode with size=1024x768 and refresh rate 59998 for output 19ca14e7ea
kwin_xkbcommon: XKB: Couldn't process include statement for 'pl(\0)'
kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
kwin_xkbcommon: XKB: Failed to compile xkb_symbols
kwin_xkbcommon: XKB: Failed to compile keymap
kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
glamor: No eglstream capable devices found
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Cannot open "/var/lib/xkbserver-1.xkm" to write keyboard description
> Exiting
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Cannot open "/var/lib/xkbserver-1.xkm" to write keyboard description
> Exiting
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
(EE)
Fatal server error:
(EE) Failed to activate virtual core keyboard: 2(EE)
```xwayland-21.1.0Michel DänzerMichel Dänzerhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1126SDDM gamma set abort2021-06-15T09:25:52ZRoman GilgSDDM gamma set abortOn an Dell XPS 7390 Xserver master fails since 245b9db03a1e1189b992409283e3d88b5d56e62d with:
```
#0 0x00007f995d56f615 in raise () from /usr/lib/libc.so.6
#1 0x00007f995d558862 in abort () from /usr/lib/libc.so.6
#2 0x000055b3fe25b9...On an Dell XPS 7390 Xserver master fails since 245b9db03a1e1189b992409283e3d88b5d56e62d with:
```
#0 0x00007f995d56f615 in raise () from /usr/lib/libc.so.6
#1 0x00007f995d558862 in abort () from /usr/lib/libc.so.6
#2 0x000055b3fe25b99a in OsAbort () at ../../src/xserver/os/utils.c:1327
#3 0x000055b3fe2610a3 in AbortServer () at ../../src/xserver/os/log.c:886
#4 0x000055b3fe261e76 in FatalError (f=f@entry=0x55b3fe2e9410 "Caught signal %d (%s). Server aborting\n") at ../../src/xserver/os/log.c:1024
#5 0x000055b3fe258f1c in OsSigHandler (unused=<optimized out>, sip=0x7ffcb0750e30, signo=11) at ../../src/xserver/os/osinit.c:156
#6 OsSigHandler (signo=11, sip=0x7ffcb0750e30, unused=<optimized out>) at ../../src/xserver/os/osinit.c:110
#7 <signal handler called>
#8 0x00007f995d697ad3 in __memmove_avx_unaligned_erms () from /usr/lib/libc.so.6
#9 0x000055b3fe2a7ebd in xf86RandR12CrtcSetGamma (pScreen=<optimized out>, randr_crtc=0x55b3ff2ef160) at ../../src/xserver/hw/xfree86/modes/xf86RandR12.c:1369
#10 0x000055b3fe2a6f80 in xf86RandR12CrtcInitGamma (crtc=crtc@entry=0x55b3fed79180, gamma_red=gamma_red@entry=1, gamma_green=gamma_green@entry=1, gamma_blue=gamma_blue@entry=1)
at ../../src/xserver/hw/xfree86/modes/xf86RandR12.c:1423
#11 0x000055b3fe2a9c5b in xf86RandR12InitGamma (pScrn=pScrn@entry=0x55b3febf8ad0, gammaSize=gammaSize@entry=256) at ../../src/xserver/hw/xfree86/modes/xf86RandR12.c:1484
#12 0x000055b3fe2aa2ba in xf86RandR12Init12 (pScreen=0x55b3fed85d00) at ../../src/xserver/hw/xfree86/modes/xf86RandR12.c:2382
#13 xf86RandR12Init (pScreen=pScreen@entry=0x55b3fed85d00) at ../../src/xserver/hw/xfree86/modes/xf86RandR12.c:893
#14 0x000055b3fe29cf8b in xf86CrtcScreenInit (screen=screen@entry=0x55b3fed85d00) at ../../src/xserver/hw/xfree86/modes/xf86Crtc.c:822
#15 0x00007f995db4b3d6 in ScreenInit (pScreen=0x55b3fed85d00, argc=<optimized out>, argv=<optimized out>) at ../../src/xserver/hw/xfree86/drivers/modesetting/driver.c:1896
#16 0x000055b3fe188167 in AddScreen (pfnInit=pfnInit@entry=0x55b3fe274780 <xf86ScreenInit>, argc=argc@entry=13, argv=argv@entry=0x7ffcb0751d88) at ../../src/xserver/dix/dispatch.c:3932
#17 0x000055b3fe2761c5 in InitOutput (pScreenInfo=pScreenInfo@entry=0x55b3fe382800 <screenInfo>, argc=argc@entry=13, argv=argv@entry=0x7ffcb0751d88)
at ../../src/xserver/hw/xfree86/common/xf86Init.c:632
#18 0x000055b3fe18bd9c in dix_main (argc=13, argv=0x7ffcb0751d88, envp=<optimized out>) at ../../src/xserver/dix/main.c:190
#19 0x00007f995d55a152 in __libc_start_main () from /usr/lib/libc.so.6
#20 0x000055b3fe14e84e in _start ()
```xserver-21.1Aaron Plattneraplattner@nvidia.comAaron Plattneraplattner@nvidia.comhttps://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/21Dual-monitor setup broken since commit cfce4b3e: Drop bo/width/height members...2020-09-15T09:23:09ZJohannes HirteDual-monitor setup broken since commit cfce4b3e: Drop bo/width/height members from struct drmmode_scanoutSince commit cfce4b3e6b05b1be14b7ce716dbfb9a15e7e21f4
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Tue Apr 21 18:48:06 2020 +0200
Drop bo/width/height members from struct drmmode_scanout
The pixmap is all we really n...Since commit cfce4b3e6b05b1be14b7ce716dbfb9a15e7e21f4
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Tue Apr 21 18:48:06 2020 +0200
Drop bo/width/height members from struct drmmode_scanout
The pixmap is all we really need.
dual-monitor setup is broken for some configurations. I've an laptop with 1920x1080 native resolution connected via eDP. When adding a second monitor, the screen gets garbled there. The Monitor has a native resolution of 1680x1050 and is connected via HDMI-DVI (monitor is only DVI, laptop has only HDMI). Going back to
commit 680b9a2976f9eb8010c8160c425c2194fb5429d1
Author: Niclas Zeising <zeising@daemonic.se>
Date: Wed Apr 15 10:34:32 2020 +0200
Fix return value check of drmIoctl()
When the drmModeSetCursor2() call was replaced with bare drmIoctl() call in
b344e155, a bug was introduced. With the use of drmModeSetCursor2(),
the return value from drmIoctl() (which calls ioctl()) were mangled, if
they were negative, they were replaced by -errno by a wrapper function
in xf86drMode.c in libdrm. After replacing drmModeSetCursor2() with the
call to drmIoctl(), this mangling no longer happens, and we need to
explicitly check if the call to drmIoctl() fails, which is indicated by
returning -1, and then why it failed, by checking errno.
If the error indicated by errno is EINVAL, then we can't use the
DRM_IOCTL_MODE_CURSOR2 ioctl(), and need to fall back to the
DRM_IOCTL_MODE_CURSOR ioctl().
This bug can manifest itself by an invisible hw cursor on systems where the
DRM_IOCTL_MODE_CURSOR2 is not implemented by the graphics driver.
Signed-off-by: Niclas Zeising <zeising@daemonic.se>
solved this. Attaching a photo from the corrupted screen.
![DSC_0039](/uploads/6fa67edf9819c713e5e416b32fc4e69d/DSC_0039.JPG)20.0Michel DänzerMichel Dänzer