[ISSUE] Mangohud issues with specific install ?

[ISSUE] Mangohud issues with specific install ?

[SpidFightFR]

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

New issue by SpidFightFR on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 6.9.4_1 x86_64 AuthenticAMD notuptodate rrmFFFFFFFFF

### Package(s) Affected

MangoHud-0.7.2_1

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

I also created this issue in upstream just in case: https://github.com/flightlessmango/MangoHud/issues/1354

### Expected behaviour

1. Run `mangohud vkcube-wayland`
2. [should work]

### Actual behaviour

1. Run `mangohud vkcube-wayland`
2.
```
Cannot connect to wayland.
Exiting ...
```

### Steps to reproduce

1. Update MangoHud from `MangoHud-0.7.0_1` to `MangoHud-0.7.2_1`.
2. Something is probably wrong with my void install cuz it only happens on my main pc. Not on my laptop.

Re: Mangohud issues with specific install ?

[TeusLollo]

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

New comment by TeusLollo on void-packages repository

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

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. 

Re: [ISSUE] [CLOSED] Mangohud issues with specific install ?

[SpidFightFR]

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

Closed issue by SpidFightFR on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 6.9.4_1 x86_64 AuthenticAMD notuptodate rrmFFFFFFFFF

### Package(s) Affected

MangoHud-0.7.2_1

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

I also created this issue in upstream just in case: https://github.com/flightlessmango/MangoHud/issues/1354

### Expected behaviour

1. Run `mangohud vkcube-wayland`
2. [should work]

### Actual behaviour

1. Run `mangohud vkcube-wayland`
2.
```
Cannot connect to wayland.
Exiting ...
```

### Steps to reproduce

1. Update MangoHud from `MangoHud-0.7.0_1` to `MangoHud-0.7.2_1`.
2. Something is probably wrong with my void install cuz it only happens on my main pc. Not on my laptop.

Re: Mangohud issues with specific install ?

[SpidFightFR]

[-- 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.

Re: Mangohud issues with specific install ?

[TeusLollo]

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

New comment by TeusLollo on void-packages repository

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

Comment:
> I will retest later with `MANGOHUD=1` added to `env` at login.

Nope, having `MANGOHUD=1` added as environment variable at WM login made no difference whatsoever. 

Re: Mangohud issues with specific install ?

[TeusLollo]

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

New comment by TeusLollo on void-packages repository

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

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-exported $DISPLAY variable of sorts. 

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. 

EDIT: Spelling