linux

[pseudo magnet]

done!

[candid wharf]

hey guys. i m looking for help: valheim gaming on linux. i have issues with the mouse. click and drag not working so i cannot use the bow. any suggestions?

it worked before the last update

[lapis aurora]

You could easily re-verify your game files in your Steam Library.

Is the mouse acting up in any other apps on your PC? Are you experiencing any other unusual things in the game? Are you playin solo game or on a server?

[candid wharf]

Thank you for your answer! I found a fix: I changed the proton version from 9.04 to the latest. now it works perfect

[limpid prism]

Valheim supports linux, you do not need to be using proton.

[feral haven]

@lapis aurora CachyOS (Arch) and I'm using the Linux version of r2modman and Valheim.

[limpid prism]

Did r2mm prompt you to change the launch options in steam for valheim? It should have.

[valid parcel]

Does playfab/crossplay work with oracle cloud servers?

Im getting a repeating message;

04/26/2026 02:05:49: Server 'MyServer' begin PlayFab create and join network for server
04/26/2026 02:06:18: PlayFab reconnect server 'MyServer'
04/26/2026 02:06:18: Server 'MyServer' begin PlayFab create and join network for server
04/26/2026 02:06:49: PlayFab reconnect server 'MyServer'
04/26/2026 02:06:49: Server 'MyServer' begin PlayFab create and join network for server

[dreamy berry]

It should, yes, though it can be a bit trickier if you're using an x86_64 emulator on an arm64 instance. If not using an emulator, what Linux distribution have you deployed?

[valid parcel]

Fixed it with Arrowmasters advice by installing libpulse-dev libatomic1 libc6. #dedicated-server message

[dreamy berry]

I wouldn't recommend libpulse-dev unless you are compiling source against libpulse. libc6 should also come with your distribution and I definitely don't recommend a manual install. You should only need:
libatomic1, libpulse0, and libpulse-mainloop-glib0 (they may be named differently in your distribution hence the question).

[limpid prism]

And I agree with Justin, I think I was only copying whatever was on the wiki at the time. The real answer is more complicated and depends on your distro.

I think libpulse-dev is listed because on most debian/ubuntu based distros it depends on libpulse0 and libpulse-mainloop-glib0 but the names might be different. libpulse-dev was probably a compromise of consistent name and common package that depends on the needed packages

[tough anchor]

Just so you know, my "world building" problems are much improved when running it this way on my system: "nice -n 20 taskset -c 4-7 %command% -console", from steam. So now I'm happy. 🙂

[lucid vigil]

20? does your audio or anyhting else on the system lag? also I assume -c 4-7 implies half of your cores with hyperthreading disabled...right?

[tough anchor]

I'm not sure why that works, but it seems to improve it the most. The audio (pipewire) runs with real-time priority, so it doesn't lag. My CPU model has 8 real cores, no hyper-threading.

[lucid vigil]

yeh, i ask becasue running anything realtime usually makes something else of a moderately high priority lag. But idk about pipewire; im still in pulseaudio stoneage.
So you ae using half of your cores. But is hyperthreading disabled in bios? Or can you even disable it successfully in linux? I never could... or is that an only-Intel uses hyperthreading problem?

[lucid vigil]

Also, at a glance it looks more like the realtime nice is being applied to taskset and not to the game.
Doing a quick search it appears schedtool is the utility to use; so you can set nice and affinity in one pass.

just some arbitrary load so i could see how it worked
glxgears & schedtool -n10 -a1 -e ffmpeg -f x11grab -video_size 512x512 -i :0.0+0,0 -c:v libx264rgb -crf 0 -preset veryslow -f matroska - | mpv --fullscreen --volume=0 -

it does work, which is interesting fo rme becasue whatever i was doing the last time i tried this wasnt able to hold affinity to any specified core for more than a fraction of a second.. i had to disable hyperthreading in bios to do that..iirc...yet this works. I guess i need to test it on valheim now

[buoyant hazel]

anyone having issue inside the swamp? for some reason my gpu goes to 0% usage when i go inside the swamp, could it be mods?

[tough anchor]

I have never seen that. Could be mods.

[buoyant hazel]

i just asked gpt x) its indicating towards "UseEquipmentInWater" mod with the arguments it brings up it sounds plausible, i will try to remove that

its like a really weird bug, the second im nearing the swamp the gpu usage drop to 0%
how can I turn see the logs or where?
under windows i always had a console opening up on the side...

[tough anchor]

The Player.log is in $HOME/.config/unity3d/IronGate/Valheim

[buoyant hazel]

Its fixed!! gpt said xD:::
The #1 Culprit: "UseEquipmentInWater"
If you have the mod UseEquipmentInWater (specifically the one by LHV-IT) installed, this is almost certainly your problem.
The Swamp is roughly 80% water and is filled with Leeches and Draugr. When enemies enter the water in this biome, this specific mod attempts to process their states or calculate equipment logic, fails, and throws an endless loop of errors.
The Fix: Uninstall UseEquipmentInWater. If you still want that functionality, replace it with HS_EquipInWater (by HS/Horem), which achieves the same thing without triggering the Swamp death-loop.

[hearty patrol]

So hey everyone, I'm having a broad set of issues that I've narrowed down I think to the steam launcher.
I can't do 3 relatively important things in Valheim:

1. I can't strafe and hold down block at the same time
2. I can't pull through the map by dragging
3. I can't use my bow. Any draw immediately fires.
   plus a handful of other smaller issues pertaining to the mouse controls...

I'm in the latest public test, I'm using the latest Proton. This has been a problem periodically throughout my experience while playing on Ubuntu but usually it's resolved by switching to a different compatibility through steam. I have been having similar control glitches while using steam though, and half the time just closing the client while the game is still running (technically I guess minimizing it) usually resolved the issue in the past, but this hasn't worked either.

[lucid vigil]

switching to a different compatibility
use the native linux client

[hearty patrol]

yeah that doesn't work. It also has the same bugs

[lucid vigil]

sounds more like hardware failure, some kind of driver/software conflict, or a distro being too edgy for it's own good.

[lapis aurora]

My experience with the Steam compatibility layers has been erratic. On both Windows and various Linux distros I have to just go through them until one works.

And it's usually not the one of them that I expected to work nor is it consistent. And all those trials and errors put a lot of unused garbage Steam compatibility crap on my disks, too. It's kind of an annoying process but eventually it does work.

[limpid prism]

trying multiple versions of proton tends to cause more trouble than it fixes most of the time. trying a version older than 10 with a game thats been updated anytime in the past 2 years is just the wrong move. the only versions of proton to try are 10, experimental, hotfix, or different versions of a recent custom build like proton-ge.

but none of that matters for a game like valheim that has a native version because nobody will be patching proton to specifically fix issues for valheim because it has a native version.

If you think steam is causing issues with the native version of the game you can try disabling the overlay and changing the launch arguments to LD_PRELOAD= %command% to try and prevent steam from injecting any of its libraries. I have never tried this with valheim but it would prevent the overlay, screen recording, and steam input from functioning if it works as it does with some other games.

[hearty patrol]

How? I'm on Ubuntu. I just keep the drivers updated, and they're pushed every 3 days or so.

Yeah, just did a fresh reinstall of the game, running on public test with experimental and the overlay disabled the game crashes before it boots up

running default compatibility prompts me to update, even though default is experimental. And now it runs. I'll see if the bug is still present

It works. The overlay was the problem

Thanks @limpid prism . The game is still running weirdly hot, but that's probably a sign I should clean my PC out more than anything.

[limpid prism]

did you use the overlay toggle in steam or LD_PRELOAD= %command%? if you did the latter it would have also disabled all of steam input which is more likely the cause for input issues.

[hearty patrol]

Na, just disabled the overlay first to try it. **by which I mean the overlay toggle, sorry

I had done a reinstall of the game before and the bug persisted. I'll see if it pops up again

[limpid prism]

huh, thats interesting. well something wacky is probably going on with your steam

[hearty patrol]

Probably. I initially started setting up my Ubuntu manually from a friend's suggestion to get used to Linux, but then once the App Center started running updates I defaulted to that. So it's likely missing something that I didn't properly install.

[lucid vigil]

@hearty patrol Maybe check if you have a bluetooth tranceiver active, and disable it to test.
I assume you are using wired keyboard and mouse?

[hearty patrol]

Yes. I do not have Bluetooth anything in my house lol

I don't know what Bluetooth would have to deal with it. Disabling the overlay worked

[lucid vigil]

you are not very specific with your info, as evidenced by ignoring my question, so i'm going through possibilities

related symptom (arrows) #830545339890532402 message