Can't say I can reproduce the missing/black materials on my RX 570, though performance of the game does seem a bit rough. Long pauses/loading between pausing and unpausing the game. Game seems to want a lot of RAM and running without a swapfile is unadvised if you have only 16GB to work with. Used Proton 7.0-6.

Looks like RADV_DEBUG=nodcc,nohiz seems to be fixing the LOD/Shading issue so it might be another RDNA3 specific LOD issue like with Hi-Fi Rush... Will add it to my report on the mesa side.
Note: This doesn't fix the crashing when sometimes teleporting via fast travel.

Using Proton Experimental

System: Arch (Kernel 6.1.9-arch1-2)
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 6750 XT
DRIVER: Mesa 22.3.4
RAM: 16 GB

Looks and runs really well at Ultra Settings in 1440p+FSR2 Quality. The only issues I encountered are:

1. After around 2 to 3 hours of playing, the game will freeze and crash (memory leak?);
2. If you set the launch options RADV_PERFTEST=rt and VKD3D_CONFIG=dxr11 it freezes the game during the first load screen.

With an RX 6700 I do not have shaders issue. But yes, sometimes with scene loading or fast travel I have an instant crash. Restarting the game allows me to play past that loading screen but it will eventually crash a few scenes later.

Played for a few hours, now the game won't launch at all and I am presented with an error box with a link to the following page: https://support.codefusion.technology/pp_inaa2nm/?e=88500006&l=english which I guess is probably broken DRM or something

I can confirm the crashes on my 1060 6gb, though no shader issues.

Looks to me like a memory leak...

• before it crashes (and the crashes occurred to me only while on the loading screens between scenes, though not every time), the quest scenes get very laggy.
• Starting the game after the crash the same scene gets repeated because the last save was before the scene, but then the frame rate is fine.
• Then it goes through the same loading screen that crashed before and passes it without crashes
• after a few scenes the same thing repeats, starting with the lag/very low framerate on a different scene

I'm having issues where the game will crash during a loading screen on my 6700 XT.

* before it crashes (and the crashes occurred to me only while on the loading screens between scenes, though not every time), the quest scenes get very laggy.

* Starting the game after the crash the same scene gets repeated because the last save was before the scene, but then the frame rate is fine.

* Then it goes through the same loading screen that crashed before and passes it without crashes

Same crash here, Proton Experimental (bleeding-edge) and Proton-GE 49. I get this in stderr when it crashes:

Win64\HogwartsLegacy.exe: ../src-wine/dlls/ntdll/unix/virtual.c:1481: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed.

I can confirm that game crashes a lot during fast travel/loading screens on my both PC. One with RX 5600 XT and second with RX 6600 XT.

For me the game stays on the "Warning" screen indefinitely. And I suddenly discovered that my game runs fine when I did not focus the window at the game. (That means I have the game running in background, and it shows up just fine as I am typing this. Once I switched back, making it full screen, the game freezes again.

Hello.
Could any of you people with the crash issue try something to see if it helps?
In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/sysctl.conf
This change should kick in after a reboot or if you run sudo sysctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on Deck.

Edit: On newer versions of systemd a conf file might need to be created in a different location.
See https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422921442

@Blisto91 thanks for the idea, i am trying it out now, changed it in proc, will keep you updated

I was able to play the game 1 time, but trying to launch it again leads to it crashing. The logs are quite strange... Proton Logs Here: https://filebin.net/96b7nxeu1hld0spc

The game seems to enter some kind of loop where it keeps printing:

01ec:warn:d3d12_pipeline_library_load_pipeline: Pipeline "2B1C3EF2891BAC37" does not exist.

then I think it tries to create a new pipline, then it complains that pipeline doesn't exist until it hits:

eventfd: Too many open files
x11drv: Can't allocate handle for display fd
365.751:0118:0210:warn:seh:OutputDebugStringA "Shutdown handler: cleanup.\n"

Hello. Could any of you people with the crash issue try something to see if it helps? In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/systctl.conf This change should kick in after a reboot or if you run sudo systctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on Deck

I did try this even though I didn't think it would help with my issue and yeah it didn't help.

Any ideas?

@MichaelAllenHardeman I have been told that might be an esync "issue" (maybe not a issue with esync itself per say, but can trigger it when a low fd limit is set).
You could try launching with PROTON_NO_ESYNC=1 %command% and see if that helps? CPU performance might decrease tho. People with kernel 5.16+ use fsync by default instead.

@Blisto91 game has successfully launched three times in a row with that option. Thanks :+1:

@Blisto91 I think the map count did the trick for the loading screen crashes. I've been able to fast travel to 6 different locations and it still hasn't crashed. My best before the change was 2. My max_map_count was only 65530 before the change

Hello. Could any of you people with the crash issue try something to see if it helps? In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/sysctl.conf This change should kick in after a reboot or if you run sudo sysctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on Deck

On newer versions of systemd you need to create a .conf file inside /etc/sysctl.d/.
I created file named 99-max_map_count.conf with the parameter vm.max_map_count=1048576.

On the next boot, you can check the value of 1048576 with cat /proc/sys/vm/max_map_count.

Thanks. Edited my comment to link to yours

Changing vm.max_map_count=1048576 seems to have fixed the crashes in my limited testing.

ulimit -Hn

$ ulimit -Hn
16384

@kisak-valve Is this better?

$ ulimit -Hn
1048576
$ ulimit -Sn
524288

@Blisto91 thanks for this tip. vm.max_map_count=1048576 solved issue with a crash during loading/fast travel on my both PC (Fedora 37 on both).

My OS limits looks following:
ulimit -Hn: 1048576
ulimit -Sn: 1024

Can report that vm.max_map_count=1048576 (thanks https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422699309 https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422921442) seems to solve the scene-loading crashes. Been playing for several hours today with no issues.

$ ulimit -Hn
524288
$ ulimit -Sn
1024

steam-990080.log

Game crashes at startup right after the very first screen with "Warning: Read before playing". This is on kernel 6.2.0-060200rc4-generic with mesa 23.1.0-devel (git-3e2c768), running on Arc 770m.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1421916724

System: CachyOS 6.2.0-rc6-1-cachyos-rc
CPU: AMD Ryzen 7 4650G
GPU: AMD Radeon RX 6700 XT
DRIVER: Mesa 23.1.0_devel.166376.c6ebd2de71d
RAM: 32 GB
PROTON: ProtonGE-47

I have a 6700 XT and have discovered that if I change any of the graphics settings then the game is prone to crashing and even freezing. Eventually it happens during gameplay and then on subsequent game loads. What I found was that deleting the the game's shader folder steamapps/shadercache/990080, the three .ushaderprecache files at steamapps/compatdata/990080/pfx/drive_c/ProgramData/Hogwarts Legacy/, and the vkd3d shader cache at steamapps/common/Hogwarts Legacy/Phoenix/Binaries/Win64/ after changing any in-game settings or after editing GameUserSettings.ini. Once I did that I was able to play at 2K60 medium with RT Ambient Occlusion enabled for a couple hours when it froze during an Accio.

I also disabled VKD3D shader caching with VKD3D_CONFIG=pipeline_library_app_cache,dxr11.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1423451428

I've tried to get get raytracing to work with my 6700xt but after I enabled it with RADV_PERFTEST=rt, enabled ray traced shadows and restarted the game, it won't load. Were you only able to get ambient occlusion to work or did you try for shadows as well?

Replying to [#6510 (comment)](https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1423451428)

I just tried and I was able to get it working with Ambient Occlusion, Shadows, and HDR. Did you also enable VKD3D_CONFIG=dxr11? You have to set both or RTX won't work for our GPUs. I have to wipe every bit of graphics cache upon changing ray tracing settings since it tends to not make it past the title screen after enabling them.

EDIT: After doing a bit more testing before bed last night I realized that Ambient Occlusion is all that I can get to enable from KDE/X11. Turning on either Reflections or Shadows from KDE causes the game to freeze on the warning screen. Turning on Ambient Occlusion works. I wiped all the caches every time I changed a graphics setting.

I have to use an embedded Gamescope session in order to turn on and use Shadows. I don't know if HDR is or isn't a requirement since I haven't tried Shadows in a non-HDR Gamescope session.

I haven't tried Reflections, alone or combined with other RT options, from a Gamescope session. I'll try that today and also try to see if an HDR enabled Gamescope session is necessary, too.

For whatever reason, turning on Reflections from KDE caused the game to not load as well as wiping the caches to force a rebuild didn't work to fix it like it did for the rest of the settings. Even wiping the caches and resetting the settings still caused the game to freeze at the warning screen. I ended up having to wipe my Proton prefix and, unfortunately, I relied to heavily on Steam Cloud Sync so I lost my save game when I did that. The game did load and work after wiping the prefix. I just wish I'd have backed up my save games before going the nuclear route.

Crashes at every loading screen after around 20minutes of gamepaly. Disabling esync did not help.

System: Arch (Kernel 6.1.9-arch1-2)
CPU: AMD Ryzen 9 5900X
GPU: AMD Radeon RX 6800 XT
DRIVER: Mesa 22.3.4-1
RAM: 32 GB
WM: Bspwm

Tried to run the game in 7.0-6 / Experimental (bleeding and not) / GE 7-49
Primary Issue:
But no matter what I do, I get a stable 20fps in the menu and 15-16 fps in the game. No matter what settings I use. With my steamdeck I just started it and got a pretty stable 40 on low.

Tried the launcher options in this thread however no change from what I can see.

Secondary, mostly just a question:
Also when starting the game with the Steamdeck I go straight into the menu after the warning text. But on this PC I need to process shaders for a few minutes each time I start?

Not really seen anyone else with this issue.

Can confirm that increasing vm.max_map_count fixes the fast travel crashes. I have set it to 262144 and it seems enough.

@SOlsson91 I also have shaders processing at the start but it is relatively fast.

Secondary, mostly just a question: Also when starting the game with the Steamdeck I go straight into the menu after the warning text. But on this PC I need to process shaders for a few minutes each time I start?

Not really seen anyone else with this issue.

That's not really an issue. It's how the game works. Any time I change the in-game settings and it prompts for me to restart the game the shaders will regenerate whenever the game restarts. I've also noticed that shader generation time will vary based on your selected graphics settings. Turning on RT can double the time it takes.

All that combined is what gave me the idea to intentionally wipe all the shader caches after changing graphics settings.

It doesn't happen with the Steam Deck because they ship shader cache for it.

I have a 6700 XT and a 4650G (CPU only) and get 2K60/Medium with Ray Tracing Ambient Occlusion enabled.

To give a warning: I deleted my prefix one too many times so now I can't even open the game because it won't validate with Warner Brothers thanks to Denuvo. This sucks. I had no idea there were limits on trying to get a buggy game to launch. This is so anti-consumer it isn't funny.

To give a warning: I deleted my prefix one too many times so now I can't even open the game because it won't validate with Warner Brothers thanks to Denuovo. This sucks. I had no idea there were limits on trying to get a buggy game to launch. This is so anti-consumer it isn't funny.

Yes this sucks.
You should try again tomorrow.
I also saw this with different games. One gets rate limited.
It is quite pathetic because this is meant to slow down the process to crack the game which is essentially deciphering the .exe file.

Also for me the vm.max_map_count fixes the issue with loadingscreen fast travel crashes

5800X3D
6800 XT
32Gb RAM

@kisak-valve Sending over my gist, tried just now and still the same issue, no difference when changing graphics settings and 15-20 fps in game about 30 in menu.

@kisak-valve Sending over my gist, tried just now and still the same issue, no difference when changing graphics settings and 15-20 fps in game about 30 in menu.

Check to see if you have amdvlk installed pacman -Qs amdvlk I saw it in your gist. You'll want to remove it if you do, it can cause issues.

Check to see if you have amdvlk installed pacman -Qs amdvlk I saw it in your gist. You'll want to remove it if you do, it can cause issues.

That was it! Removed amdvlk and lib32-amdvlk. Went from 20 fps low to pretty smooth 100+ fps high.
Thanks, time to actually start playing the game.

I was learning how to do the lumos spell and it crashed the whole PC. I forced a shutdown and after loading my PC back up, it loads the game up to the initial black screen with seizure warning and then crashes the game.

5950x
7900 xtx

@sjyasuosj
try going to steamapps/common/Hogwarts Legacy/Phoenix/Binaries/Win64/ and deleting vkd3d-proton.cache and vkd3d-proton.cache.write (if they exist) and in steamapps/compatdata/990080/pfx/drive_c/ProgramData/Hogwarts Legacy/ delete all of the files that start with D3D

I have to do that every time I change the graphics settings or get crashes during launch

@t-jonesy
I don't have vkd3d-proton.cache and vkd3d-proton.cache.write files. I did delete the D3D files. I'm still crashing lol

I was learning how to do the lumos spell and it crashed the whole PC. I forced a shutdown and after loading my PC back up, it loads the game up to the initial black screen with seizure warning and then crashes the game.

5950x 7900 xtx

I've been experiencing this same PC crashing issue, but I'm able to play again after the crash. After doing Control+Alt+F3, I saw [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! So it appears to be crashing the amdgpu driver.

This is on Ubuntu 22.10, kernel 5.19.0-29, mesa 22.2.5. Hardware being a Ryzen 5600x and a 6700 XT.

Oh, something extremely weird happened. As I went to play my game again after this crash, the game isn't even listed as installed anymore. Steam just completely forgot about the external disk the game was stored on.

Getting out of vram error while only using 11 gb vram at the time with hogswarts legacy not sure if related or different issue on my 6900 XT, im playing on Arch Linux to escape AMD radeon driver hell on windows my Linux Experience is limited but good enough to figure out stuff on my own except in this case.

Getting out of vram error while only using 11 gb vram at the time with hogswarts legacy not sure if related or different issue on my 6900 XT, im playing on Arch Linux to escape AMD radeon driver hell on windows my Linux Experience is limited but good enough to figure out stuff on my own except in this case.

My display driver is crashing with a 6700xt cant get past the character creator might be the same issue

Getting out of vram error while only using 11 gb vram at the time with hogswarts legacy not sure if related or different issue on my 6900 XT, im playing on Arch Linux to escape AMD radeon driver hell on windows my Linux Experience is limited but good enough to figure out stuff on my own except in this case.

My display driver is crashing with a 6700xt cant get past the character creator might be the same issue

My system just froze so i guess its happening for me as well darn it, guess i try on windows for now see if its any better there.

I had a crash on launch issue that was solved by moving the game from my external SSD to the same drive Steam was installed on. It was getting a permission error. I will update with the error log once I'm back on my machine.

Thought I would share just in case anyone is experiencing a crash on launch and has it on an external drive.

Well no more testing i hit activation limit, so appearntly every proton vision uses 1 activation and you can activate 5 times a day this is messed up, activations should be system wide not per operating or proton vision i hate Denuvo now, they cant even check per ip and machine id to see if its still same user ? meh i read tommorow if there is a fix else i give up on playing this on Linux till they remove denuvo.

The Menu Reader function from the accessibility options is broken. Works fine on Windows according to friends, but on Linux it always says "the current language is not supported" when attempting to turn it on; regardless of what language is selected in Steam.

Using Linux Mint 22.04 with Proton Experimental.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1426068813

Game is a stutter-fest on my nvidia 2060 laptop....framerates drop like mad after cutscenes. decreasing quality to low will give me 14 fps somehow even though i was getting 20fps at ultra.

I will then close the game and reload into the same area and magically get 60 fps....and then frame rates will decrease after that

@t-jonesy I don't have vkd3d-proton.cache and vkd3d-proton.cache.write files. I did delete the D3D files. I'm still crashing lol

If you have any RT settings enabled, turn them off. With my 6700 XT on the early access version I could get working RT AO on both Linux and Windows. Ever since the update yesterday I can't get RT AO to work and the game's crash logs indicate that the game engine is crashing on RT shader compilation on start up.

There's also a 3rd shader cache at steamapps/shadercache/990080 that can be deleted.

Oh, and on Windows after the latest update I have to delete ProgramData/Hogwarts Legacy/those cache files every time I start the game now regardless of any settings I change. This game has horrible cache issues.

played few hours, and now gives me error message who directs me to support page, i tried few things but nothing, i have two gpu one amd the other nvidia with both gives me the same error so i don't think is a problem related to drivers, at this point i don't know what to do i link here the log file:
steam-990080.log

Replying to [#6510 (comment)](https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1426068813)

Game is a stutter-fest on my nvidia 2060 laptop....framerates drop like mad after cutscenes. decreasing quality to low will give me 14 fps somehow even though i was getting 20fps at ultra.

I will then close the game and reload into the same area and magically get 60 fps....and then frame rates will decrease after that

If your frames are dropping after some time, isn't that an indicator your VRAM is maxed? I've also read there are issues with DLSS. Try using FSR2 on balanced or something so your GPU uses less VRAM.

Hello. Could any of you people with the crash issue try something to see if it helps? In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/sysctl.conf This change should kick in after a reboot or if you run sudo sysctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on >Deck.

Thanks! This seems to have fixed crashes on my hardware too. Is anyone else playing with the AMD FSR 1 and AMD FSR 2 settings? I have a Rx 5700 xt and FSR 2 is slower than FSR 1 by a huge amount. Sometimes 30 or 40 fps. Even if FSR 1 is expected to be faster on older hardware it does not seem right to have such a big gap.

I can also confirm that setting /proc/sys/vm/max_map_count to a high value eliminated crashes when fast traveling.
I had a stuttering issue as well. Turning swap off improved the situation significantly. Reducing the swappiness to 5 also had a similar effect. The situation improved further after switching to Proton GE, turning VSYNC on and setting FPS limit to uncapped.

Is anyone else playing with the AMD FSR 1 and AMD FSR 2 settings?

I just tried this. FSR 2 is a bit better for me, but not significantly.

I just tried this. FSR 2 is a bit better for me, but not significantly.

I see. Now that I have access to more places in the map I can see that the difference in performance is not so big everywhere. But so far FSR 2 has always been slower.

Increasing the setting in the max map count fixes the fast travel crashes, the game runs pretty well...

But i have a issue i havent seen anyone talking about and i dont know if its just for me, but in the open world when i just walk around the game would completely crash my system back to gdm log in screen, its like a complete graphics driver crash.

I tried everything but i am on a part in the game now where it happens constantly, since i have to follow a character i cant get past that part since complete system crash at the same exact spot.

Using arch linux and the mesa drivers.

But i have a issue i havent seen anyone talking about and i dont know if its just for me, but in the open world when i just walk around the game would completely crash my system back to gdm log in screen, its like a complete graphics driver crash.

I am also on Arch Linux with gnome and mesa drivers but this kind of crash I have not seen. Try to take a look at sudo journalctl | grep -i gpu, sudo journalctl | grep -i drm or sudo journalctl | grep -i gdm. If you are lucky you may see some kind of warning telling why it is happening.

Also arch and mesa here.
Ever since I've deleted caches from all the places AND started using VKD3D_CONFIG=pipeline_library_app_cache AND stopped using RADV_PERFTEST=gpl the game stopped randomly crashing my desktop. Ofc I also have vm.max_map_count set.
I currently have a 7h issues-free session

Edit: Actually never mind, I reverted to using no envvars and no gamemode it is working fine for now so I don't see any pattern here.

But i have a issue i havent seen anyone talking about and i dont know if its just for me, but in the open world when i just walk around the game would completely crash my system back to gdm log in screen, its like a complete graphics driver crash.

I am also on Arch Linux with gnome and mesa drivers but this kind of crash I have not seen. Try to take a look at sudo journalctl | grep -i gpu, sudo journalctl | grep -i drm or sudo journalctl | grep -i gdm. If you are lucky you may see some kind of warning telling why it is happening.

It throws out a massive log but from what i can see before it says reset, then reset succeeded is, error ring gfx_0.0.0 timeout, signaled seq=1392901, emitted seq=1392903

The line below that says: error process information:process hogwartslegacy. Pid 7603 thread hogwartslegacy. Pid 7603

Then it says gpu reset begin it has the same string repeated probably of my multiple tries.

Also arch and mesa here. Even since I've deleted caches from all the places AND started using VKD3D_CONFIG=pipeline_library_app_cache AND stopped using RADV_PERFTEST=gpl the game stopped randomly crashing my desktop. Ofc I also have vm.max_map_count set. I currently have a 7h issues-free session

I will try this, thank you.

Then it says gpu reset begin it has the same string repeated probably of my multiple tries.

That sounds like the gpu driver crashing. What is your GPU?

Then it says gpu reset begin it has the same string repeated probably of my multiple tries.

That sounds like the gpu driver crashing. What is your GPU?

6500xt,

For me game is running nice, but takes a lot of time to boot. Am I the only one?

For me game is running nice, but takes a lot of time to boot. Am I the only one?

Without any changes It's the same for me but I've found that VKD3D_CONFIG=pipeline_library_app_cache makes launching the game a lot faster because it doesn't freeze at the beginning. Also remember that this game uses Denuvo so launch times are bound to be longer.

But i have a issue i havent seen anyone talking about and i dont know if its just for me, but in the open world when i just walk around the game would completely crash my system back to gdm log in screen, its like a complete graphics driver crash.

I started having the same issue when I was running around Hogsmeade for the first time, crashing every 5 minutes or so. Sometimes just the game, sometimes the graphics drivers. After that I seem to have been able to fix it somehow by:

• Updating all my packages.
• Rebooting.
• Deleting the files mentioned in this comment.

Not sure which of them fixed it, but since doing that I was able to play for 4 hours before crashing once, and then another 2 hours. Running proton experimental with no special command line.

I've confirmed that Ray Tracing Ambient Occlusion causes the 6700 XT to crash on startup on both Windows and Linux with the Day One Patch while it works on the Early Access version. These are the game's crashlogs from Windows 11 and CachyOS using the same in-game settings aside from HDR (I've tested RT with HDR on Linux; same results).

windows.tar.gz
linux.tar.gz

Related to that, on Windows it automatically compresses their crash file, the .dmp file, but not on Proton/Linux.

Unrelated to any of that, using a wireless PS5 controller on Windows 11 it shows the PS5 controller prompts while on Linux it shows me Xbox prompts. Same controller, same PC.

Unrelated to any of that, using a wireless PS5 controller on Windows 11 it shows the PS5 controller prompts while on Linux it shows me Xbox prompts. Same controller, same PC.

I have to connect via USB and disable Steam Input to get PS5 controller prompts. But I don't have vibrations with this config.

Hello @thatLeaflet, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

It would be nice to know how the game behaves with an up to date mesa build from a PPA like oibaf or kisak-mesa. That would make it easier for a mesa dev to ponder.

Game crashed, here's the proton log. In the time since I made my first reply, I switched to Fedora Silverblue and installed Steam as a flatpak.

Steam System Information Gist
steam-990080.zip

I've been trying to get this to run at all (docker container running steam-headless) - the game doesn't actually launch (it says running on steam for a minute or so, before it just closes/stops) . Was able to get a log with PROTON_LOG=1, but have since been blocked for 24 hours by wonderful Denuovo because it never gets past what they consider the activation I guess?

steam-990080.log

Looking for any input from anyone. I see this listed a few times

1872413.845:0028:002c:err:seh:install_bpf Native libs are being loaded in low addresses, sc_seccomp 0x15007e146580, syscall 0x15007fe442d0, not installing seccomp. 1872413.845:0028:002c:err:seh:install_bpf The known reasons are /proc/sys/vm/legacy_va_layout set to 1 or 'ulimit -s' being 'unlimited'.

Then there's obviously an actual exception a few lines down...Again, any input would be helpful. Trying to get this setup for my wife.

Feb 12 16:31:46 Y4M1-II kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          RW: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000800026c9c000 from client 0x1b (UTCL2)
Feb 12 16:31:36 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32788, for process HogwartsLegacy. pid 119019 thread HogwartsLegacy. pid 119144)

Just crashed for me now. Had to reboot as it caused the entire GPU to freak out.

My GPU is the Asrock RX 6900 XT Phantom Gaming D

0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c0) (prog-if 00 [VGA controller])
        Subsystem: ASRock Incorporation Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
        Flags: bus master, fast devsel, latency 0, IRQ 152, IOMMU group 30
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at e0000000 (64-bit, prefetchable) [size=2M]
        I/O ports at f000 [size=256]
        Memory at fbf00000 (32-bit, non-prefetchable) [size=1M]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

The full specs:

Operating System: Kubuntu 22.10
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.6
Kernel Version: 6.1.11-1-liquorix-amd64 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570S AORUS MASTER
System Version: -CF

It recognizes my PS4 controller but doesn't take any input from it. Works fine on windows.

Also arch and mesa here. Ever since I've deleted caches from all the places AND started using VKD3D_CONFIG=pipeline_library_app_cache AND stopped using RADV_PERFTEST=gpl the game stopped randomly crashing my desktop. Ofc I also have vm.max_map_count set. I currently have a 7h issues-free session

what did you mean when you say you "stopped using RADV_PERFTEST=gpl"?

I'm getting "Out of video memory trying to allocate a rendering resource" error every time I launch it now, use to run nicely before. I'm on Nvidia with the launch options PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command% but even without it's not really helping. This is only with proton experimental, going with the default just never shows any screen and I can only hear music.

I've hit a page fault a couple of times now. The drivers have recovered, but the game (and often my WM) has not.

Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32780, for process HogwartsLegacy. pid 82633 thread HogwartsLegacy. pid 82633)
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:   in page starting at address 0x000080002203c000 from client 0x1b (UTCL2)
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101430
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 12 19:36:27 pc kernel: amdgpu 0000:0c:00.0: amdgpu:          RW: 0x0
Feb 12 19:36:37 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=60767188, emitted seq=60767191
Feb 12 19:36:37 pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 82633 thread HogwartsLegacy. pid 82633

I had PROTON_LOG=1 on the command line when it happened, but there's seemingly nothing of interest in there. steam-990080.tar.gz

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1427297713

Same here, i am on a part of the map where if i just walk a meter it does that complete driver crash, the logs say the exact as yours. Rendering the game unplayable and i tried all advice given(thank you for that) but nothing works, so i gave up for a bit on it.

Same here, i am on a part of the map where if i just walk a meter it does that complete driver crash, the logs say the exact as yours. Rendering the game unplayable and i tried all advice given(thank you for that) but nothing works, so i gave up for a bit on it.

Try to see if using the variables RADV_DEBUG and RADV_PERFTEST https://docs.mesa3d.org/envvars.html to disable some GPU features when launching the game helps. If some of them actually make a difference a bug report should be opened at radv page so they can investigate the problem.

Has someone here tried to disable split lock (kernel 5.19 and above)?

I have not a single issue with split lock disabled and using vm.max_map_count=1048576 to mitigate the memory leak.
I also noticed that Hogwarts Legacy is the only game that triggers SWAP on my end with swappines set to 60, 32GiB RAM and SWAP size of 4GiB.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1428435588

This seems probably like something I should know, but how does one disable it? :)

@samip5 seems its a kernel parameter split_lock_detect=off

https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html

Will also give it a try, my game just dies of lag when entering combat.

Proton GE 49 helped a ton though. I'm able to run the game on mid-high-ultra with mostly 40-60 fps just walking about. Rtx 3060 mobile with and i7 11800h, 64GB of ram.

EDIT: nvm I'm on 5.15

@samip5 you have to put split_lock_detect=off to your kernel start parameter.

For how you do it you should seek help from someone else because i have no clue. OpenSUSE made it very easy for me with YaST, that's why i was able to do it.

So I've been running Hogwarts Legacy with proton 7.0-6 and everything is working fine except ray-tracing.

I've enabled proton to see and report my nvidia RTX 3080 like so:
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr,dxr11 PROTON_ENABLE_NGX_UPDATER=1 PROTON_LOG=1 %command%

During game start I get the following errors reported:

810.253:0144:0190:warn:seh:OutputDebugStringA "LowLevelFatalError [File:Unknown] [Line: 715] \nRayTracingDevice->CreateStateObject(&Desc, IID_PPV_ARGS(Result.GetInitReference())) failed \n at W:/Engine/Source/Runtime/D3D12RHI/Private/D3D12RayTracing.cpp:384 \n with error E_INVALIDARG\n\n"
810.253:0144:0190:warn:seh:dispatch_exception "LowLevelFatalError [File:Unknown] [Line: 715] \nRayTracingDevice->CreateStateObject(&Desc, IID_PPV_ARGS(Result.GetInitReference())) failed \n at W:/Engine/Source/Runtime/D3D12RHI/Private/D3D12RayTracing.cpp:384 \n with error E_INVALIDARG\n\n"

And this:

824.288:028c:0290:trace:unwind:dump_unwind_info 0xe: pushq %r13
824.288:028c:0290:trace:unwind:dump_unwind_info 0xc: pushq %r14
824.288:028c:0290:trace:unwind:dump_unwind_info 0xa: pushq %r15
824.288:028c:0290:trace:seh:RtlRestoreContext returning to 000000007B07ED4A stack 0000000000B7D0C0
824.289:028c:0290:warn:seh:OutputDebugStringA "[2023.02.13-21.33.40:913][ 0]LogWindows: Error: === Critical error: ===\r\n"
824.289:028c:0290:trace:seh:dispatch_exception code=40010006 flags=0 addr=000000007B013945 ip=000000007B013945 tid=0290
824.289:028c:0290:trace:unwind:dispatch_exception info[0]=000000000000004b
824.289:028c:0290:trace:unwind:dispatch_exception info[1]=0000000000d251d0
824.289:028c:0290:warn:seh:dispatch_exception "[2023.02.13-21.33.40:913][ 0]LogWindows: Error: === Critical error: ===\r\n"
824.289:028c:0290:trace:unwind:RtlVirtualUnwind type 1 rip 000000007B013945 rsp 0000000000B7CB40
824.289:028c:0290:trace:unwind:dump_unwind_info **** func 13660-13980
824.289:028c:0290:trace:unwind:dump_unwind_info unwind info at 000000007B0A856C flags 0 prolog 0x18 bytes function 000000007B013660-000000007B013980
824.289:028c:0290:trace:unwind:dump_unwind_info 0x18: subq $0x200,%rsp

Anyone any ideas what's happening here?

Might be worth trying experimental as the vkd3d-proton version that ships with 7 is kinda old.

@samip5 you have to put split_lock_detect=off to your kernel start parameter.

For how you do it you should seek help from someone else because i have no clue. OpenSUSE made it very easy for me with YaST, that's why i was able to do it.

Not every CPU supports split lock detection. Check with lscpu | grep split_lock_detect.
I'm pretty sure Ryzen and Intel CPUs before gen 12 don't have this feature.

Might be worth trying experimental as the vkd3d-proton version that ships with 7 is kinda old.

experimental at least manages to launch the game.. Judging by the music playing I've even made it into the menu except my screen is black.

01f0:warn:d3d12_pipeline_library_load_pipeline: Pipeline "AA54F4B581E077F1" does not exist.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 2.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 3.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 4.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 5.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 6.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 7.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 8.
01f0:warn:d3d12_pipeline_state_init_graphics_create_info: Unused input element 9.
01f0:warn:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
0200:warn:d3d12_pipeline_library_load_pipeline: Pipeline "F1D777BB778040A7" does not exist.
0200:warn:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.

I get a ton load of these and the following errors:

01ec:warn:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
01ec:fixme:vkd3d_dxbc_compiler_emit_output: Unhandled component index 2.
01ec:warn:d3d12_pipeline_library_load_pipeline: Pipeline "58BBD96637D9F82C" does not exist.
01ec:warn:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
NGX Updater reported an error: error: failed to get server feature version in  NGX_UPDATER_API_UPDATE
0210:warn:d3d12_pipeline_library_load_pipeline: Pipeline "2E66EC47F637F9D3" does not exist.
0210:warn:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
01e0:warn:d3d12_pipeline_library_load_pipeline: Pipeline "D88A59EC5F3D1FB7" does not exist.
01e0:warn:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.

Okey when I remove PROTON_ENABLE_NGX_UPDATER=1 Everything works fine.. I don't really get up to 60 FPS with everything ( including ray-tracing ) on Ultra but I hover around 30 FPS which is fine considering that there aren't any optimized graphic drivers yet ( neither on windows ).

Proton experimental does the trick!

PC Specs:

OS: POP!_OS 22.04 LTS x86_64
KERNEL: 6.0.12-76060006-generic
CPU: AMD Ryzen 7 3800X (16) @ 3.900GHz
GPU: NVIDIA GeForce RTX 3080
Memory: 6721MiB / 32024MiB

My last question would be: What exactly does NGX_UPDATER do and would the game run better with it on and if so why doesn't it work for me?

Unrelated to any of that, using a wireless PS5 controller on Windows 11 it shows the PS5 controller prompts while on Linux it shows me Xbox prompts. Same controller, same PC.

I have to connect via USB and disable Steam Input to get PS5 controller prompts. But I don't have vibrations with this config.

If you haven't seen it, there's a PS icon mod which is what I use on Linux since I don't have any controller issues on Windows 11.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issue-1575220402

I can confirm that the rendering issue with clothes, both your own character and NPC's occurs with 7900 XTX I don't have this issue with 6900 XT.

No issues with 6900 XT with the vm.map increase to anything above 1 000 000.

Here's a proton log for running the game with 7900 XTX
steam-990080.zip

PC specs:
Operating System: Fedora Linux 37
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.10-200.fc37.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor
Memory: 31.1 GiB of RAM
Graphics Processor: Radeon RX 7900 XTX
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 GAMING X AX
System Version: -CF

I have been running it great after the vm.max_map_count change and using the following launch args: VKD3D_CONFIG=pipeline_library_app_cache PROTON_LOG=1 RADV_DEBUG=1

I can confirm that the rendering issue with clothes, both your own character and NPC's occurs with 7900 XTX I don't have this issue with 6900 XT.

Just as a quick fyi to rdna3 users.

A MR has been merged into mesa main (mesa git) that works around this issue.
If people instead prefer to use the stable radv (mesa) drivers then, until the workaround hits a stable release, launching the game with RADV_DEBUG=nodcc %command% can also rid the problem.

New update out that might solve a bunch of issues.
https://hogwartslegacy.bugs.wbgames.com/patch-notes

Can confirm, performance has improved quite a bit with the new update. But I'm still getting the occasional stutter, specially sometimes after opening the menu; and the game still crashes sometimes when fast travelling.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1430365652

Thank you! This fixed the clothing rendering issue.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1430365652

"Main mesa" is that the mesa-git? Sorry for asking have been using linux for a few years but always stuck to drivers available in the repositories. This game was the first game that crashed my gpu on linux and made me hesitant to play it.

I tried every launch arguement including the nodcc nothing worked, so im guessing its a issue related to my amd card since i dont see many people noting full gpu crashes.

"Main mesa" is that the mesa-git?

Sorry yea hehe. Meant mesa git

So I've been running Hogwarts Legacy with proton 7.0-6 and everything is working fine except ray-tracing.

Anyone any ideas what's happening here?

If you have an AMD GPU, ray tracing is very hit and miss. With the Early Access version I was able to use all the RT settings, though only RT AO performed well enough to use with my 6700 XT. As long as the shader cache was wiped it launched every time.

When the Day One Patch came out, all the RT settings quit working for me. No amount of cache wiping would fix it.

With yesterdays update, I can get RT to work only if I turn on every single RT setting, set RT to Medium, turn the rest of the in-game settings to High or Medium, and then do some voodoo because with RT enabled it'll pass the shader screen 1 in 10 times. You have to wipe the shader cache each time with RT enabled because it'll go from warning to blank screen if you don't.

I get the same errors you get on Windows and Linux. It is very apparent that the developers didn't do a whole lot of RT testing with AMD GPUs.

My latest tests were using Mesa, Gamescope, DXVK, VKD3D-Proton, and Proton, everything from git, from around 8am yesterday with Linux 6.2 as well as Windows 11 was fully up to date with the AMD driver released yesterday.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422921442

I created this file and everything works now. Thanks <3

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1427138732

steam-990080.log

My Ray Tracing Quality is set to ultra but greyed out.

I'm getting the same crash mentioned here https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1427138732.

fev 18 18:14:10 user-pc kernel: umip_printk: 17 callbacks suppressed
fev 18 18:14:10 user-pc kernel: umip: HogwartsLegacy.[3758] ip:1563693cd sp:b9c3a8: SGDT instruction cannot be used by applications.
fev 18 18:14:10 user-pc kernel: umip: HogwartsLegacy.[3758] ip:1563693cd sp:b9c3a8: For now, expensive software emulation returns the result.
fev 18 18:14:10 user-pc kernel: umip: HogwartsLegacy.[3758] ip:1570c136f sp:b9c890: SGDT instruction cannot be used by applications.
fev 18 18:14:10 user-pc kernel: umip: HogwartsLegacy.[3758] ip:1570c136f sp:b9c890: For now, expensive software emulation returns the result.
fev 18 18:14:11 user-pc kernel: umip: HogwartsLegacy.[3758] ip:1563693cd sp:b9c3a8: SGDT instruction cannot be used by applications.
fev 18 18:16:44 user-pc kernel: umip_printk: 65 callbacks suppressed
fev 18 18:16:44 user-pc kernel: umip: HogwartsLegacy.[4018] ip:1519ac43c sp:a13fecd8: SGDT instruction cannot be used by applications.
fev 18 18:16:44 user-pc kernel: umip: HogwartsLegacy.[4018] ip:1519ac43c sp:a13fecd8: For now, expensive software emulation returns the result.
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32793, for process HogwartsLegacy. pid 3758 thread HogwartsLegacy. pid 3758)
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x000080006daaf000 from client 0x1b (UTCL2)
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
fev 18 18:17:15 user-pc kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
fev 18 18:17:24 user-pc plasmashell[969]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
fev 18 18:17:25 user-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
fev 18 18:17:25 user-pc plasmashell[969]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
fev 18 18:17:25 user-pc kwin_wayland[866]: kwin_scene_opengl: A graphics reset not attributable to the current GL context occurred.
fev 18 18:17:26 user-pc kwin_wayland[866]: kwin_scene_opengl: Waiting for glGetGraphicsResetStatus to return GL_NO_ERROR timed out!

I don't know if it's just me, but it appears to be more stable if I use gamescope. I'll update this if I notice otherwise

Few days ago, I was gonna play Hogwarts Legacy on my Steam Deck, but it gave me an error saying I needed to launch it on online mode first when I was on the road.

The things is that I already did that a week ago.

With the most recent updates, everything feels more stable, I can even enable RT on medium with a mix of mid/high/ultra setting with an i7 11800h and a rtx 3060 mobile.

However, there are times when fps just tanks, around 60% of the time it's fixable by just opening and closing the menu. But the other 40% just makes the game progressively slower every time I close the menu.

I still have to apply the vm memory patch or else the game force closes sometimes after the loading screen. I didn't have to apply any patch on the steam deck because the value is already set to high value by default.

Right now, I'm getting over 60 fps most times with low 20s seldomly with ambient occulusion RT enabled on medium (will try to bump it to ultra) and everything else RT disabled on my laptop and around 30-60s overall with 80-100s on dungeons on the steam deck.

The game is almost perfect right now.

One thing that I'd love to see would be GPU direct access to textures stored on the SSD, like the ps5 has. This would probably remove the majority of the loading screens like we see on the ps5 version of the game.

EDIT: I was able to setup rt to ultra but I disabled all Ray tracing options, it was bringing my fps and gpu usage down significantly every once in a while (fixed by reloading the save, but I had to do it every 30 mins or so).

I had 2 annoying issues where fixes listed here solved them:

1. crashing to desktop - fixed by increasing max_map_count see: https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422921442
2. cut scene audio becoming very out of sync - fixed by reducing swappiness see: https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1426879086

Hopefully that helps others

sidenote: I reduced my swappiness to 5, rather than disable it. Hogwarts legacy still triggered swap, but not enough to force audio noticeably out of sync (that I've noticed yet)

Edit adding system details:
Ubuntu 22.10
Proton Experimental/Proton GE7-49
32gb ram
nvidia 3070 - ReBar enabled
X11

~I don't know if it's just me, but it appears to be more stable if I use gamescope. I'll update this if I notice otherwise~

Never mind. I created a ticket in the Mesa GitLab.

So there is definitely a memory leak, but strangely its only writing to swap it seems. On my machine, I have to keep swap on or else the process for HWL just crashes on launch. I set the max_map_count to 1Mil and that helped a lot with the crashing, but also in conjunction with adding AMD_VULKAN_ICD=RADV in my launch parameters, it solved a ton of the frame rate issues. I did notice though that during gameplay there is a ton of stuff written to memory that is regularly cleaned aka memory consumption drops back down. However, the swap does not. So it seems it's writing something into swap and not coming back to clean it up. That seems to be why most people say these steps "help make the crashes less frequent", however something else in the code must not be going back to clean up things it wrote into swap. Unfortunately, if you have less than 32GB of RAM, swap is going to be a necessity in this game. It seems to have used just at launch almost all 16GB RAM I have and ate into 8 GB of swap space. Over about 2 hours it rose to beyond 10 and never decreased.

I managed to play for 2-3 hours before the following crash. I have saved the entire log journalctl (minus keysync/ip stuff) around the time of the event in the following gist. Most of it is likely not relevant.

https://gist.github.com/Chase-san/832fa24ca5bf30afa38d9f553ac8db86

In response to the previous comment, I have 32 GiB of memory and only 2 GiB of swap.

It's not problem with Hogwarts Legacy only, PS5 gamepad has issues with many games when it's connected via Bluetooth.

I have to use Steam Input when connected via Bluetooth in many games. Disabling Steam Input causes that gamepad is not detected at all.

When PS5 gamepad is connected via USB and I disable Steam Input, games shows PlayStation icons.

Some examples (Proton Experimental):

• RWBY (418340) - PS5 gamepad connected via Bluetooth with Steam Input disabled works correctly (shows PlayStation icons)
• Witcher 3 (292030) - PS5 gamepad connected via Bluetooth with Steam Input disabled doesn't work, Steam Input enabled shows Xbox icons, Steam Input disabled via USB shows PlayStation icons and uses more gamepad features
• Hogwarts Legacy (990080) - PS5 gamepad connected via Bluetooth with Steam Input disabled doesn't work, with Steam Input enables shows Xbox icons (vibrations work), Steam Input disabled via USB shows PS5 icons, but vibrations don't work

I noticed that the gamepad name differs:

• Bluetooth: hidraw4: BLUETOOTH HID v1.00 Gamepad [Wireless Controller]
• USB: hidraw4: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller]

I'm using kernel 6.2 with the latest mesa 23 drivers, applied the above mmap fix, but this mmap fix still does not fix the issue of Hogwarts Legacy not opening?

I'm using the Intel Arc a770 discrete desktop graphics card with an AMD 5800x3d processor, so my issue might be more specific?

https://www.reddit.com/r/IntelArc/comments/10ymhkk/has_anyone_here_tried_running_hogwarts_legacy/

https://www.reddit.com/r/linux_gaming/comments/10x1e6u/fix_hogwarts_legacy_loading_screen_crash/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32788, for process HogwartsLegacy. pid 10345 thread HogwartsLegacy. pid 10345)
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080003b8f8000 from client 0x1b (UTCL2)
amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Sometimes it's a few second freeze, sometimes GPU reset and X11 session restart (I've got GPU reset sometimes on shaders loading screen). RX 6900XT, Mesa 23.0.0, Kernel 6.1.13. More people hae this issue, so I guess it's not UV issue :smile:

:astonished: My GPU has 16 GiB

memoryHeaps: count = 2
	memoryHeaps[0]:
		size   = 16508567552 (0x3d7fcc000) (15.37 GiB)
		budget = 16179281920 (0x3c45c4000) (15.07 GiB)
		usage  = 0 (0x00000000) (0.00 B)
		flags:
			None
	memoryHeaps[1]:
		size   = 17163091968 (0x3ff000000) (15.98 GiB)
		budget = 5564796928 (0x14bb01000) (5.18 GiB)
		usage  = 0 (0x00000000) (0.00 B)
		flags: count = 1
			MEMORY_HEAP_DEVICE_LOCAL_BIT

Looks like there's still a lot of free GPU memory (5.18 GiB). Proton-experimental.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1445140028

Yes i have the same GPU reset issue with this game, was told to make a mesa gitlab post or something, i am just like "i don't know how to do that, i am a gamer not a programmer" So guess it will take a while before they fix it, if it gets fixed. I only got to here from a protondb link. So will have to wait before finishing the game. Though my GPU crashes are very predictable, at two very specific spots where it just reset the whole system,

The first is when you just started the game and completed your first two classes (charms and defense against the dark arts) when you have to go to Hogsmead via following a classmate, on the way to Hogsmead just after they hipogryps flew over head just around the first bend the game resets/crashes my GPU, though i managed to get passed that with the RADV_DEBUG=nodcc launch arguement, and managed to play for +- 20 hours.

The game ran actually very well for those 20 hours i had almost no noticable stutters or framedrops or anything.

The second GPU crash is just after the beast class where you have to follow a classmate to meet her hipgryph friend. Nothing i did managed to get passed it, no ammount of launch arguments or anything could stop the GPU crashing issue, thus making it impossible to progress. I would have refunded the game but as i said i played 20hours +- so yeah fun times.

Thanks for the response. I hope it'll be fixed some day :smile: No need to refund.

I've got out of memory crash twice today so far, GPU short freeze twice, GPU crash once at loading screen...

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1445153764

https://gitlab.freedesktop.org/mesa/mesa/-/issues/8324

I was playing around by modifying the AMD_ICD_LOADER variable to AMDVLK (from RADV), and I lost my impressive performance. I used to be able to get 60-80FPS on native 1440p, and now I'm getting 25-40FPS. And it takes forever to startup now.

Doesn't change when I uninstalled AMDVLK. I do know I'm using RADV because I was testing Gamescope and it won't work with AMDVLK, and it started working again.

Also tried the following:

• delete shader cache
• deleted the wine prefix
• change from Proton 7.0-6 to Experimental

Any idea what I'm missing to fix my performance issue?

Edit: had to delete RADV_DEBUG=hang

I'm getting a strange crash at the start loading screen:

73649.417:0274:0278:warn:seh:OutputDebugStringA "Assertion failed: Client->QueryInterface( __uuidof( IDebugControl4 ), ( void** )&Control ) == ((HRESULT)0L) [File:W:/Engine/Source/Developer/CrashDebugHelper/Private/Windows/WindowsPlatformStackWalkExt.cpp] [Line: 54] \n\n"

Increasing vm.max_map_count did not resolve my issue.

Full log here:

https://gist.githubusercontent.com/mason-larobina/80f05174208cfba309b7a9cf24935c53/raw/8ef832a3df172afb3d79a6a28fd9a935cf0d6ed8/steam-990080.log

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1453051295

vm.max_map_count did resolves different issue, I think your crash is unrelated to this. However keep vm.max_map_count did set to high value to resolve another crash.

You're trying to run it on Intel integrated GPU Intel(R) UHD Graphics 620 (KBL GT2) - I guess it will not work correctly.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1445152064

Had same problem with my 3070ti and allowing pre-shader cache on Steam solved it.

So, I disabled the underclock and undervolt to my GPU, and now it simply kicks me out of my session (back to SDDM)

Here's my launch options: VKD3D_CONFIG=pipeline_library_app_cache PROTON_LOG=1 %command%
steam-990080.tar.gz

This part stuck out:

17165.604:0134:0138:trace:seh:sigsys_handler SIGSYS, rax 0x8e, rip 0x14e658ce8.
0410:warn:d3d12_resource_validate_create_info: Ignoring optimized clear value.
0410:warn:d3d12_resource_validate_create_info: Ignoring optimized clear value.
0410:warn:d3d12_resource_validate_create_info: Ignoring optimized clear value.
0410:warn:d3d12_resource_validate_create_info: Ignoring optimized clear value.
0410:warn:d3d12_resource_validate_create_info: Ignoring optimized clear value.
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:vkd3d_memory_allocator_flush_clears_locked: Failed to submit command buffer, vr -4.
02fc:warn:d3d12_device_mark_as_removed: Device 0000000037b50030 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
radv/amdgpu: The CS has been cancelled because the context is lost.
02fc:err:d3d12_swapchain_queue_present: Failed to blit swapchain buffer, vr -4.
02fc:err:d3d12_swapchain_present: Failed to queue present, vr -4.
02fc:warn:d3d12_device_QueryInterface: {9727a022-cf1d-4dda-9eba-effa653fc506} not implemented, returning E_NOINTERFACE.
02fc:warn:d3d12_device_QueryInterface: {9727a022-cf1d-4dda-9eba-effa653fc506} not implemented, returning E_NOINTERFACE.
02fc:warn:d3d12_device_QueryInterface: {98931d33-5ae8-4791-aa3c-1a73a2934e71} not implemented, returning E_NOINTERFACE.
17178.020:0134:02fc:warn:seh:OutputDebugStringA "LowLevelFatalError [File:Unknown] [Line: 715] \nResult failed \n at W:/Engine/Source/Runtime/D3D12RHI/Private/D3D12Viewport.cpp:678 \n with error E_FAIL\n\n"

Mar 04 19:22:31 Y4M1-II systemd[1]: Started Session 16 of User yamiyuki.
Mar 04 19:22:31 Y4M1-II systemd-logind[2730]: New session 16 of user yamiyuki.
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: pam_unix(sddm:session): session opened for user yamiyuki(uid=1000) by (uid=0)
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 04 19:22:31 Y4M1-II sddm-greeter[77904]: Message received from daemon: LoginSucceeded
Mar 04 19:22:31 Y4M1-II sddm[5129]: Authenticated successfully
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: [PAM] returning.
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: gkr-pam: stashed password to try later in open session
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: gkr-pam: unable to locate daemon control file
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: [PAM] Conversation with 1 messages
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: [PAM] Preparing to converse...
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: [PAM] Authenticating...
Mar 04 19:22:31 Y4M1-II sddm-helper[77939]: [PAM] Starting...
Mar 04 19:22:31 Y4M1-II sddm[5129]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11"
Mar 04 19:22:31 Y4M1-II sddm[5129]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 04 19:22:31 Y4M1-II sddm[5129]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 04 19:22:31 Y4M1-II sddm[5129]: Message received from greeter: Login
Mar 04 19:22:31 Y4M1-II sddm-greeter[77904]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 04 19:22:29 Y4M1-II bluetoothd[2702]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mar 04 19:22:26 Y4M1-II systemd-logind[2730]: Removed session 3.
Mar 04 19:22:26 Y4M1-II systemd[1]: session-3.scope: Consumed 2.243s CPU time.
Mar 04 19:22:26 Y4M1-II systemd[1]: session-3.scope: Deactivated successfully.
Mar 04 19:22:22 Y4M1-II wireplumber[77901]: <WpSiAudioAdapter:0x55d518b99050> failed to activate item: Object activation aborted: proxy destroyed
Mar 04 19:22:22 Y4M1-II wireplumber[77901]: <WpSiAudioAdapter:0x55d518b99050> Object activation aborted: proxy destroyed
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Message received from daemon: HostName
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/opus_05_pro
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/opus_05_71
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/opus_05_51
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/opus_05
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSink/opus_05
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/faststream
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/sbc_xq
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSink/sbc_xq
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/sbc
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSink/sbc
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/aptx
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSink/aptx
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 04 19:22:22 Y4M1-II bluetoothd[2702]: Endpoint registered: sender=:1.316 path=/MediaEndpoint/A2DPSource/ldac
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Message received from daemon: Capabilities
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/>
Mar 04 19:22:22 Y4M1-II systemd[5515]: app-steam-f7698b86be3343e098fe0fce0b107bce.scope: Consumed 15h 9min 35.836s CPU time.
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Adding view for "DisplayPort-2" QRect(3840,0 2560x1440)
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SessionButton.qml:38:5: Unable to assign ComboBox_QMLTYPE_101 to Control_QML>
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/Input.qml:561:5: QML Connections: Implicitly defined onFoo properties in Con>
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Loading file:///usr/share/sddm/themes/sugar-candy/Main.qml...
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Adding view for "DisplayPort-0" QRect(0,0 3840x2160)
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SessionButton.qml:38:5: Unable to assign ComboBox_QMLTYPE_13 to Control_QMLT>
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/SystemButtons.qml:70:13: Unable to assign [undefined] to QQuickItem*
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: file:///usr/share/sddm/themes/sugar-candy/Components/Input.qml:561:5: QML Connections: Implicitly defined onFoo properties in Con>
Mar 04 19:22:22 Y4M1-II sddm-greeter[77904]: Loading file:///usr/share/sddm/themes/sugar-candy/Main.qml...
Mar 04 19:22:21 Y4M1-II wireplumber[77901]: PipeWire's libcamera SPA missing or broken. libcamera not supported.
Mar 04 19:22:21 Y4M1-II wireplumber[77901]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Mar 04 19:22:21 Y4M1-II sddm[5129]: Message received from greeter: Connect
Mar 04 19:22:21 Y4M1-II sddm-greeter[77904]: Connected to the daemon.
Mar 04 19:22:21 Y4M1-II sddm-greeter[77904]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Mar 04 19:22:21 Y4M1-II sddm-greeter[77904]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Mar 04 19:22:21 Y4M1-II sddm-greeter[77904]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 04 19:22:21 Y4M1-II pipewire-pulse[77910]: 536870912
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 12 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Successfully made thread 77911 of process 77902 owned by '119' RT at priority 20.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 11 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Successfully made thread 77909 of process 77900 owned by '119' RT at priority 20.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 10 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 10 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 10 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Successfully made thread 77907 of process 77901 owned by '119' RT at priority 20.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 9 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 9 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 9 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 9 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 9 threads of 6 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Successfully made thread 77900 of process 77900 owned by '119' high priority at nice level -11.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 8 threads of 5 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Successfully made thread 77901 of process 77901 owned by '119' high priority at nice level -11.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Supervising 7 threads of 4 processes of 2 users.
Mar 04 19:22:21 Y4M1-II rtkit-daemon[5168]: Successfully made thread 77902 of process 77902 owned by '119' high priority at nice level -11.
Mar 04 19:22:21 Y4M1-II pipewire[77900]: mod.rt: found session bus but no portal
Mar 04 19:22:21 Y4M1-II pipewire[77900]: mod.rt: Can't find xdg-portal: (null)
Mar 04 19:22:21 Y4M1-II wireplumber[77901]: found session bus but no portal
Mar 04 19:22:21 Y4M1-II wireplumber[77901]: Can't find xdg-portal: (null)
Mar 04 19:22:21 Y4M1-II pipewire-pulse[77902]: mod.rt: found session bus but no portal
Mar 04 19:22:21 Y4M1-II pipewire-pulse[77902]: mod.rt: Can't find xdg-portal: (null)
Mar 04 19:22:21 Y4M1-II systemd[77888]: Started D-Bus User Message Bus.
Mar 04 19:22:21 Y4M1-II sddm-greeter[77904]: High-DPI autoscaling not Enabled
Mar 04 19:22:21 Y4M1-II systemd[77888]: Starting D-Bus User Message Bus...
Mar 04 19:22:21 Y4M1-II sddm[5129]: Greeter session started successfully
Mar 04 19:22:21 Y4M1-II systemd[77888]: Startup finished in 127ms.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Reached target Main User Target.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Started PipeWire PulseAudio.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Started Multimedia Service Session Manager.
Mar 04 19:22:21 Y4M1-II systemd[1]: Started Session 14 of User sddm.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Started PipeWire Multimedia Service.
Mar 04 19:22:21 Y4M1-II systemd[1]: Started User Manager for UID 119.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Cleanup lingering KCrash metadata was skipped because of a failed condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash>
Mar 04 19:22:21 Y4M1-II systemd[77888]: Reached target Basic System.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Reached target Sockets.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on D-Bus User Message Bus Socket.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on REST API socket for snapd user session agent.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on debconf communication socket.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on PipeWire Multimedia System Socket.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on PipeWire PulseAudio.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GnuPG cryptographic agent and passphrase cache.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GNOME Keyring daemon.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GCR ssh-agent wrapper.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on Socket to launch DrKonqi for a systemd-coredump crash.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Listening on GnuPG network certificate management daemon.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Starting D-Bus User Message Bus Socket...
Mar 04 19:22:21 Y4M1-II systemd[77888]: Reached target Timers.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Reached target Paths.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Cleanup lingering KCrash metadata was skipped because of a failed condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash>
Mar 04 19:22:21 Y4M1-II systemd[77888]: Created slice User Core Session Slice.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Created slice User Application Slice.
Mar 04 19:22:21 Y4M1-II systemd[77888]: Queued start job for default target Main User Target.
Mar 04 19:22:21 Y4M1-II systemd-xdg-autostart-generator[77897]: /etc/xdg/autostart/org.kde.discover.notifier.desktop: not generating unit, error parsing Exec= line: No such f>
Mar 04 19:22:21 Y4M1-II systemd-xdg-autostart-generator[77897]: Exec binary '/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier' does not exist: No such file or directory
Mar 04 19:22:21 Y4M1-II systemd[77888]: pam_unix(systemd-user:session): session opened for user sddm(uid=119) by (uid=0)
Mar 04 19:22:21 Y4M1-II systemd[1]: Starting User Manager for UID 119...
Mar 04 19:22:21 Y4M1-II systemd[1]: Finished User Runtime Directory /run/user/119.
Mar 04 19:22:21 Y4M1-II systemd-logind[2730]: New session 14 of user sddm.
Mar 04 19:22:21 Y4M1-II systemd[1]: Starting User Runtime Directory /run/user/119...
Mar 04 19:22:21 Y4M1-II systemd[1]: Created slice User Slice of UID 119.
Mar 04 19:22:21 Y4M1-II sddm-helper[77883]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=119) by (uid=0)
Mar 04 19:22:21 Y4M1-II sddm-helper[77883]: [PAM] returning.
Mar 04 19:22:21 Y4M1-II sddm-helper[77883]: [PAM] Authenticating...
Mar 04 19:22:21 Y4M1-II sddm-helper[77883]: [PAM] Starting...
Mar 04 19:22:21 Y4M1-II sddm[5129]: Greeter starting...
Mar 04 19:22:21 Y4M1-II sddm[5129]: Loading theme configuration from "/usr/share/sddm/themes/sugar-candy/theme.conf"
Mar 04 19:22:21 Y4M1-II sddm[5129]: Socket server started.
Mar 04 19:22:21 Y4M1-II sddm[5129]: Socket server starting...
Mar 04 19:22:21 Y4M1-II sddm[5129]: Display server started.
Mar 04 19:22:21 Y4M1-II sddm[5129]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Mar 04 19:22:21 Y4M1-II sddm[5129]: Setting default cursor
Mar 04 19:22:21 Y4M1-II assert_20230304192220_7.dmp[77859]: file ''/tmp/dumps/assert_20230304192220_7.dmp'', upload yes: ''Discarded=1''
Mar 04 19:22:21 Y4M1-II assert_20230304192220_7.dmp[77859]: response: Discarded=1
Mar 04 19:22:21 Y4M1-II assert_20230304192220_7.dmp[77859]: Finished uploading minidump (out-of-process): success = yes
Mar 04 19:22:21 Y4M1-II plasmashell[77859]: assert_20230304192220_7.dmp[77859]: file ''/tmp/dumps/assert_20230304192220_7.dmp'', upload yes: ''Discarded=1''
Mar 04 19:22:21 Y4M1-II plasmashell[77859]: assert_20230304192220_7.dmp[77859]: response: Discarded=1
Mar 04 19:22:21 Y4M1-II plasmashell[77859]: assert_20230304192220_7.dmp[77859]: Finished uploading minidump (out-of-process): success = yes
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped target Session services which should run early before the graphical session is brought up.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped target Current graphical user session.
Mar 04 19:22:21 Y4M1-II systemd[5515]: snap.firefox_edge.firefox.bc979226-b707-4bdf-a727-2059236c4266.scope: Consumed 2h 5min 47.878s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: [email protected]: Consumed 23.752s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped CoreCtrl.
Mar 04 19:22:21 Y4M1-II systemd[5515]: [email protected]: Failed with result 'exit-code'.
Mar 04 19:22:21 Y4M1-II systemd[5515]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:21 Y4M1-II systemd[5515]: snap.discord.discord.a19658a8-1e27-4c22-9cc6-82dad8f6f4c7.scope: Consumed 2min 44.967s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: plasma-plasmashell.service: Consumed 10min 36.916s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped KDE Plasma Workspace.
Mar 04 19:22:21 Y4M1-II systemd[5515]: snap.bitwarden.bitwarden.65508407-91aa-4f31-86f2-50b557edccb0.scope: Consumed 1min 17.036s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: [email protected]: Consumed 19.787s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped Nextcloud.
Mar 04 19:22:21 Y4M1-II systemd[5515]: plasma-kwin_x11.service: Consumed 12min 19.574s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped KDE Window Manager.
Mar 04 19:22:21 Y4M1-II systemd[5515]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Mar 04 19:22:21 Y4M1-II systemd[5515]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:21 Y4M1-II sddm[5129]: Running: /usr/bin/X -dpi 0 -auth /var/run/sddm/{28f5b9cb-67eb-43ab-bba8-c5c8a4b5e92d} -background none -noreset -displayfd 18 -seat seat0 >
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-pia\[email protected]: Consumed 1min 49.531s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped Private Internet Access.
Mar 04 19:22:21 Y4M1-II sddm[5129]: Adding cookie to "/var/run/sddm/{28f5b9cb-67eb-43ab-bba8-c5c8a4b5e92d}"
Mar 04 19:22:21 Y4M1-II sddm[5129]: Display server starting...
Mar 04 19:22:21 Y4M1-II sddm[5129]: Loading theme configuration from ""
Mar 04 19:22:21 Y4M1-II sddm[5129]: Adding new display on vt 1 ...
Mar 04 19:22:21 Y4M1-II sddm[5129]: Removing display ":0" ...
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-1\[email protected]: Consumed 2.148s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped Yakuake.
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-1\[email protected]: Failed with result 'exit-code'.
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-1\[email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:21 Y4M1-II systemd[5515]: at-spi-dbus-bus.service: Consumed 1.192s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped Accessibility services bus.
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-indicator\[email protected]: Consumed 5.153s CPU time.
Mar 04 19:22:21 Y4M1-II systemd[5515]: Stopped CPU Frequency Scaling Indicator.
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-indicator\[email protected]: Failed with result 'exit-code'.
Mar 04 19:22:21 Y4M1-II systemd[5515]: app-indicator\[email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:21 Y4M1-II sddm[5129]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Mar 04 19:22:21 Y4M1-II sddm[5129]: Display server stopped.
Mar 04 19:22:21 Y4M1-II acpid[2809]: 1 client rule loaded
Mar 04 19:22:21 Y4M1-II acpid[2809]: client connected from 2784[0:0]
Mar 04 19:22:21 Y4M1-II acpid[2809]: client 2784[0:0] has disconnected
Mar 04 19:22:21 Y4M1-II cpufreqd[2784]: event_wait               : Error polling ACPI Event handler: Interrupted system call
Mar 04 19:22:20 Y4M1-II assert_20230304192220_7.dmp[77859]: Uploading dump (out-of-process)
                                                            /tmp/dumps/assert_20230304192220_7.dmp
Mar 04 19:22:20 Y4M1-II plasmashell[77859]: /tmp/dumps/assert_20230304192220_7.dmp
Mar 04 19:22:20 Y4M1-II plasmashell[77859]: assert_20230304192220_7.dmp[77859]: Uploading dump (out-of-process)
Mar 04 19:22:20 Y4M1-II plasmashell[11897]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[11860]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[56320]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[77065]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[74782]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[14183]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[16321]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[12152]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[76179]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[31400]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[77298]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II plasmashell[17325]: Exiting due to channel error.
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/opus_05_pro
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/opus_05_71
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/opus_05_51
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/opus_05
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink/opus_05
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/faststream_duplex
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/faststream
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/sbc_xq
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink/sbc_xq
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/sbc
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink/sbc
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/aptx
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink/aptx
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/aptx_hd
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink/aptx_hd
Mar 04 19:22:20 Y4M1-II bluetoothd[2702]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource/ldac
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II wireplumber[5527]: dbus[5527]: Attempted to unregister path (path[0] = MediaEndpoint path[1] = A2DPSink) which isn't registered
Mar 04 19:22:20 Y4M1-II systemd-logind[2730]: Session 3 logged out. Waiting for processes to exit.
Mar 04 19:22:20 Y4M1-II sddm[5129]: Display server stopping...
Mar 04 19:22:20 Y4M1-II sddm[5129]: Socket server stopped.
Mar 04 19:22:20 Y4M1-II sddm[5129]: Socket server stopping...
Mar 04 19:22:20 Y4M1-II sddm[5129]: Auth: sddm-helper exited successfully
Mar 04 19:22:20 Y4M1-II sddm-helper[5507]: [PAM] Ended.
Mar 04 19:22:20 Y4M1-II sddm-helper[5507]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 04 19:22:20 Y4M1-II sddm-helper[5507]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Mar 04 19:22:20 Y4M1-II sddm-helper[5507]: pam_unix(sddm:session): session closed for user yamiyuki
Mar 04 19:22:20 Y4M1-II sddm-helper[5507]: [PAM] Closing session
Mar 04 19:22:20 Y4M1-II plasmashell[69988]: src/common/pipes.cpp (883) : Fatal assert; application exiting
Mar 04 19:22:20 Y4M1-II plasmashell[69988]: src/common/pipes.cpp (883) : fatal stalled cross-thread pipe (pipe is disconnected).
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kded.service: Consumed 11.345s CPU time.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KDE Daemon.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kded.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kded.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: app-org.gnome.Rhythmbox3-ee1bce69385c448fb97260121a4b876c.scope: Consumed 3min 39.727s CPU time.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping KDE Plasma Workspace...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped target KDE Plasma Workspace Core.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Virtual filesystem service - digital camera monitor.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Mar 04 19:22:20 Y4M1-II systemd[5515]: gvfs-udisks2-volume-monitor.service: Consumed 1.071s CPU time.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Virtual filesystem service - disk device monitor.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Portal service.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Geoclue Demo agent.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Discord.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-ksystemstats.service: Consumed 52.109s CPU time.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Track hardware statistics.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Consumed 5min 11.363s CPU time.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped OpenRGB.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Powerdevil.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Virtual filesystem service.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Portal service...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping KDE Window Manager...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Track hardware statistics...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Proxies GTK DBus menus to a Plasma readable format.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Virtual filesystem service - disk device monitor...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Virtual filesystem service - digital camera monitor...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Virtual filesystem service...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Accessibility services bus...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Private Internet Access...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping CoreCtrl...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping CPU Frequency Scaling Indicator...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Geoclue Demo agent...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Discord...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Nextcloud...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping OpenRGB...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopping Yakuake...
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped target Startup of XDG autostart applications.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KRunner provider for baloo file indexer.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Xdg Desktop Portal For KDE.
Mar 04 19:22:20 Y4M1-II systemd[5515]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KScreen.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kscreen.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kscreen.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Accessibility.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Consumed 1.414s CPU time.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KDE Connect.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped Handle legacy xembed system tray icons.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-xembedsniproxy.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-xembedsniproxy.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KDE PolicyKit Authentication Agent.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-polkit-agent.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-polkit-agent.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KActivityManager Activity manager Service.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KDE Session Management Server.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-ksmserver.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-ksmserver.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped KDE Global Shortcuts Server.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped target KDE Plasma Workspace.
Mar 04 19:22:20 Y4M1-II systemd[5515]: Stopped target plasma-workspace-x11.target.
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-gmenudbusmenuproxy.service: Failed with result 'exit-code'.
Mar 04 19:22:20 Y4M1-II polkitd(authority=local)[2719]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.73, object path /org/kde/PolicyKit1/Authentic>
Mar 04 19:22:20 Y4M1-II kglobalaccel5[5810]: X connection to :0 broken (explicit kill or server shutdown).
Mar 04 19:22:20 Y4M1-II kglobalaccel5[5810]: The X11 connection broke: I/O error (code 1)
Mar 04 19:22:20 Y4M1-II systemd[5515]: plasma-gmenudbusmenuproxy.service: Main process exited, code=exited, status=1/FAILURE
Mar 04 19:22:20 Y4M1-II pia-client[5984]: [2023-03-05 00:22:20.913][5d4c][default][warning] The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kscreen_backend_launcher[6019]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II plasmashell[5823]:       after 395359 requests (395359 known processed) with 0 events remaining.
Mar 04 19:22:20 Y4M1-II plasmashell[5823]: XIO:  fatal IO error 125 (Operation canceled) on X server ":0"
Mar 04 19:22:20 Y4M1-II plasmashell[5823]: The X11 connection broke: I/O error (code 1)
Mar 04 19:22:20 Y4M1-II xembedsniproxy[5877]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II polkit-kde-authentication-agent-1[5875]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kaccess[5996]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II org_kde_powerdevil[5876]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kded5[5913]: X connection to :0 broken (explicit kill or server shutdown).
Mar 04 19:22:20 Y4M1-II ksmserver[5795]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kdeconnectd[5983]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kwin_x11[5800]: file:///usr/share/kwin/outline/plasma/outline.qml:14: TypeError: Cannot read property 'longDuration' of null
Mar 04 19:22:20 Y4M1-II kwin_x11[5800]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kactivitymanagerd[5872]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II gmenudbusmenuproxy[5874]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kglobalaccel5[5810]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II corectrl[5981]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II yakuake[5959]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II at-spi-bus-launcher[6183]: X connection to :0 broken (explicit kill or server shutdown).
Mar 04 19:22:20 Y4M1-II openrgb[5960]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II plasmashell[67841]: Fatal IO error 10 (No child processes) on X server :0.
Mar 04 19:22:20 Y4M1-II baloorunner[11368]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II env[6703]: X connection to :0 broken (explicit kill or server shutdown).
Mar 04 19:22:20 Y4M1-II kded5[5797]: X connection to :0 broken (explicit kill or server shutdown).
Mar 04 19:22:20 Y4M1-II kded5[5797]: The X11 connection broke: I/O error (code 1)
Mar 04 19:22:20 Y4M1-II bitwarden[6063]: bitwarden: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 04 19:22:20 Y4M1-II xdg-desktop-portal-kde[7069]: The X11 connection broke (error 1). Did the X11 server die?
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Mar 04 19:22:20 Y4M1-II plasmashell[11376]: [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Mar 04 19:22:20 Y4M1-II plasmashell[5823]: amdgpu: amdgpu_cs_query_fence_status failed.
Mar 04 19:22:20 Y4M1-II plasmashell[11376]: amdgpu: amdgpu_cs_query_fence_status failed.
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GPU reset(2) succeeded!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: [drm] Skip scheduling IBs!
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: recover vram bo from shadow done
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: recover vram bo from shadow start
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Mar 04 19:22:20 Y4M1-II kernel: [drm] JPEG decode initialized successfully.
Mar 04 19:22:20 Y4M1-II kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Mar 04 19:22:20 Y4M1-II kernel: [drm] kiq ring mec 2 pipe 1 q 0
Mar 04 19:22:20 Y4M1-II kernel: [drm] DMUB hardware initialized: version=0x02020013
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: SMU is resumed successfully!
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: use vbios provided pptable
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: SMU driver if version not matched
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5400 (58.>
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: SMU is resuming...
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Mar 04 19:22:20 Y4M1-II kernel: [drm] reserve 0xa00000 from 0x83fd000000 for PSP TMR
Mar 04 19:22:20 Y4M1-II kernel: [drm] PSP is resuming...
Mar 04 19:22:20 Y4M1-II kernel: [drm] VRAM is lost due to GPU reset!
Mar 04 19:22:20 Y4M1-II kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000800000).
Mar 04 19:22:20 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GPU reset succeeded, trying to resume
Mar 04 19:22:19 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GPU smu mode1 reset
Mar 04 19:22:19 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GPU mode1 reset
Mar 04 19:22:19 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: MODE1 reset
Mar 04 19:22:19 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: free PSP TMR buffer
Mar 04 19:22:19 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GPU reset begin!
Mar 04 19:22:19 Y4M1-II kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 69855 thread HogwartsLegacy. pid 69977
Mar 04 19:22:19 Y4M1-II kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=19032271, emitted seq=19032273
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          RW: 0x0
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          MAPPING_ERROR: 0x0
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          WALKER_ERROR: 0x0
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          MORE_FAULTS: 0x0
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x000080006a9ca000 from client 0x1b (UTCL2)
Mar 04 19:22:08 Y4M1-II kernel: amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32790, for process HogwartsLegacy. pid 69855 thread HogwartsLe>
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "playlist-add-to-new" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "playlist-add-to" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-trash" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-select-none" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-select-all" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-properties" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-paste" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-delete" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-cut" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-copy" which didn't change it
Mar 04 19:21:46 Y4M1-II gmenudbusmenuproxy[5874]: kde.dbusmenuproxy: Got enabled change for action "clipboard-add-to-queue" which didn't change it
Mar 04 19:21:46 Y4M1-II rhythmbox[68638]: Failed to send notification (Karma): GDBus.Error:org.freedesktop.Notifications.Error.ExcessNotificationGeneration: Created too many >
Mar 04 19:21:46 Y4M1-II rhythmbox[68638]: Failed to send notification (Karma): GDBus.Error:org.freedesktop.Notifications.Error.ExcessNotificationGeneration: Created too many >
Mar 04 19:21:07 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: SGDT instruction cannot be used by applications.
Mar 04 19:21:00 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: For now, expensive software emulation returns the result.
Mar 04 19:21:00 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: SGDT instruction cannot be used by applications.
Mar 04 19:20:55 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: For now, expensive software emulation returns the result.
Mar 04 19:20:55 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: SGDT instruction cannot be used by applications.
Mar 04 19:20:55 Y4M1-II kernel: umip_printk: 49 callbacks suppressed
Mar 04 19:19:09 Y4M1-II kernel: umip: HogwartsLegacy.[70050] ip:1516d1d15 sp:1781bf090: SGDT instruction cannot be used by applications.
Mar 04 19:19:00 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: For now, expensive software emulation returns the result.
Mar 04 19:19:00 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: SGDT instruction cannot be used by applications.
Mar 04 19:18:53 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: For now, expensive software emulation returns the result.
Mar 04 19:18:53 Y4M1-II kernel: umip: HogwartsLegacy.[69855] ip:14fa4f834 sp:b95e00: SGDT instruction cannot be used by applications.
Mar 04 19:18:53 Y4M1-II kernel: umip_printk: 85 callbacks suppressed

Confirmed increasing max_map_count fixed flue travel crash issue. Kubuntu 22.04, AMD 6800XT/16GB, 32GB system RAM. Instead of setting it permanently I run sudo sysctl -w vm.max_map_count=1000000 before playing which sets it until next reboot. None of the launch options suggested made any difference that I could detect.

Question:

Would it be useful to issue another report for NVIDIA based cards?

Most of the suggestions here are useless to me since they're suggesting fixes for AMD cards.

Game is playable on my RTX3080 but has serious FPS drops in-between.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1454737939

Can confirm. I have the same issue with Proton Experimental [bleeding edge] and Proton-GE-49

Anyone else getting weird flickering square-ish artifacts in raytraced reflections? This is happening on my Nvidia 3090 with Proton Experimental running on Arch.

Also, can confirm as well that the max_map_count fix has made the game way more stable. Is it recommended to permanently set this value? Are there any downsides? Wondering if I should just continue to manually set it each time before I run the game.

@urbenlegend Are you able to post a screenshot? :slightly_smiling_face:

@Blisto91 It's easier to describe with video: https://imgur.com/a/Nwmuo58

In dark areas where there's only small reflective areas, it looks really sparkly. In mirrors, you can see that the flickering is coming from these weird blocky glitches.

The game stopped loading for me. It launches fine with same parameters I used previously but all I see is a black screen and hear background music but the "loading shaders" bar doesn't appear or anything else. Alt-tabbing out prevents me from entering the game again. Anyone else have this issue?

I am on Arch linux on a nvidia2060 laptop

The game stopped loading for me. It launches fine with same parameters I used previously but all I see is a black screen and hear background music but the "loading shaders" bar doesn't appear or anything else. Alt-tabbing out prevents me from entering the game again. Anyone else have this issue?

I am on Arch linux on a nvidia2060 laptop

I found that I got the game working again by changing my screen res to something small, Launching the game and getting it all working, Then exiting out and putting the res back (Im not sure why this worked for me), Not sure If I messed something up in the graphics settings with Ray tracing

What I found makes the crash 100% of the times just after the first cutscene is enabling steam input. If I play with keyboard and mouse, the games works fine. If I use my PS4 controller using steam input, it crashes all the time.
Sorry, actually, strangely enough the game stops crashing when I enable PROTON_LOG=1 in the launch settings.

Anyone else getting weird flickering square-ish artifacts in raytraced reflections? This is happening on my Nvidia 3090 with Proton Experimental running on Arch.

Also, can confirm as well that the max_map_count fix has made the game way more stable. Is it recommended to permanently set this value? Are there any downsides? Wondering if I should just continue to manually set it each time before I run the game.

The only downside to increasing permanently is that you are allowing any program to use more resources before it gets killed. So some buggy program might use more resources instead of just crashing. Very unlikely to be a problem at all. Source: https://archive.is/xyaA6

Unrelated: after this mmap fix I did see another crash, but it was different. During play the game suddenly slowed dramatically then all of Ubuntu restarted to a fresh session. This might have been related to me setting the graphics to "ultra", I now set them back to "recommended" :)

A recent updated made all textures blurry, no matter what settings I have setup.

I'm reverting back to the previous update for now.

Using just the map_count fix did not help in solving the crashes when loading or fast traveling. in my case. I checked the game process with top, and realized the game was using more than 50gb VIRT memory, which I guess is related to the memory leak that the map_count fix is trying to address. However, having enabled a small swap partition (only 4gb) made the above fix useless. After increasing the swap to 32gb, the game does not crash anymore while loading.

The game was previously stuck on screen with "Warnings" and would not show shader loading screen, instead showing a black background with background music playing.

I got it to work with the following commands PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 PROTON_HIDE_NVIDIA_GPU=0 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json gamemoderun %command% -dx12

However this no longer works and I am getting same problem on every proton version.

Whatever I try, I'm completely unable to get the game to run. Tried setting the Map Limit to 16777216 and even the 1000000 recommended in this thread.
Tried with Proton 7.0.6 and GE-53 as well as Experimental.

Only thing I've get is a Black Screen without music, before the game crashes after about 10 seconds.

steam-990080.log

@Severus157 i see you have either amdvlk or amd pro vulkan drivers installed. They are known not to work too well with vkd3d-proton. radv (mesa vulkan) is recommended

I had the black screen error after updating to latest nvidia + kernel. The epilepsy warning came, but afterwards a black screen showed up. I've deleted the Proton Cache in steamapps/common/Hogwarts Legacy/Phoenix/Binaries/Win64/ and just started the game with only the parameters PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11.
It was again a black screen, but the shaders were (slowly) generated again in this folder.
After around 10-15min black screen idling, the vk3d-proton.cache.write file reached 12,3MB and Hogwarts Legacy began to load properly.

@Blisto91

@Severus157 i see you have either amdvlk or amd pro vulkan drivers installed. They are known not to work too well with vkd3d-proton. radv (mesa vulkan) is recommended

Thank you for the tipp. Though I still have the same problem only that I sometimes not even get the Black Screen.
I've installed vulcan-radeon and set the Environment Variables in /etc/environment according to Arch Wiki.

DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam

Here's the new Log:
steam-990080.log

Did I do something wrong?

Edit:
Steam System Information Gist

Hello @Severus157, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Here is the Gist
Gist also included in Post above.

It's suggesting you don't have 64bit radv installed. At least not in that location

It's suggesting you don't have 64bit radv installed. At least not in that location

Thanks, looks like VK_ICD_FILENAMES is malformed (https://gist.github.com/Severus157/0d17835dff16068a52872c9a5513005a#file-gistfile1-txt-L712)

How can I fix this?
My cli output looks fine as far as I can see?

[svenja@svenja-arch icd.d]$ pwd
/usr/share/vulkan/icd.d
[svenja@svenja-arch icd.d]$ ls -la
total 24
drwxr-xr-x 2 root root 4096 Mär 26 15:19 .
drwxr-xr-x 5 root root 4096 Jan  2  2022 ..
-rwxr-xr-x 1 root root  615 Jan  2 18:37 amd_icd32.json
-rwxr-xr-x 1 root root  611 Jan  2 18:27 amd_icd64.json
-rw-r--r-- 1 root root  149 Mär 18 01:58 radeon_icd.i686.json
-rw-r--r-- 1 root root  147 Mär 18 01:58 radeon_icd.x86_64.json
[svenja@svenja-arch icd.d]$ cat radeon_icd.x86_64.json 
{
    "ICD": {
        "api_version": "1.3.238",
        "library_path": "/usr/lib/libvulkan_radeon.so"
    },
    "file_format_version": "1.0.0"
}[svenja@svenja-arch icd.d]$ cd /usr/lib/
[svenja@svenja-arch lib]$ ls -la | grep libvulkan
-rwxr-xr-x   1 root root   9303272 Mär 18 01:58 libvulkan_radeon.so
lrwxrwxrwx   1 root root        14 Jan 29 15:34 libvulkan.so -> libvulkan.so.1
lrwxrwxrwx   1 root root        20 Jan 29 15:34 libvulkan.so.1 -> libvulkan.so.1.3.240
-rwxr-xr-x   1 root root    477112 Jan 29 15:34 libvulkan.so.1.3.240
[svenja@svenja-arch lib]$ cat /etc/environment 
#
# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
# QT_QPA_PLATFORMTHEME=qt5ct
BROWSER=firefox
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam

Or is it a permission problem on the json files? How should the permissions look like?

VK_ICD_FILENAMES is a colon separate list and the second entry is being parsed as /usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam with the space not separating the noise at the end of the variable.

Hmm... Okay weird. Than it looks like the environment variable I used for being able to use the vulkan-radeon package is somehow wrong...

I've used the direct information from archwiki to set them and copied the variable completely.

Do you need the other drivers? If you don't it's easier if they were just removed.

Do you need the other drivers? If you don't it's easier if they were just removed.

Had that mainly for better Performance on Star Citizen, when I played it. But I've just uninstalled amdvlk for testing, removed the Environment Variables and rebooted.
Unfortunately still not working. Hogwarts Legacy doesn't want to start, not getting any Screen at all.

New SteamInformation

New Log:
steam-990080.log

Vulkaninfo:

[svenja@svenja-arch ~]$ vulkaninfo --summary
==========
VULKANINFO
==========

Vulkan Instance Version: 1.3.240


Instance Extensions: count = 21
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 4
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6

Instance Layers: count = 8
--------------------------
VK_LAYER_AMD_switchable_graphics_32 AMD switchable graphics layer 1.3.235  version 1
VK_LAYER_INTEL_nullhw               INTEL NULL HW                 1.1.73   version 1
VK_LAYER_MESA_device_select         Linux device selection layer  1.3.211  version 1
VK_LAYER_MESA_overlay               Mesa Overlay layer            1.3.211  version 1
VK_LAYER_VALVE_steam_fossilize_32   Steam Pipeline Caching Layer  1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64   Steam Pipeline Caching Layer  1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32     Steam Overlay Layer           1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64     Steam Overlay Layer           1.3.207  version 1

Devices:
========
GPU0:
        apiVersion         = 1.3.238
        driverVersion      = 23.0.0
        vendorID           = 0x1002
        deviceID           = 0x731f
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon RX 5700 XT (RADV NAVI10)
        driverID           = DRIVER_ID_MESA_RADV
        driverName         = radv
        driverInfo         = Mesa 23.0.0
        conformanceVersion = 1.2.7.1
        deviceUUID         = 00000000-0b00-0000-0000-000000000000
        driverUUID         = 414d442d-4d45-5341-2d44-525600000000

VK_ICD_FILENAMES is a colon separate list and the second entry is being parsed as /usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam with the space not separating the noise at the end of the variable.

Hmm... Okay weird. Than it looks like the environment variable I used for being able to use the vulkan-radeon package is somehow wrong...

I've used the direct information from archwiki to set them and copied the variable completely.

You misunderstood the article. That was meant to launch Steam with RADV. When you declare the variable, you aren't supposed to put the "steam" part.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1484138599

Thanks. But I've completely removed the Variables now and even removed amdvlk. So shouldn't be an issue anymore.

You still have 32bit amdvlk installed

You still have 32bit amdvlk installed

Damn... Forgotten that part.
But even after uninstall and reboot, no change. Game will not start.

• Verified Game Files, resetted Proton Prefix.
  I really don't know what's wrong anymore. This is crazy.
  I'm going to completely reinstall the Game. Hopefully this will help somewhat. Will take about 10 hours, but well...

Thank you though.

Gist
After playing Legacy on Steam deck for a while (Everything working fine) I'm back on my Linux Machine. However now and the last few days I only get the following message

What I have tried:

• Reinstalled the game completely
• Different proton versions:
  • Experimental
  • 7.0-6
  • GE Proton 7-52
• Removed the pfx folder and verified the files.

Thanks

@MichaelAllenHardeman I have been told that might be an esync "issue" (maybe not a issue with esync itself per say, but can trigger it when a low fd limit is set). You could try launching with PROTON_NO_ESYNC=1 %command% and see if that helps? CPU performance might decrease tho. People with kernel 5.16+ use fsync by default instead.

This solved my issue also on pop os 22.04, nvidia 3090 with driver version 530

The new game patch today seems to have addressed a bunch of issues I had with raytracing. It no longer has any weird artifacts and the performance has improved.

Still needs that vm.max_map_count change though.

There is a wine patch that is needed in order to get the game to work with Anv (Intel's Vulkan driver on Linux):
https://gitlab.winehq.org/wine/wine/-/commit/4fab9ff230f497499da223ade9bbe3633a657f05

Would like to request that this gets backported to Proton (or if Proton gets rebased to 8.6 release that should also include it) in order to unblock this.

According to the original bug report on Wine, it should also help with an Unreal Engine 5.1 demo (Matrix Awakens) and possibly other apps.

See also https://github.com/ValveSoftware/Proton/issues/2927#issuecomment-1537547199

mai 16 20:21:22 kthx kernel: umip_printk: 19 callbacks suppressed
mai 16 20:21:22 kthx kernel: umip: HogwartsLegacy.[32290] ip:152a000a3 sp:b9e3c8: SGDT instruction cannot be used by applications.
mai 16 20:21:22 kthx kernel: umip: HogwartsLegacy.[32290] ip:152a000a3 sp:b9e3c8: For now, expensive software emulation returns the result.
mai 16 20:21:31 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: SGDT instruction cannot be used by applications.
mai 16 20:21:31 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: For now, expensive software emulation returns the result.
mai 16 20:21:31 kthx kernel: umip: HogwartsLegacy.[32290] ip:152a000a3 sp:b9e3c8: SGDT instruction cannot be used by applications.
mai 16 20:22:48 kthx NetworkManager[1009]: <info>  [1684261368.6539] dhcp4 (enp5s0): state changed new lease, address=192.168.1.112
mai 16 20:24:24 kthx kernel: umip_printk: 29 callbacks suppressed
mai 16 20:24:24 kthx kernel: umip: HogwartsLegacy.[32290] ip:14f60b9a4 sp:b9e890: SGDT instruction cannot be used by applications.
mai 16 20:24:24 kthx kernel: umip: HogwartsLegacy.[32290] ip:14f60b9a4 sp:b9e890: For now, expensive software emulation returns the result.
mai 16 20:24:24 kthx kernel: umip: HogwartsLegacy.[32290] ip:152a000a3 sp:b9e3c8: SGDT instruction cannot be used by applications.
mai 16 20:24:24 kthx kernel: umip: HogwartsLegacy.[32290] ip:152a000a3 sp:b9e3c8: For now, expensive software emulation returns the result.
mai 16 20:24:40 kthx kernel: umip: HogwartsLegacy.[32290] ip:1593ff28d sp:b9d6d8: SGDT instruction cannot be used by applications.
mai 16 20:25:01 kthx CRON[33725]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
mai 16 20:25:01 kthx CRON[33726]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
mai 16 20:25:01 kthx CRON[33725]: pam_unix(cron:session): session closed for user root
mai 16 20:26:30 kthx kernel: umip_printk: 118 callbacks suppressed
mai 16 20:26:30 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: SGDT instruction cannot be used by applications.
mai 16 20:26:30 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: For now, expensive software emulation returns the result.
mai 16 20:26:31 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: SGDT instruction cannot be used by applications.
mai 16 20:26:31 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: For now, expensive software emulation returns the result.
mai 16 20:26:31 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: SGDT instruction cannot be used by applications.
mai 16 20:28:50 kthx kernel: umip_printk: 21 callbacks suppressed
mai 16 20:28:50 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: SGDT instruction cannot be used by applications.
mai 16 20:28:50 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: For now, expensive software emulation returns the result.
mai 16 20:29:04 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: SGDT instruction cannot be used by applications.
mai 16 20:29:04 kthx kernel: umip: HogwartsLegacy.[32290] ip:15766a9a1 sp:b9cc50: For now, expensive software emulation returns the result.
mai 16 20:29:04 kthx kernel: umip: HogwartsLegacy.[32290] ip:159456571 sp:b9ce78: SGDT instruction cannot be used by applications.

journal is absolutely spammed by this.

Game is currently crashing for me after the initial seziure warning message, with a dialog "Ran out of video memory".

Arch - 6.4.1
Nvidia 4090: 535.54.03
Proton Experimental

Proton log

Every time game crashed with error "out of video memory trying to allocate a rendering resource..."

Every time game crashed with error "out of video memory trying to allocate a rendering resource..."

I had this too: https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1445152064
It was random when I had this message (AMD Radeon here) or game was stable or AMD driver crashed.

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1427138732

I haven't touched the game in a while, but anyone else still gets this issue?

I'm playing it now with a 6950XT with no problems, but I am wondering if there's a way to get RT enabled currently its greyed out in the menu.

VKD3D_CONFIG=dxr %command% if using mesa 23.2.0 (which doesn't have a stable release yet) or above.
Below mesa 23.2.0 you will need a extra env var, but i recommend not trying that as the game will either crash (and maybe also on startup afterwards) or leak memory heavily. 23.2.0 and above should be fine afaik.

I'm playing it now with a 6950XT with no problems

are you still using specific launch configs?

I'm playing it now with a 6950XT with no problems

are you still using specific launch configs?

Edit: I recently upgraded to this card I previously had a 6700XT and also had no problems playing it on there also with no configuration.

No, It's working out of the box as in I just installed it and hit play on Steam.

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: TUF GAMING X570-PLUS (WI-FI)
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 5800X 8-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4850 MHz
16 logical processors
8 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Freedesktop.org SDK 22.08 (Flatpak runtime) (64 bit)
Kernel Name: Linux
Kernel Version: 6.4.12-100.fc37.x86_64
X Server Vendor: The X.Org Foundation
X Server Release: 12201009
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20230606.51628
Video Card:
Driver: AMD AMD Radeon RX 6950 XT (navi21, LLVM 15.0.7, DRM 3.52, 6.4.12-100.fc37.x86_64)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.4 (git-8b0202e4b4)
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x73a5
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 23.62" x 13.39" (27.13" diag), 60.0cm x 34.0cm (68.9cm diag)
Primary VRAM: 16384 MB
Sound card:
Audio device: USB Mixer
Memory:
RAM: 64194 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 952228 MB
Largest Free Hard Disk Block: 119649 MB
Storage:
Number of SSDs: 2
SSD sizes: 1000G,512G
Number of HDDs: 0
Number of removable drives: 0

No, It's working out of the box as in I just installed it and hit play on Steam.

Why was this needed: VKD3D_CONFIG=pipeline_library_app_cache?

Why was this needed: VKD3D_CONFIG=pipeline_library_app_cache?

To prevent two caches I guess (game has it's own cache). From docs:

VKD3D_CONFIG=pipeline_library_app_cache is an alternative to VKD3D_SHADER_CACHE_PATH=0 and can be automatically enabled based on app-profiles if relevant in the future if applications manage the caches better than vkd3d-proton can do automagically.

Ray tracing with Mesa 23.2.0 (69f5c51b2d2), RX 6900 XT, Proton-experimental:

@zaps166 Weird, I can't seem to reproduce this on my end. Do you encounter this right during the shader compilation at startup or somewhere else in the game? Also, do you have any special environment variables or launch options set besides VKD3D_CONFIG=dxr?

@pixelcluster Only VKD3D_CONFIG=dxr is set. It asserts when loading a map, menu is working. VKD3D_SHADER_CACHE_PATH=0 and/or deleting game shader cache doesn't make any difference.

Could you post a Proton log where the crash happens?

@zaps166 If you can get to the main menu, but not load into any game, I guess the crash might be specific to certain areas of the game. Which area are you in in the save that you're trying to load?

Right, depends on location. Newly created character is working.

I'm here:

Logs (please remove .txt suffix): steam-990080.log.zst

New tests:

• I can create a new character and start game with RT,
• performance seems about 50% lower comparing to Windows on the same graphics settings - e.g. 33 FPS Windows, 22 FPS Linux (2880x1620, all settings to High),
• I can't load any game save including new game save (assert),

I reproduced the issue, looking into it now. Thanks for reporting!

~1.5h gameplay, Proton-Experimental (experimental-8.0-20230907), Mesa 23.2 (cc3aad2a9fb761a242174f414a0b1e07b03e2b36), Kernel 6.5.2, RX 6900XT, full GPU reset - login screen:

[11272.163466] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32781, for process HogwartsLegacy. pid 37076 thread HogwartsLe:cs0 pid 37209)
[11272.163471] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000233fb000 from client 0x1b (UTCL2)
[11272.163473] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
[11272.163474] amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: SQC (data) (0xa)
[11272.163475] amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[11272.163476] amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[11272.163476] amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[11272.163477] amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[11272.163477] amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[11282.319564] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3648516, emitted seq=3648518
[11282.319738] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 37076 thread HogwartsLe:cs0 pid 37209
11282.319875] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[11282.610227] amdgpu 0000:03:00.0: amdgpu: MODE1 reset
[11282.610230] amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
[11282.610278] amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
[11283.136568] amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
[11283.136726] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
[11283.136784] [drm] VRAM is lost due to GPU reset!
[11283.136792] [drm] PSP is resuming...
[11283.215962] [drm] reserve 0xa00000 from 0x83fd000000 for PSP TMR
[11283.352994] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[11283.352997] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[11283.352999] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5800 (58.88.0)
[11283.353000] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[11283.353032] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
[11283.428346] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[11283.429605] [drm] DMUB hardware initialized: version=0x0202001E
[11283.574387] [drm] kiq ring mec 2 pipe 1 q 0
[11283.581525] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[11283.582131] [drm] JPEG decode initialized successfully.
[11283.582150] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[11283.582151] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[11283.582152] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[11283.582152] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[11283.582152] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[11283.582153] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[11283.582153] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[11283.582154] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[11283.582154] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[11283.582154] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[11283.582155] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[11283.582155] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[11283.582156] amdgpu 0000:03:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0
[11283.582156] amdgpu 0000:03:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0
[11283.582156] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[11283.582157] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[11283.582157] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[11283.582158] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
[11283.582158] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
[11283.582158] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
[11283.582159] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
[11283.589481] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start
[11283.618022] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done
[11283.618030] amdgpu 0000:03:00.0: amdgpu: GPU reset(2) succeeded!

@zaps166 Hi there. Is this with or without Ray Tracing turned on?

@zaps166 Hi there. Is this with or without Ray Tracing turned on?

Hi! 2880x1620 with High/Ultra mixed settings without RT.

I don' think the pagefault is related to the unstable mesa, because I had this problem many times in the past on various kernel/mesa versions.

Today same after ~1.5h:

[ 9751.934956] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32783, for process HogwartsLegacy. pid 11363 thread HogwartsLe:cs0 pid 11491)
[ 9751.934963] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000227f7000 from client 0x1b (UTCL2)
[ 9751.934965] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201430
[ 9751.934966] amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: SQC (data) (0xa)
[ 9751.934967] amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[ 9751.934968] amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[ 9751.934968] amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[ 9751.934969] amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[ 9751.934970] amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[ 9761.956618] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

this time soft recovered and game crash after long freeze.

Is it vkd3d or game or mesa bug?

Today no amdgpu pagefault (kernel 6.5.3).

I found a strange regression in Proton 8 / Experimental: when I close game (Hogwarts Legacy or some other games) the mouse is grabbed into a game (I'm on Xorg) and I can't use mouse while game is closing (when window is already closed, but process is still running or when alt-tab while game is closing).

When game freezes, mouse is inaccessible and I have to kill process using keyboard to get the mouse back. This problem doesn't exist on Proton 7.0-6.

@zaps166 It is interesting that you are reporting this behavior on both Proton 8.0-3 and Experimental. I found a regression that behaves exactly like you are describing in experimental, but the blamed commit is only in experimental and I do not see the issue on 8.0-3 (or 8.0-4-rc). Could you please re-try Proton 8.0-3/4 to double check that you are seeing this on stable? Could you also please try this build and see if it fixes the issue? Build uploaded here: https://www.codeweavers.com/xfer/alasky/cursor-revert/ with lock code "revert". Thank you for the report!

@alasky17 Oops, maybe I checked different proton and I thought it's 8.0 :sweat_smile: My mistake, sorry. Proton 8.0-3 and 8.0-4-rc are OK.

I'm downloading the cursor-revert, but I noticed bleeding-edge returns cursor much earlier like experimental.

cursor-revert build was ok, but game started without my saves!

@zaps166 Thank you for testing! That is quite strange, as it should have been very similar to experimental-8.0-20230907. Hopefully you got them back? It sounds like you are indeed running into the same regression as me -- it is under investigation :)

That is quite strange, as it should have been very similar to experimental-8.0-20230907

Maybe it's random how long the cursor is grabbed after closing game, now tested and it was same as in proton-experimental. Sometimes cursor is back when process is closed, sometimes a bit earlier. Hard to test - let's say - it's the same :smile:

Hopefully you got them back

Yes, saves are back :smile:

@alasky17 Found another regression, affects many games, not only Hogwarts Legacy. When I disconnect or turn off the monitor and connect or turn on again, game freezes and needs to be killed. Happens to me on Proton-Experimental and Proton 8.0-3, but works properly on Proton 7.0-6. RADV driver, Xfwm4 and Openbox WMs.
On Proton-Experimental on some games cursor is grabbed and I have to kill processes manually on keyboard, because can't click "Stop" on Steam (btw. when we can expect the cursor-revert fix in bleeding edge? :smile_cat: ?).

Logs (remove .txt suffix and unpack): steam-990080.log.zst.txt

@kisak-valve Hi, thanks for investigation!

I can't get this game to run for more than a few hours.

• It crashes with "Error out of video memory trying to allocate a rendering resource" on Experimental.
  • Multiple of those messages usually pop up at once
  • The game usually keeps running and i can even walk around, but it finally freezes and crashes when i open the map
• I'm getting segfaults on stable 8.0-4
  • EDIT: also getting ouf of memory on stable 8.0-4

8.0-4 segfault

[ 5424.258522] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32780, for process HogwartsLegacy. pid 30774 thread HogwartsLe:cs0 pid 30937)
[ 5424.258530] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x00008000244e2000 from client 0x1b (UTCL2)
[ 5424.258533] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101430
[ 5424.258535] amdgpu 0000:2f:00.0: amdgpu: 	 Faulty UTCL2 client ID: SQC (data) (0xa)
[ 5424.258537] amdgpu 0000:2f:00.0: amdgpu: 	 MORE_FAULTS: 0x0
[ 5424.258538] amdgpu 0000:2f:00.0: amdgpu: 	 WALKER_ERROR: 0x0
[ 5424.258539] amdgpu 0000:2f:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x3
[ 5424.258540] amdgpu 0000:2f:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
[ 5424.258542] amdgpu 0000:2f:00.0: amdgpu: 	 RW: 0x0
[ 5434.356531] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=1808632, emitted seq=1808634
[ 5434.356746] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 30774 thread HogwartsLe:cs0 pid 30937
[ 5434.356929] amdgpu 0000:2f:00.0: amdgpu: GPU reset begin!
[ 5434.600010] amdgpu 0000:2f:00.0: amdgpu: MODE1 reset
[ 5434.600014] amdgpu 0000:2f:00.0: amdgpu: GPU mode1 reset
[ 5434.600077] amdgpu 0000:2f:00.0: amdgpu: GPU smu mode1 reset
[ 5435.119945] amdgpu 0000:2f:00.0: amdgpu: GPU reset succeeded, trying to resume

gpu crash, had to reboot system. Recovery wasn't very clean. Got a lot of segfaults in other apps after it.

Specs

In short: Arch linux, wayland, RX6900, Ryzen 5950X, 64GiB Memory

Computer Information:
Manufacturer: Micro-Star International Co., Ltd.
Model: X570-A PRO (MS-7C37)
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 9 5950X 16-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 5084 MHz
32 logical processors
16 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.5.5-arch1-1
X Server Vendor: The X.Org Foundation
X Server Release: 12302001
X Window Manager: GNOME Shell
Steam Runtime Version: <Runtime disabled>
Video Card:
Driver: AMD AMD Radeon RX 6900 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.5-arch1-1)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.2.1-arch1.2
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x73bf
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 24.02" x 13.78" (27.68" diag), 61.0cm x 35.0cm (70.3cm diag)
Primary VRAM: 16384 MB
Sound card:
Audio device: USB Mixer
Memory:
RAM: 64222 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 938195 MB
Largest Free Hard Disk Block: 20791 MB
Storage:
Number of SSDs: 4
SSD sizes: 1000G,1000G,1000G,240G
Number of HDDs: 0
Number of removable drives: 0

It used to work flawlessly with increasing the vm.max_map_count a month ago or so. But now it crashes after just a few (~10) minutes of playing. I tried it with and without esync. The logs do not list any errors. Does somebody have an idea what could be the cause of it?

steam-990080.txt.zip

Computer Information:
Manufacturer: ASRock
Model: B650 PG Lightning
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 9 7900X 12-Core Processor
CPU Family: 0x19
CPU Model: 0x61
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5733 MHz
24 logical processors
12 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Fedora Linux 38 (Workstation Edition) (64 bit)
Kernel Name: Linux
Kernel Version: 6.5.7-200.fc38.x86_64
X Server Vendor: The X.Org Foundation
X Server Release: 12014000
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20230801.56012
Video Card:
Driver: AMD AMD Radeon Graphics (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.7-200.fc38.x86_64)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.8
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 74 Hz
VendorID: 0x1002
DeviceID: 0x744c
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 4480 x 1440
Primary Display Size: 28.54" x 16.85" (33.11" diag), 72.5cm x 42.8cm (84.1cm diag)
Primary VRAM: 20480 MB
Sound card:
Audio device: USB Mixer
Memory:
RAM: 31783 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 1906104 MB
Largest Free Hard Disk Block: 1156001 MB
Storage:
Number of SSDs: 2
SSD sizes: 2000G,960G
Number of HDDs: 0
Number of removable drives: 0

Replying to https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1779207512

It's probably, the AMD GPU, I had similar issues with it continuously crashing with no support or fix in sight and it was something in the drivers, it probably worked for a while on a driver update and they borked it again most likely with a newer GPU update.

I found it quite amusing/annoying that i specially bought a AMD card because everyone said it's the best on/for Linux but it was a mistake because this game works fine on a NVIDIA card. But i basically gave up on the game on Linux. That said I have no issues on other games so it's not so bad, just a bit of a splinter.

I also had GPU crashes sometimes (not often), but I was able to complete the game on Linux. Usually after clearing caches it worked more stable. Maybe try this:

1. Remove all shader caches:

• game (~/.local/share/Steam/steamapps/compatdata/990080/pfx/drive_c/ProgramData/Hogwarts Legacy/*)
• mesa (~/.cache/mesa_shader_cache/*)
• vkd3d-proton [if exists] (~/.local/share/Steam/steamapps/common/Hogwarts Legacy/Phoenix/Binaries/Win64/vkd3d-proton.cache.write)

1. Update Mesa to 23.1.9 (maybe not 23.2.1).
2. Start game with VKD3D_CONFIG=pipeline_library_app_cache %command% or VKD3D_SHADER_CACHE_PATH=0 %command% - this prevents generating another shader cache (vkd3d-proton.cache.write).

Btw. I have disabled shader pre-caching (in Steam->Settings->Downloads).

Also for all users who don't know yet - don't forget to set vm.max_map_count to high value (see https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1422699309).

Hogwarts Legacy crashes after epilepsy warning and company logos on a brand new Steam Deck 1TB OLED. Other games run fine. Logs attached.
steam.log

I don't have crash after epilepsy warning. The game is running on RX 6900 XT and proton experimental-8.0-20231129, also raytracing is working (with lower performance than on Windows). I use Mesa 23.3.0 and Linux 6.6.3.

When I use raytracing in game I noticed GPU crash after changing rendering resolution e.g. from 1280x720 to 1920x1080 or changing scaling to XeSS and going back from menu to game (in this case, fortunately soft recover only, but game will crash soon after):

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32780, for process HogwartsLegacy. pid 5213 thread HogwartsLe:cs0 pid 5345)
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000e27e1000 from client 0x1b (UTCL2)
amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:03:00.0: amdgpu: 	 Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:03:00.0: amdgpu: 	 MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 WALKER_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 PERMISSION_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 MAPPING_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu: 	 RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Similar behavior on Windows when I do the same things - game crashes.

Maybe this can help developers (vkd3d-proton / Mesa) fix the occasional GPU crashes without raytracing, too. Even if it's a game bug, GPU must not fully reset and crash the entire user session...

Had NVidia 525 on here with Proton 8. It crashed whenever I fast travelled.

Now trying NVidia 535 with Proton 8. Vulkan shaders compiled for an age, now this popup (which breaks streaming, and seems to be AMD-related, even though I use NVidia):

AND it compiles shaders when starting the game - it must really like compiling shaders:

After all that, the game still loads as before, but on the first fast travel, it crashes.

$ ulimit -Sn
1024
$ ulimit -Hn
1048576

What fixed it for me in the end was:

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/sysctl.conf
This change should kick in after a reboot or if you run sudo sysctl -p

I'm also having issues on the nvidia side with proton 8, 7 and experimental.

Sometimes the error of this comment https://github.com/ValveSoftware/Proton/issues/6510#issuecomment-1859261305 also shows up in my 4060TI

But the main one I've been getting is this one:

Usually, the dlss option also does not appear and on either of the options the game lasts a whole 5 minutes of gameplay

When dlss does show up, it lasts about 50 minutes to an hour.

Other information:

The lack of memory error will only go away when I switch proton versions.

Shaders take around 3 minutes to compile

Already have the vm.max_map_count set to 1000000

$cat /proc/sys/vm/max_map_count
1000000

Sometimes when the game crashes this message goes to my clipboard, I only noticed this because of kde connect sending it to my phone:

LowLevelFatalError [File:Unknown] [Line: 1210] GameThread timed out waiting for RenderThread after 120.00 secs

$ulimit -Hn 
1048576

$ulimit -Sn 
1024

Log file:
steam-990080.zip

dmesg gives me this info as well:

[ 3674.559110] NVRM: GPU at PCI:0000:10:00: GPU-03d22a31-1390-9aa1-3aee-7e48f3c5cba1
[ 3674.559124] NVRM: Xid (PCI:0000:10:00): 32, pid=6847, name=gstglcontext, Channel ID 000000b6 intr 00800000
[ 3674.559536] NVRM: Xid (PCI:0000:10:00): 32, pid=6847, name=gstglcontext, Channel ID 000000b6 intr0 00040000
[ 3674.559871] NVRM: Xid (PCI:0000:10:00): 32, pid=6847, name=gstglcontext, Channel ID 000000b6 intr 00800000

OS: Nobara Linux 38 (KDE Plasma) x86_64 
Host: MS-7C91 2.0 
Kernel: 6.6.7-203.fsync.fc38.x86_64 
Resolution: 2560x1440, 1920x1080 
DE: Plasma 5.27.9 
WM: KWin 
Display Server: X11
CPU: AMD Ryzen 7 5700G with Radeon Graphics (Integrated Graphics disabled on bios)
GPU: NVIDIA GeForce RTX 4060 Ti - Driver 535.146.02
Memory: 32GB 3200MHz

If any information was left out, please message me that I'll update this message

gstglcontext looks like GStreamer OpenGL. Also your Nvidia dmesg errors look similar to AMD's page fault maybe?

Could you try adding PROTON_HIDE_NVIDIA_GPU=0 %command% ?

New problem: Really, really bad performance (8 fps max ingame on i9-10850k, RX 7900XT, 24GB RAM), might be due to it falling back to OpenGL for some reason, indicated by there being two processes in the Gnome Dock, one named Hogwars Legacy, the other OpenGL Renderer:

steam-990080.zip

Problem occurs in Proton Experimental, 8.0-4 and several custom verions.

OS: Nobara 38, Mesa Version 23.3.0

@JobeSound Have you made sure with something like mangohud that the game isn't using your iGPU instead of your 7900xtx?

@JobeSound Have you made sure with something like mangohud that the game isn't using your iGPU instead of your 7900xtx?

Mangohud shows 0 GPU usage, so I think it might really be using the iGPU, but this has also turned up some conflicting information. Mangohud and vulkaninfo both report driver version 24.0.0-devel for both iGPU and dGPU, while glxinfo -B shows 23.3.0.

How would I go about forcing the dGPU? I have found MESA_VK_DEVICE_SELECT=1002:744c which should select the 7900XT but showed no change.

@JobeSound Have you made sure with something like mangohud that the game isn't using your iGPU instead of your 7900xtx?

This happened to me as well, and I have single GPU. My CPU is Ryzen 5 2600, which doesn't have an iGPU. And it's not just a AMD GPU problem, since I have an NVIDIA GPU.

@siren15 Are you using a second monitor? My issue was caused somehow by my second monitor being connected to the HDMI port in the MB (I have 1xHDMI port and 3xDP in my GPU and no DP cables). It worked fine for almost everything including games in Linux, but not in Windows (second monitor had no signal). I set the UEFI to disable iGPU output (not sure what it's called exactly) and got it to work. Was going to get a DP cable soon anyway, will update if having both monitors connected to the GPU helps.

@JobeSound I only have a vive link box plugged in, for my vr setup, and I don't think that really counts as a monitor. So no, unless just the fact that you have something else beside your primary monitor plugged in to your GPU, is what's causing the issue.

You can use nvtop to see GPUs and it's load when game is running.

I am having trouble getting it working, I have a RTX 2060 TI, 16gb ram, i7 running on Mx Linux(Debian)

I can get it to the warning screen then it just crashes.. Ill try to figure out how to get the logs and more details

Had no luck. The game crashed in less than 20 minutes when it launched.

Proton experimental gave this me. I tried 5 times:

I get the same most times with all of Proton 8, Experimental bleeding-edge, and GE 8-25. The crash isn't reliable though, the timing can change and sometimes it starts (about 20%). Weirdly it never allocates even close to 100% of VRAM. Anyway, I have 100% success rate when setting VKD3D_CONFIG=pipeline_library_app_cache

No issues to report once it's actually running.

Specs: CachyOS (Arch), KDE Plasma X11, 4070 Ti (driver 545.29.06)

I solved Out of video memory error on NVIDIA (driver version 545.29.06) during startup following way :

deleted vkd3d-proton.cache (and vkd3d-proton.cache.write ) from Hogwarts Legacy/Phoenix/Binaries/Win64

and modified steam cmd line : VKD3D_SHADER_CACHE_PATH=0 %command%

Out of video memory error not appear anymore but nag long black screen at start before "preparing shaders" still irritate.

PS : look like problem with proton internal cache (ie DXBC/DXIL -> SPIR-V conversion caching). I think this issue have to be sent to vulkan developers

I solved Out of video memory error on NVIDIA (driver version 545.29.06) during startup following way

I had occasional out of video memory errors on AMD Radeon when using VKD3D_SHADER_CACHE_PATH=0.

I enabled vsync in game and disabled upscale

I always use V-Sync and never use upscale (I just reduce the "resolution" a little) - I have occasional pagefaults on AMD anyway.

Ultra is playable at around 42-47 but it stutters more

I noticed if Hogwarts Legacy drops below 60 FPS on ultra it stutters also with FreeSync enabled (less than FreeSync disabled, but still stutters). It's smooth on Windows. My monitor range is 40-60 FPS.

I had occasional out of video memory errors on AMD Radeon when using VKD3D_SHADER_CACHE_PATH=0.

Sorry. I ma bit not get what relation your comment have to "out of video memory" issue on NVIDIA. On Nvidia this issue prevent booting of game completely until you change proton version. My workaround prevent constant changes of proton version.

With proton-experimental or proton-GE-8-27 the game fails to start and shows an error Failed to initialize DirectX 12. Graphics drivers may require an update, or graphic adapter may not be supported.

It launches with proton 8.0-4, however it takes 5 to 15 minutes to get past the initial black screen/epilepsy warning, every time. After that, it works well.

NVIDIA GTX 1060 6GB with 535.43.02 driver and kernel 6.5.13.

@bluca Hi there.
Could i get you to attach a log from Proton Experimental? If you run the game with PROTON_LOG=1 %command% as a launch option in Steam a log called steam-990080.log should appear in your users home folder.

Sure
steam-990080.log.gz

@bluca Could you try a few things to try to narrow down the point of failure?

1. Does dx12 mode work on Proton 8.0-5rc? You can select that as a Beta option from the Proton 8 tool.
2. Could you try dropping in vkd3d-proton from 8.0-4 into Proton - Experimental?
   cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/vkd3d-proton/.
   cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib64/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/vkd3d-proton/.
   After you are done, you can delete the Proton - Experimental/files/lib64/wine/vkd3d-proton/ and Proton - Experimental/files/lib/wine/vkd3d-proton/ folders and "Verify integrity of files" on Proton - Experimental to get the original shipped versions.

1. No, same error, logs:
   steam-990080-8.0-5rc.log.gz

2. Yes it works, logs:
   steam-990080-copy.log.gz

@bluca Thank you for the info! I'm assuming you aren't set up to build vkd3d-proton and run a bisect? Unfortunately we have been unable to repro, so that is the only way to try to figure out what is going wrong. If you are up for it, I went ahead and put the first build for a bisect here: https://www.codeweavers.com/xfer/alasky/hogwarts-legacy-bisect/ with lock code "hogwarts". To test, you can drop the tarball in ~/.steam/steam/compatibilitytools.d/. (you might need to create this folder) and reboot Steam. After that, the Proton version will show up in your drop-down menu and you can select it and see if this version succeeds or fails.

The linked version works. But I can bisect it myself - what's the version/sha that was included in 8.0-4?

nvm found it

The README said you could just rebuild the same builddir and it should work, but that is apparently not the case, and was causing that build problem. By blasting it away on each bisect step it fixes that.

And I found the problem - the first bad build is this commit which enables DXR by default: https://github.com/HansKristian-Work/vkd3d-proton/commit/1a049c662cf9ea968c17fad17a4a76c582957492

And sure enough, by setting VKD3D_CONFIG=nodxr the game launches just fine with the current Proton Experimental.

I reproduced the out of memory errors on launch with GTX 1660 Ti and RTX 4070. It happened reliably on both if I deleted the shader cache between launches, though it would usually only happen for a single launch on the 4070, unlike the 1660 where it would continue until I deleted the vkd3d-proton.cache file as well.

I tested the 4070 with 535.43.22 (the Vulkan beta driver) and wasn't able to reproduce the errors with that, so hopefully that should work better.

Hello @bluca, NVIDIA 535.43.02 is relatively old and also marked beta in that release series. Are you able to test a newer driver version without treading into the Franken-Debian realm?

@kisak-valve @alasky17 I have installed the latest nvidia production branch release, 535.154.05, released two days ago, and it does not make a difference, still the same error.

An update... today i've managed to start the game without changes any paramters or variables.
The game starts without problem.
After initial wizard i've closed the game and....now...

It wont starts anymore!!!!!

I've tried a dozen times but nothing happend. Same error as before.

It is so strange...

I have a weird reproducible crash of Hogwarts Legacy. In the error condition, a few seconds after starting the game, before even the Epilepsy Warning screen is shown, the game will open a small window titled "The Phoenix game has crashed and will close" with contents only the words "Fatal Error". Note that this is different from the message a lot of Windows users seem to encounter that contains more text and starts with "LowLevelFatalError".

Now for the weird part: If I start Steam from a terminal, then Hogwarts starts without issues. If I start Steam with the .desktop file that has Terminal=false from my desktop environment (which is Cinnamon), Hogwarts crashes with the above error. It's 100% reproducible.

It does not seem to be related to stdin/stdout/stderr. I can redirect all 3 from/to /dev/null when launching steam and the game will still work if steam is started from a terminal. It's also not necessary that the terminal window is still around, when the game is started. My current start script to work around this bug looks like this:

#!/bin/bash
set -m #enable job control in script
steam >/dev/null </dev/null 2>/dev/null &
disown
sleep 2

I launch this from the steam.desktop file with Terminal=true, so the terminal opens for 2 seconds and then closes.

Some theories on what could be responsible:

• Something to do with process groups/controlling terminal
• Some process settings/limits applied by PAM differently for a terminal session than for the main window manager session

The system is Ubuntu 22.04 with the Cinnamon desktop environment. I've tried both Proton 8.05 and Experimental. Same behavior.

RE: vm_max_map_count
Arch is increasing the default value to reduce crashes: https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/ so this should no longer be required as a change on latest Arch releases.

@bluca Are you able to reproduce the initialization issue with the latest 550 production driver? Right now this would be 550.67.

I've checked DualSense 5 game pad after game update on Windows - gamepad works very well there with haptics, rumble. On Proton it still doesn't have any haptics. Rumble works only when DS5 gamepad is detected as Xbox (sometimes after hot-plugging).

Compatibility Report

• Name of the game with compatibility issues: Hogwarts Legacy
• Steam AppID of the game: 990080

System Information

• GPU: NVIDIA Corporation GA106 [Geforce RTX 3050]
• Video driver version: nvidia 550.78.0.0
• Kernel version: 6.6.32
• Link to full system information report as Gist: https://gist.github.com/phodina/0ba43f42caa43147ab92879e72f89bcf
• Proton version: Experimental

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-990080.log

https://github.com/ValveSoftware/Proton/assets/2997905/3bbf736c-a1cd-40d4-b397-2ba862b6ebb4

Symptoms

The game starts but the window does not display any graphical output. Sound can be heard.

Reproduction

Launch the game

Hi @kisak-valve ,
yes so I switched to X based session instead of Wayland GNOME session. The window also provides no graphics just graphs the buffer for whole desktop. There's no sound and the dialog about wait/kill pops up. After several wait buttons press I killed the app and it completely crashed the session.

Same on the second attempt.

Here's the log.

steam-990080_first_attempt.log

steam-990080-second_attempt.log

I'll check the egl render path as you suggested.

The game is still resetting the AMD GPU (sometimes without pagefault im dmesg, sometimes can soft-recover after few seconds of freeze):

[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4033305, emitted seq=4033307
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 4394 thread vkd3d_queue pid 4537

or

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32780)
amdgpu 0000:03:00.0: amdgpu:  in process HogwartsLegacy. pid 9282 thread vkd3d_queue pid 9422
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000a0be5000 from client 0x1b (UTCL2)
amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4909244, emitted seq=4909246
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 9282 thread vkd3d_queue pid 9422

or

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32779)
amdgpu 0000:03:00.0: amdgpu:  in process HogwartsLegacy. pid 13107 thread vkd3d_queue pid 13247
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080008ad6e000 from client 0x1b (UTCL2)
amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401430
amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Mesa: 24.1.5 (compiled)
Kernel: 6.10.3 (Manjaro)

Any ideas?

@zaps166 I haven't been able to reproduce this with my card in the 2 hours I tried. How often would you say you encounter these crashes? Do you see it happen more often in specific areas or doing certain actions? What model is your card? I see that you've been affected for a few months at least, but would you say the crashes were always there for you or did they start at some point?

@simifor

How often would you say you encounter these crashes?

For me it looks random - sometimes few hours no crash, sometimes few minutes, sometimes within 1-2 hours.

Never tried to play longer on Nvidia and/or Windows, so can't tell about them.

I use VKD3D_SHADER_CACHE_PATH=0.

It also doesn't depend when I use Ultra or High image quality, FreeSync doesn't matter, too. I have V-Sync always enabled, TAA without other upscaling. Image size (resolution) also doesn't matter. Motion blur, CA, Film Grain - disabled, FoV set to max. RT off.

What model is your card?

RX 6900 XT. It never happened in different games. Currently only in this game or my Vulkan applications when I do a mistake.

Do you see it happen more often in specific areas or doing certain actions?

I have to look more carefully when this happen again, but it's in various locations/actions - flying, walking, running, fighting...

I see that you've been affected for a few months at least, but would you say the crashes were always there for you or did they start at some point?

I play occasionally also other people sometimes play on my PC on their accounts - all have same issues in various locations in game. Also I see similar crashes from other people here - did it stopped crashing for them or they stopped reporting it? I see similar crashes since the first game release (so game update, kernel update, mesa update doesn't matter).

@zaps166 It's hard to say for certain what the cause might be, but one thing that comes to mind is this https://gitlab.freedesktop.org/drm/amd/-/issues/3131 if you use mangohud you can check your clockspeed to see if it might be clocking too high. If you limit the speed and stop seeing the crash, it would be worth sharing your experience in that thread.

@simifor Recently (for few weeks) I already limited GPU clocks to 2 GHz and I see same crashes, but I have drastically lower power consumption and only little lower graphics settings. In the past I remember I used stock clocks without any manual adjustments - same crashes.

Next time when I'll play, I'll monitor all clocks, voltages, temperatures, etc.

Is it any (simple) way to debug it somehow?

@zaps166 well, at this point it's just a guess that the card might be clocking too high and leading to a gpu crash. If that's the case, the card should be clocking higher than the manufacturer advertised speed, so you can use something like mangohud to keep an eye on clockspeeds to make sure it's not actually going higher than your limits..

Now, to be fair, clocking higher than manufacturer speeds is actually expected, and this is something that happens on both windows and linux, but in some cases it seems that linux is clocking even higher than windows. IF the card is clocking higher than manufacturer speeds and crashing, it's a good idea to ensure that you can actually cap it to a lower point and see if crashes still happen to discard or confirm that this is the issue here.

@simifor Yes, I already lowered clocks to 2 GHz (normally it boosts to ~2.5 GHz) and I had same crashes.

Today I haven't crashed yet, but in logs I have a lot of lines like this:

38643.969:0130:02d4:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 4096 < 65536 (dim 3, 256 x 256 x 1, 9 levels, 1 samples, fmt [#53](/issue/ValveSoftware/Proton/53), flags #0).

Compatibility Report

• Name of the game with compatibility issues: Hogwarts Legacy
• Steam AppID of the game: 990080

System Information

• Distro: Gentoo Linux (LLVM18-based)
• CPU: AMD Ryzen 7 3700X 8-Core
• GPU: RX 7800 XT
• Video driver version: Mesa 24.2.2 (radeonsi, navi32, LLVM 18.1.8, DRM 3.57)
• RAM: 32 GB @ 3600 MHz
• Kernel version: 6.10.9-tkg-eevdf-gentoo-llvm18-generic_v3
• Link to full system information report: Gist
• Desktop Environment: KDE Plasma 6.1.4
• Display Session: Wayland
• Proton version: 9.0-3 experimental-bleeding-edge-9.0-121840-20240920-pc506af-w9d08b8-d43c276-v2ce6df

I confirm:

• [x] that I have checked whether there are updates for my system available.

steam-990080.log

Symptoms

The game froze from what I presume must be a thread issue related to my usage of a PS4 controller (references to HID and controller are found in the log).

. . .

"../src-wine/dlls/xinput1_3/main.c: controllers[0].crit" wait timed out in thread 0134, blocked by 02fc, retrying (60 sec)
"../src-wine/dlls/winebus.sys/main.c: cs" wait timed out in thread 0080, blocked by 0070, retrying (60 sec)

. . .

Steam itself then becomes unresponsive, forcing me to close the game with ALT+F4 instead of the "stop game" button in the Steam client.

For additional context: my PS4 controller was low on battery at this time but had not disconnected from it quite yet; my desktop still reported it as connected, so I'm not quite sure what triggered this xinput error in Proton.

Reproduction

1. Advanced Launch Options: PROTON_LOG=1 DXVK_HUD=compiler PROTON_HIDE_NVIDIA_GPU=1 gamemoderun %command%
2. Use an (official) Sony PS4 controller via Bluetooth
3. Start the game (new game)
4. Progress past the initial prologue until you have access to walk around freely
5. Do the "Charm" class quest (This was the order I did it in but this might not be required)
6. Attempt to do the "Defense Against the Dark Arts" quest <- (Froze for me at the point)

Also, controller hotpluging seems to not work... For me, if the controller becomes disconnected during gameplay, attempting to reconnect it makes the game stop recognizing its inputs.

EDIT: Additionally, when launching the game, sometimes my inputs get changed via the Steam Input menu automatically; most frequently, the Left Bumper/L1 gets rebound to Left Trigger for some reason.

Also, controller hotpluging seems to not work... For me, if the controller becomes disconnected during gameplay, attempting to reconnect it makes the game stop recognizing its inputs.

Whole below text is about DS5 gamepad.

I can confirm, but it depends on settings, etc. When Steam Input is enabled for this game, it can't detect after hot plugging. Otherwise it can detect again, but it can be detected as XBox or PlayStation (random which glyphs get).

When Steam Input is enabled:

• no hot plugging
• on Proton Experimental we have regular rumble and PlayStation glyphs
• on Proton 9 we have regular rumble and XBox glyphs

When Steam Input is disabled:

• hot plugging working, but poorly (see below text)
• no rumble
• gamepad connected via USB - no audio haptics in this game (on Windows it works correctly), game doesn't open any audio stream for gamepad

And sometimes it just hangs on a black screen upon launching the game with gamescope...
(Launched gamescope in a terminal, then added DISPLAY=:1 to the game's launch options)

I launched the game 3 times so far this afternoon and now I just can't seem to get past this. :/

EDIT: Wait, what? That's... odd. My proton version was changed to experimental for some reason. Rather, I guess I was using experimental the whole time and just thought I was until now?

EDIT: Wait, what? That's... odd. My proton version was changed to experimental for some reason. Rather, I guess I was using experimental the whole time and just thought I was until now?

Experimental is used for this game by default (why?). You can change it in game properties by manually selecting different Proton version.

@kisak-valve I assure you that is not the case:

@kisak-valve I can confirm with @ThisNekoGuy post.

I've been having similar problems to @zaps166. Sometimes it works for hours, sometimes it crashes after 15-30 minutes of play.

• GPU: AMD Radeon RX 6800 XT
• Driver: Mesa 24.1.6-1
• Kernel: 6.10.6-10-MANJARO
• DE: KDE Plasma 6.0.5 (X11)

Before I play, I su root, echo "manual" > /sys/class/drm/card1/device/power_dpm_force_performance_level and echo "1" > /sys/class/drm/card1/device/pp_power_profile_mode.

The game freezes, the screen goes blank and then comes back, still frozen. I have to forcibly turn my computer off with the power button. These are the logs:

amdgpu 0000:0a:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32793)
amdgpu 0000:0a:00.0: amdgpu:  in process HogwartsLegacy. pid 14145 thread vkd3d_queue pid 14220
amdgpu 0000:0a:00.0: amdgpu:   in page starting at address 0x00008000e0523000 from client 0x1b (UTCL2)
amdgpu 0000:0a:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301430
amdgpu 0000:0a:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:0a:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:0a:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:0a:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:0a:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:0a:00.0: amdgpu:          RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3534728, emitted seq=3534729
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 14145 thread vkd3d_queue pid 14220
amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
amdgpu 0000:0a:00.0: amdgpu: failed to suspend display audio
amdgpu 0000:0a:00.0: amdgpu: MODE1 reset
amdgpu 0000:0a:00.0: amdgpu: GPU mode1 reset
amdgpu 0000:0a:00.0: amdgpu: GPU smu mode1 reset
amdgpu 0000:0a:00.0: amdgpu: GPU reset succeeded, trying to resume
[drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
[drm] VRAM is lost due to GPU reset!
amdgpu 0000:0a:00.0: amdgpu: PSP is resuming...
amdgpu 0000:0a:00.0: amdgpu: reserve 0xa00000 from 0x83fd000000 for PSP TMR
amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
amdgpu 0000:0a:00.0: amdgpu: SMU is resuming...
amdgpu 0000:0a:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5a00 (58.90.0)
amdgpu 0000:0a:00.0: amdgpu: SMU driver if version not matched
amdgpu 0000:0a:00.0: amdgpu: use vbios provided pptable
amdgpu 0000:0a:00.0: amdgpu: SMU is resumed successfully!
[drm] DMUB hardware initialized: version=0x02020020
[drm] kiq ring mec 2 pipe 1 q 0
[drm] JPEG decode initialized successfully.
amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring sdma2 uses VM inv eng 15 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring sdma3 uses VM inv eng 16 on hub 0
amdgpu 0000:0a:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
amdgpu 0000:0a:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
amdgpu 0000:0a:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
amdgpu 0000:0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
amdgpu 0000:0a:00.0: amdgpu: recover vram bo from shadow start
amdgpu 0000:0a:00.0: amdgpu: recover vram bo from shadow done
amdgpu 0000:0a:00.0: amdgpu: GPU reset(2) succeeded!
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

@riiga

Exactly, totally random.

You gave steps to use 3D fullscreen profile - it means you don't use corectrl and you don't undervolt your GPU?

I have to forcibly turn my computer off with the power button.

Xorg should restart automatically after a while (do you use modesetting driver? - delete xf86-video-amdgpu package). Otherwise enable sysrq keys and press sysrq+K (and wait a bit) - should kill and restart the graphical session after GPU reset.

Exactly, totally random.

Yeah, yesterday when I decided to report my problem on here was after the game crashed only 15 minutes or so into playing. After rebooting and commenting here I played again without problem for 3 hours more.

You gave steps to use 3D fullscreen profile - it means you don't use corectrl and you don't undervolt your GPU?

Correct. I have CoreCtrl installed but don't use it anymore. I only used it to adjusted the fan curve on my old RX 590 before I bought my current card. Should I be using CoreCtrl instead of setting 3D fullscreen?

Xorg should restart automatically after a while (do you use modesetting driver? - delete xf86-video-amdgpu package).

It would seem I am using amdgpu. No idea what the difference between that and modesetting is.

inxi:

 Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT /
    6900 XT] vendor: XFX Speedster MERC 319 driver: amdgpu v: kernel
    arch: RDNA-2 bus-ID: 0a:00.0
  Display: unspecified server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    driver: X: loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi
    gpu: amdgpu resolution: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: gbm,x11,surfaceless,device inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6800 XT (radeonsi
    navi21 LLVM 18.1.8 DRM 3.57 6.10.6-10-MANJARO)
  API: Vulkan v: 1.3.279 drivers: radv surfaces: xcb,xlib devices: 1

@riiga

Should I be using CoreCtrl instead of setting 3D fullscreen?

You can create manual profile in CoreCtrl which will set 3D fullscreen and choose it from system tray instead of writing commands. After playing game you can uncheck profile from system tray to use global profile which you can configure to go back to Automatic performance mode.

It would seem I am using amdgpu. No idea what the difference between that and modesetting is.

In the past xf86-video-amdgpu didn't reset Xorg automatically after GPU reset. On modesetting Xorgs closes and DM manager restarts. modesetting is universal and modern driver, works good for AMD GPUs for me (also allows to run Zink). But be aware that wine and proton background processes with exe files has to be killed manually after session restart before starting Steam again.

Another solution is to use amdgpu.reset_method=3 parameter - it should throw DEVICE_LOST and freeze the game only (alt-tab + Stop button on Steam should be enough). But it's not perfect, I found it breaks hibernation and can't recover all crashes properly (e.g. after some crashes you can have higher idle GPU power consumption or lower performance until reboot).

Hey guys

I had similar issues, the game crashing randomly, being barely playable, low FPS and whatnot.
However I found a solution that might also work for your systems: Turn off XMP in your BIOS. After I turned it off, I haven't had a single crash in 10 hours of gameplay.

Running everything on ultra (no RT) on 1440p@120fps works like a charm I'd say, although the occasional frame drop still occurs and most likely is due to poor optimization.

My GPU is an nVidia RTX 3080 Ti running on driver version "565.77" on EndeavourOS.

I really hope that you can enjoy this game as much as I can. :)

Game runs after update. I guess a lot of problems in this game is because of in-game shader cache (including few minutes black screen on Nvidia when loading and maybe AMD PAGEFAULT crashes).

1. Disable Steam shader cache (I always have this disabled).
2. Keep vkd3d-proton and GPU drivers cache enabled (don't disable manually).
3. Delete game shader cache on every game start. It can be done by the script:

#!/bin/sh
cd "/home/user/.local/share/Steam/steamapps/compatdata/990080/pfx/drive_c/ProgramData/Hogwarts Legacy/" || exit
rm -f D3D*cache
exec "$@"

In Steam game LAUNCH OPTIONS: /home/user/del_hl_shader_cache.sh %command%

Please modify paths and script name.

@ginolegigot Thank you for the report.
This Nvidia specific crash have already been fixed on Bleeding Edge i can see. But it haven't made its way to regular Experimental yet.

Looks to me there's a good number of people complaining about the game not starting after the update, it might be a game issue.

@UsernamesAreNotMyThing

Looks to me there's a good number of people complaining about the game not starting after the update, it might be a game issue.

It might be a game issue, especially in-game shader cache. Does deleting the cache manually (C:\ProgramData\Hogwarts Legacy\D3D*) help them to launch the game?

Thank you @Blisto91 i confirm getting proton experimental on bleeding edge fixes the issue thanks!

@kisak-valve I have a question about Dual Sense gamepad. I noticed dualsense-haptics-wip branch for proton-experimental. Game opens the audio stream for gamepad and it's working. Are there any plans to push these changes to proton-experimental?

Another interesting thing is that haptics on this gamepad in Horizon Forbidden West just works on default proton-experimental branch.

Hello @zaps166, friendly reminder that I'm a moderator for Valve's issue trackers on GitHub and not a Proton developer myself. I don't have any extra insight into that Proton build.

Ok, sorry for that ping!

I have a black screen Issue. When game starts I see only black screen, but music plays. Some time later I'm able to reach main menu by pressing any key (according to sounds, main character laughs, snitch). Tried bleeding edge and deleting content of drive_c/ProgramData/Hogwarts Legacy/, nothing changed. (Latest nobara, nvidia 4070)

This is the current performance with Proton using an Nvidia 4090 - https://www.youtube.com/watch?v=vclKGHPzF5U

For the loading issue @nllsdfx has mentioned, this also happens to me using Windows 11 (Same hardware) and on another older computer with a 6700k and an Nvidia GTX 1080. On the GTX 1080 for example it takes around 6 minutes for the Shader loading line to visually show. On the 4090 computer in might take even 30 seconds before anything visually shows, or it might happen in less than a second.

On both cases I do need to wait for the shader compilation to finish. I got used to waiting between 30 seconds to over 5 minutes already (For this particular game only), and only because on Windows 11 it also happens once in a while.

Why is the sky blacked out when I open the door?

Note that if you are using the 570 driver and you are not in the latest official version of it, then there is a 50% fps penalty to the game. Am currently 50% fpa less right now when I moved from the 565 to the 570 for testing. Cyberpunk is also affected.

Hogwarts Legacy is the most weirdly broken game I've ever tried in Proton. It runs on the first attempt - I created a character and finished the tutorial. On the second launch attempt... nothing. Doesn't start at all. Syncs save game with cloud then shuts down. Checking game integrity succeeds
PROTON_LOG=1 results in an almost empty file:

lizsquir@PiMutant:~$ cat steam-990080.log 
======================
Proton: 1742490093 proton-9.0-4e
SteamGameId: 990080
Command: ['/mnt/data/steam/steamapps/common/Hogwarts Legacy/HogwartsLegacy.exe', '-SaveToUserDir', '-UserDir=Hogwarts Legacy']
Options: {'forcelgadd'}
depot: 3.0.20250210.116596
pressure-vessel: 0.20250122.0 scout
scripts: 0.20250122.0
sniper: 3.0.20250210.116596 sniper 3.0.20250210.116596
Kernel: Linux 6.8.0-56-generic [#58](/issue/ValveSoftware/Proton/58)-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 14 15:33:28 UTC 2025 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
======================

The solution is to delete steam/steamapps/compatdata/990080 on every launch, forcing the game to install on every start.

@kisak-valve https://gist.github.com/pshem/0a4dc0d6c2416932c09de6c3565d26cc maybe this gist tells you something it doesn't tell me. I've trimmed it to start just before I installed Hogwarts legacy for the first time, (first game execution is WarThunder), and ended it after Hogwarts legacy started consistently starting... knock on wood.

This sequence repeats a lot when Hogwarts failed to start:

[2025-03-29 21:43:46] Adding process 55185 for gameID 990080
[2025-03-29 21:43:46] Adding process 55186 for gameID 990080
[2025-03-29 21:43:48] Adding process 55273 for gameID 990080
[2025-03-29 21:43:48] Traceback (most recent call last):
[2025-03-29 21:43:48]   File "/mnt/data/steam/steamapps/common/Proton 9.0 (Beta)/proton", line 1745, in <module>
[2025-03-29 21:43:48]     g_session.init_session(sys.argv[1] != "runinprefix")
[2025-03-29 21:43:48]   File "/mnt/data/steam/steamapps/common/Proton 9.0 (Beta)/proton", line 1652, in init_session
[2025-03-29 21:43:48]     g_compatdata.setup_prefix()
[2025-03-29 21:43:48]   File "/mnt/data/steam/steamapps/common/Proton 9.0 (Beta)/proton", line 852, in setup_prefix
[2025-03-29 21:43:48]     self.migrate_user_paths()
[2025-03-29 21:43:48]   File "/mnt/data/steam/steamapps/common/Proton 9.0 (Beta)/proton", line 823, in migrate_user_paths
[2025-03-29 21:43:48]     os.rename(old, old + " BACKUP")
[2025-03-29 21:43:48] OSError: [Errno 39] Directory not empty: '/home/lizsquir/.steam/debian-installation/steamapps/compatdata/990080/pfx/drive_c/users/steamuser/Local Settings/Application Data' -> '/home/lizsquir/.steam/debian-installation/steamapps/compatdata/990080/pfx/drive_c/users/steamuser/Local Settings/Application Data BACKUP'
[2025-03-29 21:43:48] Game Recording - game stopped [gameid=990080]

Seems like Proton can recover from one failed prefix move, but not two?

@kisak-valve Seeing the same issues as fellow B580 owner @Shanrya.

System Information

• GPU: Intel Arc B580 [Mesa Intel(R) Graphics (BMG G21) (0xe20b)]
• Video driver version: Mesa 25.0.2
• Kernel version: 6.13.9
• Link to full system information report as Gist:
• Proton version: Both GE-Proton9-27 (Flatpak) and Proton Hotfix

Symptoms

No longer seeing the triangular corruption the other user mentioned, but still seeing shimmering artifacts around edges. I assume this is also a driver issue?

Clip recorded using Steam Recordings. Steam seems to only produce corrupted clips for me, so I've attached some screenshots too.

https://github.com/user-attachments/assets/d207f60e-5ebb-4ce7-aab9-b98c8ea8bb47

Confirmed the game is crashing, but after almost 30 minutes (Intel 14900K, RTX 5090, Driver 580.95). I will add the proton log later, but the video is here https://www.youtube.com/watch?v=lDPQPLv2O_Q as proof (I was hoping it would not crash, but after about 25+ minutes I got the out of memory issue).

Started playing the game a couple of days ago. Ray tracing seems to be bugged. When turned on in combination with DLAA or TAA, the ray traced lighting seems to flicker on and off. It's not a fast flicker, it mostly looks like it's off and then randomly turns on for a second. Switching to DLSS fixes it.

Also I can't turn on Reflex until the DLSS is on.

Here's the example:

https://github.com/user-attachments/assets/3574c6d1-f766-40b5-be11-3f4afaa62b50

System Information:
Distro: EndeavourOS Linux
Kernel: 6.18.2-arch2-1
RAM: 64 GB
GPU Driver: NVIDIA 590.48.01
GPU: NVIDIA GeForce RTX 4090
CPU: AMD Ryzen 9 7950X
Default Proton.

Enabling Raytracing results in unplayable lags on my system, even with the lowest setting. These lags show up especially when flying and when running around in Hogsmeade.

The CPU usage goes from about 50% (no Raytracing) on the highest threat up to spikes with about 100% CPU usage on all 32 threats (Raytracing on)

System Info:
Distro: Ubuntu 24.04
Kernel: 6.14.0-37-generic
RAM: 64 GB
GPU Driver: Mesa 25.3.2 - kisak-mesa PPA
GPU: AMD Radeon RX 9070 16GB
CPU: AMD Ryzen 9 5950X
GE-Proton-latest (Using Heroic Games launcher)

No Raytracing (No CPU limit):

With Raytracing (Reflections=low, Geometry=low, Shadows=off, Ambient Occlusion=off) (Highly CPU limited):

It appears that the CPU usage with Raytracing enabled is much higher than expected, even on the lowest setting. It looks like a bug.

Jerych

I am attaching the PROTON_LOG related to my issue.
After the Proton Experimental update dated 2025-12-23, the game still runs only on the integrated graphics card, despite the RTX 4080 Laptop GPU being selected in the game settings. It's the only game i have with this issue.

Steam Runtime info.txt
steam-990080.log
steam-0.log

@Jerycho95 This seemed to have fixed it for me where the game will now start using my discrete GPU instead of my integrated one.

TLDR:

Use the environment variable DXVK_FILTER_DEVICE_NAME and the value is the the full name of the GPU that you have.

DXVK_FILTER_DEVICE_NAME

adding "DXVK_FILTER_DEVICE_NAME = NVIDIA GeForce RTX 4080 Laptop GPU" works. Thank you !

Hey there, new to linux and definitely never posted on steam's github trying to debug something so if I'm in the wrong place please let me know.

Basically bought and installed Hogwarts Legacy only a few days ago and it doesn't run. I click launch game, something pops up for a split second and then closes again. I have verified the game installation but that's about all my troubleshooting skills. Any help on this would be greatly appreciated.

• Distro: Linux Mint 22.2
• Kernel: 6.14.0-37-generic
• Ram: 32Gb
• GPU driver: Nvidia 580.95.05
• GPU: Nvidia RTX Pro 2000 Blackwell Laptop
• CPU: Intel(R) Core(TM) Ultra 9 285H (64bit)

Have tried proton experimental, aswell as forcing it to run on proton 8.0-5

Incase I needed to include more: System Info