From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-lz4 segaults when running tests on x86_64-musl
Date: Wed, 07 Apr 2021 01:11:00 +0200 [thread overview]
Message-ID: <20210406231100.OqToCEIfADQChxCzTxU4ITMKVrcS5CQkDmXXr_vUQ68@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30060@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/30060#issuecomment-814491603
Comment:
**Note**: this segfault also affects `xpra` when trying to connect to a remote session with, *e.g.*,
```
xpra start ssh:remote-hostname --exit-with-children --start-child xterm
```
because `xpra` tries to use `lz4` compression. I believe this can be worked around in `xpra` by disabling `lz4` compression using the `--compressors=lzo,zlib` argument or the `compressors` configuration option.
next prev parent reply other threads:[~2021-04-06 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 22:47 [ISSUE] " ahesford
2021-04-06 23:11 ` ahesford [this message]
2022-05-17 2:14 ` python3-lz4 segfaults " github-actions
2022-06-01 2:14 ` [ISSUE] [CLOSED] " github-actions
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=20210406231100.OqToCEIfADQChxCzTxU4ITMKVrcS5CQkDmXXr_vUQ68@z \
--to=ahesford@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).