Valve's Deadlock not launching on hyprland. Wine dumps core. #10485
Replies: 11 comments 20 replies
-
|
is it running in wayland or x11? if wayland, please attach a WAYLAND_DEBUG=1 log. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue as you, I couldn't play since big shop update but today the game randomly worked. As far as I know there was no patch for the game itself. I use mesa-git, hyprland-git. Besides daily updates for these two (I've checked after every update if it's fixed) I did not change anything with my setup. BUT Today while trying to find out why my Steam download speeds are low (don't ask) I've installed |
Beta Was this translation helpful? Give feedback.
-
|
SDL_VIDEODRIVER=wayland |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that I have this issue as well. The game crashes when running on Hyprland, but it runs fine on KDE. |
Beta Was this translation helpful? Give feedback.
-
|
I found a solution thanks to a comment on protondb, just run the game with since the game only runs with xwayland (crashes when enabling proton wayland support) it could be an issue on hyprland's xwayland implementation since the game runs fine without any tinkering on KDE. |
Beta Was this translation helpful? Give feedback.
-
This worked for me thank you so much life saver :) on omarchy |
Beta Was this translation helpful? Give feedback.
-
|
If everything above doesn't help, make sure SDL_VIDEO_DRIVER and QT_QPA_PLATFORM environment variables in hyprland.conf are commented or removed |
Beta Was this translation helpful? Give feedback.
-
|
I've been struggled with this all day. Here's what ended up working for me. Launch Options: |
Beta Was this translation helpful? Give feedback.
-
|
None of these fixes worked for me on 4070, 580.95.05 and GE_Proton10_21-1 |
Beta Was this translation helpful? Give feedback.
-
|
I thought I was having this issue as well, but it turns out it was an error with wayland, steam, and spaces in the mount point names of hard drives. I'd loaded deadlock onto a hard drive with a space in it, and when i renamed the mount point to remove the spaces, the game launched normally. It wasn't even getting to the point where log files were being generated, because the spaces were interrupting the command when it executes. I'm leaving this advice here for posterity, and those fools such as I who thought they could insert a space into literally every filepath on their system: Don't do that. Do not insert spaces into mount points; it does not go well. I'm embarrassed to have even done this; frankly, I should know better. |
Beta Was this translation helpful? Give feedback.
-
|
Using a clean Omarchy installation 3.2.0 I managed to get deadlock running by checking out the discord messages for gaming. My solution was to add these parameters to launch:
and have set compatibility to Latest Proton. Currently running on Nvidia |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For the past 3/4 days I've been unable to launch Valve's Deadlock. Other games launch fine. Even Dota 2 does.
I tried many things without luck. Today I installed sway and plasma and I realized that they do launch there, so it's something to do with hyprland.
I tried launching the game with the new PROTON_ENABLE_WAYLAND and I tried downgrading hyprland to 0.48.1-5 but there was no difference in behavior.
The bug report in Valve's forum includes all information and has the core dump attached:
https://forums.playdeadlock.com/threads/linux-game-fails-to-launch-wine-dump-in-game-folder-attached.65306/
I can collect any information if needed.
Beta Was this translation helpful? Give feedback.
All reactions