Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Vulkan glitching out on some applications since a recent Void-Linux update ?
Date: Tue, 28 May 2024 20:50:39 +0200	[thread overview]
Message-ID: <20240528185039.B1D6928872@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50545@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

Closed issue by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/50545

Description:
### Is this a new report?

Yes

### System Info

Void 6.9.1_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFF

### Package(s) Affected

vulkan-loader-1.3.261.1_2 mesa-vulkan-radeon-24.0.7_1 (?)

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

I didn't find such a report. Devs and I agree on the fact that it doesn't come from the mod, since i tested this version already, before updating my system, and everything worked.
It's only recently that this issue happened, i took a wild blind guess at vulkan-loader but i legit don't know.

### Expected behaviour

The test were based on the latest release of the Vulkanmod for minecraft (version 0.4.2 - stable, which i tested in the past, without any issues).
It should work normally.

### Actual behaviour

The screen glitches out with the app running in fullscreen.
[video sample](https://pub-933bfc621bd04d93ab1b82361d7baa1a.r2.dev/vkmod%20bug.mp4)

### Steps to reproduce

1. Update Void with the latest packages to this day
2. Run Minecraft with vulkanmod

  parent reply	other threads:[~2024-05-28 18:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 19:05 [ISSUE] [Help-Wanted] " SpidFightFR
2024-05-27 19:07 ` SpidFightFR
2024-05-27 19:07 ` SpidFightFR
2024-05-28  2:06 ` Luciogi
2024-05-28  4:41 ` SpidFightFR
2024-05-28  4:43 ` Luciogi
2024-05-28  5:25 ` Luciogi
2024-05-28  5:38 ` SpidFightFR
2024-05-28  5:38 ` SpidFightFR
2024-05-28  7:32 ` Luciogi
2024-05-28  7:49 ` Luciogi
2024-05-28  9:30 ` SpidFightFR
2024-05-28  9:31 ` SpidFightFR
2024-05-28  9:32 ` SpidFightFR
2024-05-28 13:11 ` Luciogi
2024-05-28 17:15 ` SpidFightFR
2024-05-28 17:15 ` SpidFightFR
2024-05-28 17:16 ` Luciogi
2024-05-28 17:57 ` SpidFightFR
2024-05-28 17:58 ` SpidFightFR
2024-05-28 18:04 ` SpidFightFR
2024-05-28 18:10 ` SpidFightFR
2024-05-28 18:37 ` SpidFightFR
2024-05-28 18:50 ` SpidFightFR [this message]
2024-05-28 18:50 ` SpidFightFR
2024-05-28 18:56 ` SpidFightFR
2024-05-28 19:01 ` SpidFightFR
2024-06-01 12:30 ` Dr64h
2024-06-01 12:33 ` Dr64h
2024-06-01 13:40 ` SpidFightFR
2024-06-02 12:09 ` Dr64h
2024-06-02 12:17 ` Dr64h
2024-06-02 17:23 ` SpidFightFR
2024-06-04 18:23 ` [ISSUE] [CLOSED] " SpidFightFR
2024-06-04 18:23 ` SpidFightFR

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=20240528185039.B1D6928872@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).