Github messages for voidlinux
 help / color / mirror / Atom feed
From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Mangohud issues with specific install ?
Date: Sun, 16 Jun 2024 21:02:12 +0200	[thread overview]
Message-ID: <20240616190212.469EA2B5E4@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50846@inbox.vuxu.org>

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

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/issues/50846#issuecomment-2171815757

Comment:
> I just installed `Vulkan-Tools-1.3.231.1_1` just to test this, and:
> 
> `export MANGOHUD=1` `mangohud vkcube-wayland`
> 
> OUTPUT: `Cannot connect to wayland.` `Exiting ...`
> 
> Given that `exec dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY XDG_CURRENT_DESKTOP` is run after launching the `sway` WM, this cannot be pinpointed to a non-exorted $DISPLAY variable of sors.
> 
> Based on limited evidence, I would be leaning upon a bug into `MangoHUD`, which is kinda of a shame, because version `MangoHud-0.7.2_1` fixed most of my problems with `MangoHUD` not working at all.
> 
> Anyone else testing this, remember to check the manpages to understand why `export MANGOHUD=1` needs to be run.
> 
> I will retest later with `MANGOHUD=1` added to `env` at login.

thanks for your analysis, i agree with you.
as a consequence, i'll close this thread as "wont fix" since it's not a voidlinux bug.
The issue in the mangohud project is linked above.
Take care.

  parent reply	other threads:[~2024-06-16 19:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16  8:52 [ISSUE] " SpidFightFR
2024-06-16 18:32 ` TeusLollo
2024-06-16 19:02 ` [ISSUE] [CLOSED] " SpidFightFR
2024-06-16 19:02 ` SpidFightFR [this message]
2024-06-16 20:45 ` TeusLollo
2024-06-16 20:45 ` 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=20240616190212.469EA2B5E4@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).