You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently trying out Vanilla OS, and I am evaluating it to be my next primary OS. Sadly though, I experience a problem with applications in the apx containers (including vso). Since every user application that isn't Flatpak is supposed to be installed via apx, this appears to be a severe problem for me.
What went wrong?
When starting an application with gpu hardware acceleration support via apx, it doesn't have access to the GPU. This causes different problematic behavior.
Example / Steps to reproduce
I encountered this problem with 2 (of so far 3 tested) applications: VS Code and Zed. I installed both of them in a subsystem based on the vanilla-os/dev stack (and zed a second time in vso), then exported the applications using apx <subsys> export ...
When launching VS Code, I get a blank Gtk Window, with only the window title being what I would expect. The window body is white, but the mouse cursor changes shape when hovering over different (invisible) elements within the application. If I launch VS Code using the --disable-gpu flag, the window appears as expected, though this is not a favorable solution.
When launching Zed, behavior is different: As Zed highly depends on the GPU, it first up prompts me with a warning, that it couldn't detect dedicated graphics and falls back to LLVMpipe software decoding. In the meantime my PCs fans ramp up to full blast.
Funnily enough though, when running the cur-gpu tool (after cp'ing it into the home dir, so the container can access it), it correctly prints out my GPU.
Setup
I am running VanillaOS 2 Orchid using the vanilla-os/nvidia package. My GPU is an RTX 3070.
For funsies I tried switching to the deprecated vanilla-os/nvidia-proprietary package and there both applications work just fine. But therefore, another Electron app (namely GoXLR Utility) suffered from the problems I had with VS Code before (maybe that might be, because I compiled it from source, and it expected the other drivers maybe? I am too novice on that topic to do an educated guess, tbh).
I hope, this is the correct place to report this issue. If not, please don't hesitate to redirect me to the correct repo.
Cheers.
The text was updated successfully, but these errors were encountered:
Hello there,
currently trying out Vanilla OS, and I am evaluating it to be my next primary OS. Sadly though, I experience a problem with applications in the apx containers (including vso). Since every user application that isn't Flatpak is supposed to be installed via apx, this appears to be a severe problem for me.
What went wrong?
When starting an application with gpu hardware acceleration support via apx, it doesn't have access to the GPU. This causes different problematic behavior.
Example / Steps to reproduce
I encountered this problem with 2 (of so far 3 tested) applications: VS Code and Zed. I installed both of them in a subsystem based on the
vanilla-os/dev
stack (and zed a second time in vso), then exported the applications usingapx <subsys> export ...
--disable-gpu
flag, the window appears as expected, though this is not a favorable solution.Funnily enough though, when running the
cur-gpu
tool (aftercp
'ing it into the home dir, so the container can access it), it correctly prints out my GPU.Setup
I am running VanillaOS 2 Orchid using the
vanilla-os/nvidia
package. My GPU is an RTX 3070.For funsies I tried switching to the deprecated
vanilla-os/nvidia-proprietary
package and there both applications work just fine. But therefore, another Electron app (namely GoXLR Utility) suffered from the problems I had with VS Code before (maybe that might be, because I compiled it from source, and it expected the other drivers maybe? I am too novice on that topic to do an educated guess, tbh).I hope, this is the correct place to report this issue. If not, please don't hesitate to redirect me to the correct repo.
Cheers.
The text was updated successfully, but these errors were encountered: