From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: workrave - 1.10.52_1 - 'workrave' terminated by signal SIGSEGV (Address boundary error)
Date: Sun, 23 Feb 2025 13:10:50 +0100 [thread overview]
Message-ID: <20250223121050.D36CC2DDBD@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54091@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/54091#issuecomment-2676826845
Comment:
This isn't really a bug, but is instead a lack of Wayland support. We don't permit patches that backport feature additions. There's nothing to do but wait for a proper upstream release.
prev parent reply other threads:[~2025-02-23 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:44 [ISSUE] " RandallFlagg
2025-01-23 23:25 ` classabbyamp
2025-01-25 1:17 ` rationalize-zz
2025-01-26 14:08 ` RandallFlagg
2025-01-26 14:13 ` classabbyamp
2025-02-23 12:10 ` [ISSUE] [CLOSED] " ahesford
2025-02-23 12:10 ` ahesford [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=20250223121050.D36CC2DDBD@inbox.vuxu.org \
--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).