Package Details: xorg-xwayland-explicit-sync-git 23.2.4.r387.ga57b44948-2

Git Clone URL: https://aur.archlinux.org/xorg-xwayland-explicit-sync-git.git (read-only, click to copy)
Package Base: xorg-xwayland-explicit-sync-git
Description: Run X clients under Wayland with explicit sync patch
Upstream URL: https://xorg.freedesktop.org
Keywords: nvidia xwayland
Licenses: custom
Groups: xorg
Conflicts: xorg-server-xwayland, xorg-server-xwayland-git, xorg-xwayland
Provides: xorg-server-xwayland, xorg-server-xwayland-git, xorg-xwayland
Submitter: martiuk
Maintainer: martiuk
Last Packager: martiuk
Votes: 20
Popularity: 5.23
First Submitted: 2023-11-25 18:13 (UTC)
Last Updated: 2024-03-30 16:18 (UTC)

Required by (104)

Sources (2)

Pinned Comments

martiuk commented on 2023-12-07 16:15 (UTC) (edited on 2023-12-07 16:28 (UTC) by martiuk)

Since these patches are coming direct from the merge requests, I can't guarantee they'll work, as it is affected by upstream changes from xserver and whether the merge request is up-to-date.

Latest Comments

1 2 3 4 5 6 7 Next › Last »

sr.team commented on 2024-04-19 15:17 (UTC)

Last builded package from chaotic-aur: https://nc.sr.team/s/Q94JsTcczJ2mNS5

xiota commented on 2024-04-18 06:08 (UTC)

PKGBUILD for anyone interested.

hirak99 commented on 2024-04-15 16:50 (UTC)

I see, thanks @Sangeki.

Sangeki commented on 2024-04-15 12:55 (UTC) (edited on 2024-04-15 15:43 (UTC) by Sangeki)

@hirak99 We still need a git build until the next XWayland release next month.

The purpose of this AUR package, XWayland-git + explicit sync MR, is indeed void and ideally we'd switch to regular xorg-xwayland-git but that has not been updated for the recent upstream changes and doesn't even build.

The easiest (incorrect) solution for now is to just remove the patch from this PKGBUILD.

hirak99 commented on 2024-04-15 03:24 (UTC)

The patch has been merged on April 9th into xorg-xwayland-git.

Does this mean that we do not need this anymore?

EarlOfBurl commented on 2024-04-13 10:15 (UTC)

@Sangeki Thank you very much!

Now it does work again.

Sangeki commented on 2024-04-13 07:14 (UTC) (edited on 2024-04-13 13:49 (UTC) by Sangeki)

@EarlOfBurl For a quick and easy solution just edit this PKGBUILD to remove the application of the patch and build/install with makepkg.

Remove or comment out lines 41-44.

The MR has been merged upstream and that's why the patch doesn't apply anymore (it already is) and the build fails. We'll probably be transitioning to regular xorg-xwayland-git when ownership of that AUR package has been sorted. If that happens before the next release of XWayland next month.

EarlOfBurl commented on 2024-04-13 06:51 (UTC) (edited on 2024-04-13 06:51 (UTC) by EarlOfBurl)

I think I messed up. I saw yesterday, that the normal xorg-xwayland package got updated, so I thought "Perhaps explicited sync got merged, just try it and if it not works, fall back to this package". After trying out the official package, the result was as bad as before I applied this patch here. But when I tried to reinstall I couldn't.

An excerpt from the errors and install log:

patching file hw/xwayland/xwayland-glamor-gbm.c Hunk #1 FAILED at 62. Hunk #2 succeeded at 1401 with fuzz 1 (offset 381 lines). Hunk #3 FAILED at 1172. Hunk #4 succeeded at 1637 with fuzz 2 (offset 400 lines). 2 out of 4 hunks FAILED -- saving rejects to file hw/xwayland/xwayland-glamor-gbm.c.rej patching file hw/xwayland/xwayland-glamor.h Hunk #1 FAILED at 57. 1 out of 1 hunk FAILED -- saving rejects to file hw/xwayland/xwayland-glamor.h.rej patching file hw/xwayland/xwayland-present.c Hunk #1 FAILED at 695. 1 out of 1 hunk FAILED -- saving rejects to file hw/xwayland/xwayland-present.c.rej patching file hw/xwayland/xwayland-window-buffers.c Hunk #1 FAILED at 32. Hunk #2 FAILED at 384. 2 out of 2 hunks FAILED -- saving rejects to file hw/xwayland/xwayland-window-buffers.c.rej patching file .gitlab-ci.yml Reversed (or previously applied) patch detected! Skipping patch.

Do I have to wait it out now because I messed up or any chance to get it installed once again?

xuanruiqi commented on 2024-04-09 16:24 (UTC)

It seems that the current maintainer is currently banned, and (though not the reason of the ban) has a infamous history of adopting and/or uploading packages then ignoring all requests.

We'd have to wait for the admins/PUs to orphan the package. But I suppose it will be quick...

1 2 3 4 5 6 7 Next › Last »