Finally made the switch, and I'm now using PopOS. I have one major issue I've yet to solve though. I have a 3840x1080 monitor, which is wider than a lot of games natively support. On Windows I had an app called flawless widescreen that could enable full ultra wide aspect ratio for a lot of different games. Is there something similar for Linux? Particularly for Elden Ring and the FF VII remakes

submitted by /u/Dbeebe25
[link] [comments]

submitted by /u/Spectechdon
[link] [comments]

Everytime I want to play fortnite on the faugus launcher I always get this network error code that won't even let me into the game. Here's the error code:HTTP Response Code 200,Curl Code:0 and above it it just says network error how do I make it stop I wanna play fortnite!

submitted by /u/lynxgaming2015
[link] [comments]

any workaround to fix this issue? run with Proton-GE 10.26

submitted by /u/DavidAstonish
[link] [comments]

Hi everyone.

I have been having constant crashes with bazzite, I thought it was a Ubisoft launcher (though this issue started happening after I played some Ubisoft games) problem at first, but now my other games crash my pc too after playing for a couple of minutes. I don't get what has happened.

A year ago, when I installed it fresh, everything was working fine and I didn't have any problems at all. All my games worked perfectly fine. The issue isn't proton, as these games work no problem on steamdeck. It's not my hardware, as I noticed other users have the same problem on newer hardware like the ROG ALLY as well. But the crashes for me have been so frequent that both my bluetooth and wifi have stopped working.

Here's the things I already tried:

• increasing swap from 4gb to 8gb
• checking/stress testing if RAM is corrupted with memtest, it isn't
• numerous fresh installs of games, different proton versions and updating bazzite
• turning off background caching of games
• updated my bios
• reset my bios
• reseated all my hardware

These are my specs:

• Aorus X570 motherboard
• AMD Ryzen 5 1600 CPU
• 16 gb DDR4
• AMD RX580 8gb GDDR5
• 512 nvme ssd main drive
• 1tb 2.5" ssd secondary drive

I have noticed this always happens after either loading vulkan shaders, or when it runs install scripts. SO my questions are: What's the best course of action? Should I do a fresh install? Different OS maybe? Or just wait and buy the Steam Machine? How can I post a report when the wifi + bluetooth don't work?

submitted by /u/basnband
[link] [comments]

When I play certain games in fullscreen the taskbar is still visible at the bottom of the screen. I can resolve this by setting the panel to auto-hide but I don't like this option and don't want to have to keep switching it back and forth when not gaming. I've tried multiple different Proton versions but it makes no difference.

submitted by /u/TeePegg
[link] [comments]

I’m well aware that Steam Input creates a virtual controller and hides my physical device from the game.

When I disable Steam Input, the game does recognize my joystick, but it does not work correctly, most likely because it is a generic controller (trigger axes are inverted, L2 is switched with R3 and so).

However, when Steam Input is enabled, the game fails to detect any controller at all. My assumption is that the game does not properly handle the Steam virtual gamepad / XInput device exposed by Steam Input.

What I’m trying to achieve is:

• Use Steam Input to remap and normalize my controller
• While still having the game properly recognize the controller as a valid gamepad

System details:

• OS: Pop!_OS 24.04 LTS x86_64
• Controller: Generic Sony-compatible wired controller
• Steam installation: system package (not Flatpak)
• Without Steam Input: controller detected, partially broken
• With Steam Input: controller not detected

Has anyone encountered a similar issue or found a way to force Steam Input to expose a controller type (XInput vs DirectInput) that this kind of game can properly recognize?

Any guidance would be appreciated.

submitted by /u/StarChanne1
[link] [comments]

My reTHAWed has been working perfectly so far. I'm running it through Proton 9.0-4 and the game has been running really well, but for some reason this one specific mission causes a crash. Every time I finish the mission, the game closes and shows this error box. I recorded a video showing the mission and the crash happening.
This is the error I'm getting

submitted by /u/engiebombado
[link] [comments]

When i try to launch NFS UNBOUND the EA App launches and says there was an error on our end try again later. That happened in the past too and EA servers are up so i don't think it's an error on their end. I fixed it in the past but i don't remember what i did.

submitted by /u/super2061
[link] [comments]

submitted by /u/MarchApart105
[link] [comments]

Hello,

I am using Ubuntu 24.04.3 LTS. My graphic card is a Radeon RX6800. I have installed drivers found [here](https://www.amd.com/en/support/download/linux-drivers.html#linux-for-radeon) with the following command :

sudo apt update wget https://repo.radeon.com/amdgpu-install/7.1.1/ubuntu/noble/amdgpu-install_7.1.1.70101-1_all.deb sudo apt install ./amdgpu-install_7.1.1.70101-1_all.deb sudo amdgpu-install -y --usecase=graphics,rocm sudo usermod -a -G render,video $LOGNAME

I can launch games from Steam without any problem. But when I launch my games from my epic library using Heroic Launcher, it doesn't work. I have the following errors in the logs :

libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/000:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/001:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/002:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/003:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/004:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/005:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/006:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/007:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/008:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/009:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/010:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/011:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/012:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/013:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/014:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/015:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/016:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/017:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/018:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/019:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/020:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/021:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/022:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/023:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/024:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/025:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/026:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/027:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/028:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/029:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/030:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/031:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/032:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/033:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/034:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/035:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/036:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/037:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/038:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/039:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/040:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/041:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/042:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/043:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/044:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/045:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/046:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/047:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/048:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/049:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/050:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/051:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/052:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/053:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/054:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/055:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/056:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/057:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/058:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/059:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/060:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/061:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/062:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/063:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/064:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/065:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/066:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/067:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/068:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/069:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/070:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/071:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/072:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/073:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/074:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/075:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/076:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/077:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/078:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/079:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/080:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/081:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/082:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/083:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/084:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/085:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/086:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/087:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/088:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/089:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/090:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/091:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/092:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/093:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/094:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/095:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/096:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/097:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/098:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/099:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/100:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/101:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/102:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/dri) libGL error: failed to load driver: radeonsi libGL error: MESA-LOADER: failed to open swrast: /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/000:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/001:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/002:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/003:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/004:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/005:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/006:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/007:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/008:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/009:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/010:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/011:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/012:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/013:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/014:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/015:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/016:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/017:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/018:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/019:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/020:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/021:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/022:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/023:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/024:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/025:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/026:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/027:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/028:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/029:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/030:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/031:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/032:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/033:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/034:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/035:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/036:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/037:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/038:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/039:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/040:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/041:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/042:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/043:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/044:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/045:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/046:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/047:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/048:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/049:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/050:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/051:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/052:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/053:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/054:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/055:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/056:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/057:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/058:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/059:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/060:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/061:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/062:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/063:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/064:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/065:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/066:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/067:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/068:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/069:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/070:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/071:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/072:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/073:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/074:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/075:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/076:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/077:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/078:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/079:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/080:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/081:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/082:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/083:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/084:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/085:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/086:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/087:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/088:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/089:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/090:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/091:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/092:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/093:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/094:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/095:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/096:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/097:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/098:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/099:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/100:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/101:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/dri/102:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/dri) libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext

I have done some research, but I haven't managed to resolve the issue.

Does anyone have any ideas?

Thanks

submitted by /u/Sylck
[link] [comments]

My microphone isn't picked up correctly in voice chat games (for me it's R.E.P.O), however it works well outside of voice chat (PAVU Control, Discord...). In the audio settings I get listed 2 input options but neither of them work. The first one, "PulseAudio Input", just freezes my game and after a while the audio gets stuck in the middle of the test audio bar (or whatever it's called) without moving even if I talk. The second one, "Monitor of Family 17h/19h HD Audio Controller Analog Stereo", DOES pick up sound but not from my mic; of course it picks up audio from the game. I'm super confused and would love to hear everyone's opinions.

P.S.

I'll list out my hardware/software for more context:

I'm using an external mic - HyperX Quadcast

For my output I use a headset, but with the mic turned off

Maybe it's not really necessary, but I got Steam from Flathub

submitted by /u/Over_Transition_6418
[link] [comments]

Got my Thinkpad X1 2-in-1 today with Core Ultra 7 258v and Arc 140v iGPU. First, I'm astonished at how powerful this is for not putting out more than medium heat. It runs my entire game library just as good as my 2010 Mac Pro w/RX 580, which is all I wanted in life.

That said...

I have three games that exhibit really odd behavior. Star Wars Jedi Fallen Order, Star Wars Squadrons, and Star Wars Battlefront 2 (2017). They run like crap most of the time, like 20fps, but will magically clear up to a perfect 60fps for a few seconds here and there.

I had a similar problem back in the day with my Mac Pro where it wasn't handling VRAM correctly and the FPS would drop badly once the VRAM filled up, and minimizing/maximizing the game could sometimes fix it. At some point in the last few months, an update somewhere completely resolved the problem.

This behaves similarly, but backward, which leads me to suspect a driver issue again.

And it's just those games too. I use a game called Overload as my benchmark, and if my gaming rig can run that at max graphics, it can run anything else I want. And Overload plays butter smooth on the Arc 140v at 1080p.

Input/diagnostic tips are welcome.

SECONDARY QUESTION: Where can I report this to the Intel Arc iGPU driver maintainers?

submitted by /u/DarthZiplock
[link] [comments]

Steam all in on wayland 2026

submitted by /u/fyzeera
[link] [comments]

Hi everyone,

I’m running into a frustrating issue with World of Warcraft on Linux, specifically involving the mouse cursor disappearing after a few seconds in-game. I wanted to share my setup and what I’ve already tried, and ask for guidance on whether native Wayland or XWayland is currently the better choice for WoW.

System / Environment

• Distro: Ubuntu 24.04.3 LTS
• Desktop: GNOME on Wayland
• GPU: NVIDIA (latest proprietary drivers, 580 series)
• Launcher: Steam (Snap) → Battle.net → WoW
• Compatibility: Proton Experimental and GE-Proton 10-26
• Display: Multi-monitor, mixed refresh rates
• Input: Mouse cursor disappears visually, but input still works

The Problem

• WoW launches normally
• After a few seconds in-game with right-clicking to re-position my character(s) (or after alt-tab / focus changes), the mouse cursor becomes invisible
• Mouse clicks still register, but the cursor itself is gone
• The issue can persist until WoW and sometimes Battle.net are fully closed

This happens only in WoW, not system-wide.

Things I’ve Already Tried

• Enabling “Use Software Cursor” in WoW
• Running WoW in Windowed (Fullscreen) and Fullscreen modes
• Switching between Proton Experimental and GE-Proton 10-26
• Fully restarting WoW and Battle.net between tests

I’ve also experimented with launch options in Steam:

SDL_VIDEODRIVER=x11 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

The aforementioned launch option DID NOT work.

Question for the community

1. For WoW on NVIDIA, is it currently recommended to:
   • Stay on XWayland (e.g. SDL_VIDEODRIVER=x11), or
   • Try native Wayland via PROTON_ENABLE_WAYLAND=1?
2. Has anyone had reliable success with WoW on native Wayland + NVIDIA, or is XWayland still the practical choice?
3. Are there any additional cursor-specific fixes (Wine/Proton/Mutter/NVIDIA) that I may have missed?

I’m not opposed to workarounds, but I’m trying to avoid constantly restarting the game or juggling desktop sessions just to keep the cursor visible. Any guidance from others running WoW on Linux especially on NVIDIA + Wayland would be greatly appreciated.

Thanks in advance!

submitted by /u/CompSciGeekMe
[link] [comments]

Specs - GTX 1650 4GB - R5 5600X - 16GB

Proton version: 10.0-3

The first time I ran the game I was getting ~30 fps at 1080p low settings but now every time I try to load the game, it runs at ~10 fps or crashes before loading with the following message:

Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting...

I checked and neither my ram nor my vram maxxed out before crashing. I saw some YT benchmark videos with similar specs and it ran fine with the same settings.

submitted by /u/epspATAopDbliJ4alh
[link] [comments]

So i saw that steam offers some kind of proton version for Easy Anti-Cheat Would it be possible to use something like heroic game launcher to direct fortnite through steam to get the anti cheat proton working?

(Im not a professional with linux so i have no clue how proton or anything works)

Also does epic games dislike linux or why haven't they ported the epic games launcher to linux yet?

submitted by /u/LOL7430
[link] [comments]

Hi. I played Marvel Rivals on Linux Mint like a month ago and it ran flawlessly, but I played it again today after the most recent game update and every minute or so I get 5 fps drops: what I mean by that is that it's running at 170-200 fps, and suddenly the game stops one time, then goes to normal, then stops again, and so on, 5 times in a span 3 seconds. I haven´t actually measured it, but it is extremely consistent. I'm using Proton Experimental, which is what worked for me before.

My PC specs:

Ryzen 5 5600
RX 6800 16GB
DDR4 2 x 16 GB 3600Mhz
1TB SSD

I have applied the following fix already, but it didn´t work: https://www.reddit.com/r/linux_gaming/comments/1iutojb/comment/me2dwa1/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

submitted by /u/Mat0m
[link] [comments]

My current pc has the following tech specs:

• CPU - i5-7400, 4 cores, 4 threads (I think), 3.00 GHz
• GPU - GTX 1050Ti
• RAM - 32 GB DDR4 2400MHz
• Storage - 2 TB SATA HDD

Given these tech specs, I have been seriously considering migrating to Linux, but am a little apprehensive, thus this post. I am wanting to play roms from several different consoles. Which emulation front end comes the most recommended? I know of Retroarch, which I am not too fond of because, to me, it seems like once you install it, you're on your own, but if I have to go with it I will. I'm just wanting a few more options besides Retroarch. Thanks in advance for all your help.

submitted by /u/SamGamjee71
[link] [comments]

From researching, on Steam, you need a program called optiscaler and you put this ~/fgmod/fgmod %command% at launch options to use optiscaler with steam.

But I couldn't find how to use optiscaler with Heroic. I tried asking LLMs like chatgpt but they didn't help me much.

submitted by /u/IhateReddit9697
[link] [comments]