From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mtxclient causes nheko to segfault
Date: Sat, 11 Jun 2022 12:26:43 +0200 [thread overview]
Message-ID: <20220611102643.wiaNfUcoRtgwKSyr5GpPoFf-QYTed2jYJXzEx9ouka8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37442@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Closed issue by RunningDroid on void-packages repository
https://github.com/void-linux/void-packages/issues/37442
Description:
<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
### System
* xuname:
Void 5.15.45_1 x86_64 GenuineIntel uptodate rrmFFFFFFFFFFFFFFFF
* package:
mtxclient-0.7.0_1
nheko-0.9.2_2
### Expected behavior
Not segfaulting when viewing a room in nheko
### Actual behavior
Segfaulting when viewing a room in nheko
### Steps to reproduce the behavior
1. launch nheko
2. try to view a room
Rebuilding mtxclient fixes this, but as near as I can tell the only dependency that's been updated is [openssl](https://github.com/void-linux/void-packages/commit/134c645bd4fd68c6669f917a10a4bd7e6df7fd0e) so I don't know why it fixes it.
Related: Nheko-Reborn/nheko#1083
prev parent reply other threads:[~2022-06-11 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:33 [ISSUE] " RunningDroid
2022-06-08 13:30 ` balejk
2022-06-08 14:48 ` balejk
2022-06-08 21:12 ` deepbluev7
2022-06-08 21:12 ` deepbluev7
2022-06-11 9:44 ` kartikynwa
2022-06-11 10:26 ` Johnnynator [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=20220611102643.wiaNfUcoRtgwKSyr5GpPoFf-QYTed2jYJXzEx9ouka8@z \
--to=johnnynator@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).