From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Mesa 24.3.1 Update Causing Segmentation Faults On Several-Vendors GPU Architectures
Date: Wed, 11 Dec 2024 21:39:32 +0100 [thread overview]
Message-ID: <20241211203932.E1D7C31526@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53434@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
New comment by SpidFightFR on void-packages repository
https://github.com/void-linux/void-packages/issues/53434#issuecomment-2537095387
Comment:
@TeusLollo Hey, thanks for your message, it truly means a lot.
Although, I'm not officially a maintainer for mesa, i do try my best to keep it updated within void repos, as much as possible. Because it means a lot in my personal usage.
I'll keep an eye out for the next minor release of mesa's 24.3 branch.
In the meantime, there should be one or so new releases into 24.2 branch, so i'll make sure to take these into account.
next prev parent reply other threads:[~2024-12-11 20:39 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 18:25 [ISSUE] Removal of -Ddri3=enabled from Mesa 24.3.1 Update May Be Causing Segmentation Faults In Some Applications TeusLollo
2024-12-09 18:30 ` classabbyamp
2024-12-09 18:32 ` classabbyamp
2024-12-09 18:34 ` SpidFightFR
2024-12-09 18:34 ` TeusLollo
2024-12-09 18:35 ` classabbyamp
2024-12-09 18:37 ` TeusLollo
2024-12-09 18:38 ` SpidFightFR
2024-12-09 18:38 ` TeusLollo
2024-12-09 18:39 ` SpidFightFR
2024-12-09 18:39 ` TeusLollo
2024-12-09 18:40 ` TeusLollo
2024-12-09 18:41 ` SpidFightFR
2024-12-09 18:42 ` SpidFightFR
2024-12-09 18:57 ` TeusLollo
2024-12-09 18:58 ` TeusLollo
2024-12-09 18:59 ` TeusLollo
2024-12-09 19:09 ` EnumuratedDev
2024-12-09 19:19 ` TeusLollo
2024-12-09 19:58 ` SpidFightFR
2024-12-09 21:01 ` TeusLollo
2024-12-10 5:56 ` Mesa 24.3.1 Update May Be Causing Segmentation Faults In Some Applications On AMD Polaris-based GPUs sofijacom
2024-12-10 8:29 ` biopsin
2024-12-10 8:54 ` sofijacom
2024-12-10 10:48 ` risusinf
2024-12-10 10:54 ` SpidFightFR
2024-12-10 12:49 ` classabbyamp
2024-12-10 12:57 ` naneros
2024-12-10 13:49 ` SpidFightFR
2024-12-10 15:43 ` TeusLollo
2024-12-10 15:44 ` TeusLollo
2024-12-10 17:20 ` Mesa 24.3.1 Update Causing Segmentation Faults On Several-Vendors GPU Architectures TeusLollo
2024-12-10 17:28 ` TeusLollo
2024-12-10 17:30 ` TeusLollo
2024-12-10 18:00 ` biopsin
2024-12-11 1:00 ` zlice
2024-12-11 10:18 ` hvraven
2024-12-11 20:18 ` TeusLollo
2024-12-11 20:21 ` TeusLollo
2024-12-11 20:39 ` SpidFightFR [this message]
2024-12-23 21:30 ` classabbyamp
2024-12-27 13:33 ` narodnik
2024-12-27 20:04 ` TeusLollo
2024-12-27 20:06 ` TeusLollo
2024-12-28 13:49 ` narodnik
2024-12-28 13:55 ` classabbyamp
2024-12-28 14:27 ` TeusLollo
2024-12-28 14:28 ` TeusLollo
2024-12-28 19:50 ` narodnik
2024-12-28 19:50 ` narodnik
2024-12-28 20:35 ` narodnik
2024-12-29 1:24 ` TeusLollo
2024-12-29 1:24 ` TeusLollo
2024-12-29 1:25 ` TeusLollo
2024-12-29 1:26 ` TeusLollo
2024-12-29 1:26 ` TeusLollo
2024-12-29 1:29 ` TeusLollo
2024-12-29 1:30 ` TeusLollo
2024-12-29 9:21 ` narodnik
2024-12-29 9:32 ` narodnik
2024-12-29 11:57 ` narodnik
2024-12-29 14:14 ` TeusLollo
2024-12-29 19:08 ` narodnik
2024-12-29 20:50 ` narodnik
2024-12-30 10:08 ` narodnik
2024-12-30 10:18 ` narodnik
2024-12-30 10:42 ` narodnik
2025-01-01 14:42 ` narodnik
2025-01-27 16:04 ` zlice
2025-01-27 20:58 ` TeusLollo
2025-01-27 21:14 ` zlice
2025-01-27 21:15 ` zlice
2025-01-27 21:30 ` hvraven
2025-02-02 1:01 ` TeusLollo
2025-02-03 10:03 ` hvraven
2025-02-09 20:47 ` rationalize-zz
2025-02-10 14:34 ` TeusLollo
2025-02-10 14:36 ` SpidFightFR
2025-02-18 20:20 ` TeusLollo
2025-02-18 20:20 ` TeusLollo
2025-02-23 14:53 ` [ISSUE] [CLOSED] " TeusLollo
2025-02-23 14:53 ` TeusLollo
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=20241211203932.E1D7C31526@inbox.vuxu.org \
--to=spidfightfr@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).