From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: wine: add xshm build option
Date: Sat, 12 Feb 2022 10:54:18 +0100 [thread overview]
Message-ID: <20220212095418.z2auET5asKCR-Py3QftsZhOhhEnEZpcQWaYqFU8JbbQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35525@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
There's a merged pull request on the void-packages repository
wine: add xshm build option
https://github.com/void-linux/void-packages/pull/35525
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
This PR adds the `xshm` build option to control support for the X Shared Memory Extension (Xshm).
The reason for this change is that I run Wine in an LXD container that doesn't have access to the hosts shared memory (`/dev/shm`). Wine will print the error message
```
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 130 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Value in failed request: 0xb40
Serial number of failed request: 535
Current serial number in output stream: 539
```
which results in corrupted graphics, making Wine applications unusable.
To work around this issue I disabled the Xshm extension on the host, but this can result in performance issues. The `xshm` build option allows me to disable Xshm support in Wine, while having it enabled for all other applications.
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-02-12 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 8:11 [PR PATCH] " amak79
2022-02-12 9:54 ` Hoshpak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220212095418.z2auET5asKCR-Py3QftsZhOhhEnEZpcQWaYqFU8JbbQ@z \
--to=hoshpak@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).