Shadow of the Tomb Raider
But 1920x1080/high/gtx980 seems playable. But there walls turns black when get close to them.
Good:
Bad:
@NTMan can you reproduce the wall issue depicted above?
There no wall issue with medium settings. But another issue still there:
Random black triangles on body skin.
I was asking specifically whether those issues are Nvidia-specific or not. For the record, what's your driver version?
Distro: Ubuntu 18.04
GPU: GTX 980, Nvidia proprietary driver 396.54
RAM: 16GB
Proton 3.7-6 Beta
The black wall issue seems to be an issue with tesselation, as turning that off fixes the problem for me.
I’m also having the black artifacts on skin, which does not seem to be resolved by changing any setting.
Distro: Ubuntu 18.10
GPU: Gtx 1080, Nvidia 396.54
Ram: 8gb
Proton: 3.7-6 beta
- Proton 3.7-6 Beta - [UN-CHECK] "Use this tool ...". No launch options.
- After pressing PLAY, a warning will appear for no display adapter installed.
- TAA, BTAO, Motion Blur, Screen Space Reflections: all cause blinking spots (speckles, freckles) artifacts on Lara's skin.
- Tessellation causes black patches on some surfaces.
- No controller rumble. 'Run Benchmark'/(start button) on controller does not work.
LOW Potato - A10-7800/GTX 660SC. Mint 18.3 (4.15.0-34, Nvidia 396.51).
HIGH Potato - i5-3750 (4.0 GHz set mobo)/1070 Ti SC BLACK. SteamOS beta 2.166 (Linux 4.16, Nvidia 396.54)
Doitsujin fixed this issue earlier today, this will roll out when proton ships DXVK 0.72
With latest dxvk git wall issue is gone, but rest issues remains, including black patches on body skin.
I'll test the game once it is actually released (they have a rather interesting definition of September 14th). Skin artifacts might be another case of weird Z-Fighting that some games have on Nvidia.
@NTMan It would be nice if could actually comment on whether those issues affect you, since you're on Vega, and whether there are other (visual) bugs on your end.
@doitsujin I'm not @NTMan, but I do have a Vega 64 to test with. After updating to 0.72 I'm seeing no issues so far, aside from normal shader caching stutter.
Faces appear clean, but I'll comment again if that changes.
Ubuntu 18.04
Mesa 18.3.0-devel from padoka ppa (llvm8.0)
Kernel 4.18.0 (slightly customized to turn off AMD PSP, since it breaks reboots and passthrough)
System Info
@dlove67 Thanks. I have access to the game now as well and can't reproduce those issues on Polaris either.
Nvidia users: Please keep an eye on future Vulkan beta driver updates.
I got exactly the same issues mentioned above.
I have a GTX 1060 6GB, 16GB RAM, i7-8086k and Ubuntu 18.04 with nvidia 396.54.
I tried to install the newest dxvk in steam to test this, I cloned dxvk, built it and then installed it to the proton prefix of steam (/.steam/steam/steamapps/common/Proton 3.7/dist/share/default_pfx/). It still has the black polygon problem, did I something wrong installing it?
The DXVK DLLs you need to replace are located in Proton 3.7/dist/lib64/wine/dxvk.
@doitsujin thanks, after replacing the dxvk libs with the newest build, the black walls aren't there anymore with tesselation on.
Any idea what the flickering black dots on skin is related to?
Any idea what the flickering black dots on skin is related to?
@SammyJames Probably due to z-fighting on Nvidia cards with proprietary drivers.
I believe they (Nvidia) have a fix coming probably next week as a vulkan beta driver, you'll be able to update to it with the dev graphics-driver ppa not long after release.
I got another problem today, but since it only occured once to me and was not reproducible I guess it is hard to debug: After doing a stealth kill on a trinity guy the screen slowly turned black, very slowly starting in a small black point everything around me dissappeard, I still could go to the menu and still heard sound. After changing some graphic settings the image returned and I could set the settings back without any further trouble.
Since I only had it once in multiple hours of gameplay it is probably not important or critical, maybe it is not even a Linux/Proton/Dxvk only bug, and could occur on windows too. I just thought write it down here, so should this issue later occur in a more troubling way or more often for somebody else, it is documented...
@lal12 On Windows 10 with latest 399.24 Nvidia driver (tuned for this Tomb Raider) in DX11 I noticed flickering textures and black flashbacks in a few places. No such issues in DX12 mode so it might be driver/engine related.
Having tested with DXVK 0.72 with 2 RX 470's and a GTX 1070, no issues are present on AMD but on the nvidia driver there is lots of black spots all over lara when benchmarking. Hopefully nvidia will fix in vulkan driver update...
@lal12 i can confirm this bug, it happened multiple times to me, Nvidia GTX 1080 396.54, Ubuntu 18.04, DXVK 0.72.
it is not stealth kill relevant as it happened also at a camp or after looting a box.
it looks like a sheet of paper slowly burning till it covers the whole screen. strangely the menues work and i resolve the problem by switching from fullscreen to windowed mode.
@lal12 @Llorrin Okay, I have seen this (maybe twice), but it was many launches ago. I thought I resolved it by un-checking "Use this tool instead ..." in Steam Play settings, but that just might have been a happy (waving a dead chicken) coincidence.
@doitsujin are you dxvk developer?
I noted that the picture in game updates with jerks when the game is launched under the Wayland session or the game option "Exclusive fullscreen" set to off. And everything is so bad that even the mouse pointer move in the menu and on deskop (when the game minimized) with jerks.
Can you more investigations working dxvk under Wayland?
Thanks!
That probably happens because everything goes through XWayland. The same thing happens when using X with a compositor, but that's not something that can be fixed in DXVK.
@doitsujin
Hmmm, ok
Why another games works smooth under Wayland session?
For example Wolfenstein II: The New Colossus
I am want write bug report to XWayland but I don't know how describe what is culprit in jerks when I run "Shadow of the Tomb Raider".
Can you write bug report to XWayland?
Can anyone on Nvidia test whether the new 396.54.06 beta driver fixes the visual issues?
No. (On my LOW spec machine ^) For BTAO, Motion Blur, Screen Space Reflections and TAA and above, there are still spots. I tried to get a screen cap, but after it crashed it keeps crashing to desktop before menu load.
DXVK v0.72
GeForce GTX 660
Driver: 396.54.06
Vulkan: 1.1.85
Okay. Reboot and game validate (1 file fixed). Still there. (I arbitrarily chose BTAO for screen cap.)
For what it's worth, 410.57 didn't change this, and Vulkan is back to 1.1.82 for some reason.
Here's a proton build which doesn't fix the black patches on Lara's skin but it raised FPS from 19 to 31 (according to the in-game benchmark) for me. It needs latest DXVK and the other setting fixes mentioned here.
https://github.com/kakra/wine/releases/tag/wine-proton_3.7-3.16-unofficial-1
Meanwhile I rebased to wine-3.17 with some more patches included. This increases benchmark FPS from 31 to 32, and reduces CPU-bound from 12% to 4%:
https://github.com/kakra/wine/releases/tag/wine-proton_3.7-3.17-unofficial-1
I wonder how far Valve has come yet with making a new Proton version based on newer wine - I guess there could be sleeping a lot of performance improvements and bug fixes done by Valve people.
Also, anyone here knows if it is possible to run any games with vkd3d yet? It looks like at least this one won't find a graphics adapter in DX12 mode. Which is probably also where the launcher error results from...
- No changes with Nvidia 390.54.09 (spots remain).
- Proton 3.16-1 causes a low-resolution pixellated display.
- Game won't start with DXVK v0.90 in any Proton branch.
Proton 3.16 may have changed the screen mode numbering. You may want to switch the resolution in-game back and forth.
Okay, this appears not to be so bad at higher resolutions, but I'm testing at 720p on the lowest-of-the-low settings, including no AA. Whatever type of aliasing, or softening, is present in the current Proton (3.7) display goes completely away in 3.16, causing the fonts, etc. to get extremely jagged. There is a definite, visible difference. Not sure if it's just a more crisp render (therefore more 'correct') or what.
Anyway, there is nothing to gain right now on the 3.16 branch with this game. Looking forward, the 'jaggies' and v0.90 crashes seem like potential regressions. Nvidia Vulkan driver is null for spots so far.
I'm soon pushing an update to my own Proton build based on at least wine-3.18 and including some experimental scheduler improvements (still working on the rough edges). Rebasing was quite a hassle because upstream merged commits but it looks like I've got everything important. I'll test how it looks there with lower resolutions. Compared to Proton 3.7, the performance almost doubled. I didn't check with upstream Proton 3.16 yet (read: excluding my additional patches).
Hello @NeptNutz, please open a separate issue report for the scaling issue with Proton 3.16-1. Make sure you include the known good and affected versions.
@doitsujin Have you forgotten my request?
@NTMan Wolfenstein 2 New Colossus is afair a native Vulkan game, there's nothing to translate and frame timing becomes much easier... Doom 2016 is also a native Vulkan game which probably works just fine. In that perspective, your request has already been answered. I don't think there is any current priority to optimize for Wayland here. And then, it's probably also something which needs to be fixed on the Wine-side, too. I'd say that Wayland is just not ready for gaming yet (because of the games and layers involved, not because of Wayland).
Meanwhile, try to turn off vsync. It's probably something that you need to adjust in the game and the compositor (compositors tend to override the vsync setting).
@NeptNutz Is the other report already up? I'm seeing jagged appearance, too. The draw surface for the game is supposed to interpolate linearly but it doesn't, it uses nearest point algorithm.
Not yet. I'm sharpening the language. ;-)
@NeptNutz Is it true that only DXVK games are affected (or in other words: games that render via Vulkan, directly or indirectly)? I can see that the OpenGL fullscreen hack uses GL_LINEAR but for Vulkan it seems to be hidden away in some precompiled shader. I was already finding that when I tried to implement super-sampling by using an oversized render surface: Instead of melting pixels together, the vulkan fullscreen hack would just skip pixels instead.
BTW @NeptNutz you should be able to alleviate this problem by choosing a resolution which is an even divider of your native resolution while width and height should be still dividable by 8 or 4 (not sure)... This may not be possible for all resolutions, tho. I'd have an idea of synthesizing such resolutions in my own build if you're interested. E.g. native = 1920x1080 -> hacked = 960x540 (divided by 2) or 640x360 (divided by 3)
@kakra Yes, it looks like a DXVK issue. I just tried OpenGL and the scaling looks correct (minus all the other issues and slowness). I suppose it was wrong to assume this was, overall, a Proton issue, but I, like most I suspect, have fallen into simply equating Proton and DXVK as one in the same. ;-)
No no no, DXVK does nothing wrong. The issue comes from the vulkan code path in Proton. I just wanted to make sure that your graphics setup is ok generally. Proton scales with GL_LINEAR in opengl mode but with "VK_NEAREST" (or whatever it's called there) in vulkan mode.
In the end, I think it should be made configurable because depending on the screen setup, your personal preference, or the game itself, one mode may have benefits above the other.
@NTMan Wolfenstein 2 New Colossus is afair a native Vulkan game, there's nothing to translate and frame timing becomes much easier... Doom 2016 is also a native Vulkan game which probably works just fine. In that perspective, your request has already been answered. I don't think there is any current priority to optimize for Wayland here. And then, it's probably also something which needs to be fixed on the Wine-side, too. I'd say that Wayland is just not ready for gaming yet (because of the games and layers involved, not because of Wayland).
Meanwhile, try to turn off vsync. It's probably something that you need to adjust in the game and the compositor (compositors tend to override the vsync setting).
vsync was off all time.
I just beg you to fill appropriate bug for XWayland (provide code sample which are demonstrate problem for XWayland developers) if the problem is in it.
Moving from XWayland to X doesn't increase FPS, but make any motion smooth even on low FPS (in my case 22-30).
@NTMan Is it maybe this? https://bugs.freedesktop.org/show_bug.cgi?id=106736
Launch crash is resolved as of Proton 3.16-2 Beta (DXVK v.0.90-8-g6558b27).
The problem with jerking picture update under Wayland solved by this patch:
https://gitlab.freedesktop.org/xorg/xserver/merge_requests/48
P.S. For this magic Vsync must be ON
3.16-4 Beta crashes this on launch. (Nvidia 396.54.09)
@NeptNutz Does it crash in wineserver for you? I'm inspecting a crash with my own build here and as far as I can tell it's not related to the patches I added. You should be able to look at dmesg to quickly find which process crashed lately. If that process crashed, you may need to manually clean up the exe files still running: pkill -9 .exe.
@NeptNutz I fixed it by reintegration the esync patches. So your crash is probably unrelated because the reintegration is needed only for wine-3.19 master.
Anyone experiencing this problem with nvidia 410.73 driver? I had to manually install it on Ubuntu 18.10 and remove other 396 components. I'm interested in this game on Proton when all bug are addressed.
410.73 doesn't change much for Vulkan.
396.54.09 is still the best bet.
niedz., 11 lis 2018, 05:33: Berg Lloyd-Haig [email protected]
napisał(a):
Anyone experiencing this problem with nvidia 410.73 driver? I had to
manually install it on Ubuntu 18.10 and remove other 396 components. I'm
interested in this game on Proton when all bug are addressed.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/1417#issuecomment-437643182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHsdo6lytf2l5RtGPIPD5TTWGH0hEZpks5ut6iagaJpZM4WlyFV
.
linux 4.19.2 (archlinux)
nvidia 415.18-1
and both Proton 3.16.4-BETA and 3.7.8
Sometimes crashes and sometimes I get a black screen after this screen (sound works, can hear birds and animals):
Neither 410 nor 415 support all the features that DXVK currently needs. You should stick to the Vulkan beta driver currently until NVIDIA integrated the new Vulkan API functions into the mainline driver.
Hey All,
Quick question. What fps do you all get? I get around mostly in the 30s give or take. My graphics card is a GTX 970 if that has anything to do with it and settings in game are medium even with low the fps is the same. CPU is an i7. The FPS can also drop to like 15 for a few secs.
dxvk 0.92
Nvidia drivers: 410.73
To get rid of the black flashy textures we gotta turn off Ambient Occlusion, Motion Blur and Screen Space Reflections. As far as I know turning even one of them on will bring back the flashy textures.
Any one have any ideas on the fps issue? I'm sure the game can be played with my graphics card.
Other than that game is running great. Even playable.
CPU is an i7
If it's a 10-year old i7 then it would naturally struggle, this game is extremely CPU-intensive.
Its Intel Core i7-6700 @ 8x 4GHz as far as i know its 3 years old, thats what the wiki says.
An i7-3770K here, so it fits the 7 year old bill. I also get around 30 fps but CPU and GPU are both underutilized (GTX 1050 Ti 4GB). So there's probably still sync issue between threads.
Even on Windows with DX11 this game performs poorly, it can utilize only 4 threads and quickly becomes CPU bound.
This game is really meant to be played on DX12 but vkd3d isn't mature enough yet.
@kakra When you mentioned the word SYNC i thought about enabling esync that seemed to have worked on one bit...when the game loads (loading screen before mission) I now get around 200-300 fps as before it was around 50 to 70 at that bit. Still in the 30s though in game play.
Maybe that gives some one more ideas.
@mixalis1987 what is your OS?
Logs could also help, see here how to obtain them.
Could you post in-game benchmark results as well?
My results on R7 2700X + GTX 1080, Nvidia 410.73, max settings (there are artefacts visible) and SMAAT2x: https://imgur.com/a/MFPeSM8
@mati865 hmm it might be my GPU in the end might not work well with the nvidia drivers for this game. On windows I did a benchmark with the same settings "medium" the game recommended High but I thought I would try medium anyway and I got 63 fps at the end. On linux same settings I got 32 fps. In a lot of videos on the net the only difference I can see is that they are running a GTX 1080. Tried taking a screenshot but all that came out was a black picture. Oh and lowest settings on linux I got 50 fps but still had heavy drops when actually playing.
This is what gave me the tip on the GPU:
https://steamcommunity.com/app/750920/discussions/0/1734342161855349063/
My OS is Manjaro 18.0
Kernel: 4.19.2-1-MANJARO
Desktop Environment: xfce4
Ram: 16GB
@mixalis1987 are you using Exclusive Fullscreen setting? Maybe the compositor is misbehaving.
What is your output of ulimit -Hn command?
Are you CPU or GPU capped during the benchmark (you can take a picture with your mobile). Could you also try another demanding game?
It could be the issue with GTX 970 infamous 3.5GB "bug".
@mati865 No Exlusive Fullscreen is off.
The ulimit -Hn command gives 1048576
Turning off shadows does give a boost of about 10 fps but the game looks really bad.
Never heard of the graphics bug, shame don't have a higher card to test. But why then does it run better on windows OS?
@mixalis1987, @mati865 is referring to a marketing miscommunication around the release of the GTX 970. Here's a random article from around that time: https://www.pcworld.com/article/2888877/its-a-feature-not-a-flaw-nvidia-ceo-addresses-geforce-gtx-970s-memory-spec-fiasco.html
@kisak-valve Thanks for the info.
So its a feature and not a bug, but why then the difference in fps with windows and linux, it must be with the drivers then?
@mixalis1987 your CPU is unbelievably underperforming. Those figures would be right for something like i3 or Pentium but definitely not for your i7.
Exclusive Fullscreen causes game to hang when minimizing but improves performance, you should try it. Another thing to try is changing CPU scheduler to performance (or pstate-performance for Intel).
I thought DXVK could be allocating so much memory it hits that slow 0.5GiB part but it's not the case.
Nvidia released driver update to make applications less likely to allocate that 0.5GiB and I was wondering if it works with lower level stuff like DXVK.
@mati865 How do I change CPU scheduler to performance? Also it looks like enabling Exclusive Fullscreen did help.. a bit. With that on game did feel a bit smoother, still fps is around 45 though. That's with shadows set to low.
Why would the CPU under perform so bad? In task manager the cpu shows like 1-4% when i'm like browsing or something.
I figured the command to max CPU, it is cpupower frequency-set -g performance but it only helped a little bit.
@mixalis1987
cpupower frequency-set -g performance
@mati865 Thanks, yea did that. Edited my previous post 20 minutes ago.
For reference: Feral Interactive are working on a Linux port of Shadow of the Tomb Raider.
From gamingonlinux.com:
Originally published by Square Enix and developed by Eidos-Montréal, Feral Interactive confirmed today that Shadow of the Tomb Raider is officially heading to Linux in 2019.
@mixalis1987 if it's with ESYNC then I have no idea what could cause that bottleneck. There could be something useful in the logs, here are instructions how to obtain them: https://github.com/ValveSoftware/Proton#runtime-config-options
@HonkingGoose Yea I noticed that this morning, good peace of news. But no official release date could be end of 2019 haha.
@mati865 Honestly I have no idea I honestly think it's the GPU, it's getting old but I got it to a playable state. In caves and tombs its actually pretty smooth, the major drop in fps is in towns but you can still run around and do your business so for now I guess I'll have to make do with that and keep randomly checking for solutions.
It's hard to diagnose if it is the card because every one I see is playing on a gtx 1080 or more. I was planning on upgrading soon anyway so we will see.
In caves and tombs its actually pretty smooth, the major drop in fps is in towns
This and graphs you uploaded previously strongly indicate the CPU is holding back. It can be driver bug or whatever else but in the end CPU either cannot keep up or is not utilized properly.
So do I need new CPU or do we have some kind of settings we can play with? I already set the power to max performance from the command provided.
I also set the performance to max for the GPU in the nvidia control panel.
You said it's working fine on the Windows so it's not hardware issue.
You could run in the terminal this command:
while true; do (echo "%CPU %MEM ARGS $(date)" && ps -e -o pcpu,pmem,args --sort=pcpu | cut -d" " -f1-5 | tail) >> ps.log; sleep 5; done
And run around the city for about 1-2 minutes to get some data.
OK my new graphics card came today and I thought I would test it out...obviously. Indeed when changing the card it did help with the FPS on this game. I got up to 75 in towns as before I was getting 15, 25 - 30 ish. I am getting 90 to almost 150 outside of towns. I still set the CPU to performance and I also set the card to max power usage to help. without those settings I got around 40 - 50 in town still good. The card I got is GTX 1080 ti. So my theory was right.
My OS updated today and it had the latest nvidia drivers and vulkan for manjaro. Tested the game and I was getting amazing FPS up to 150 on ultra settings and around 70 in towns. We still got the flashing black skin though with the two settings mentioned previously set on. No big deal.
Just sharing since I stumbled upon this & it might provide useful.
Look at the DX11 frame latency & CPU clockspeed in the benchmark, then look at DX12.
September Benchmarks: https://youtu.be/9OKVPIOxtMY
December Benchmarks(Same problem still there: DX11 vs DX12: https://youtu.be/Am8951dIL8c
The overall framerates are better in DX12, but the CPU clockspeed is not being maintained for some weird reason, the temps are not throttling and theres no power limit issues(tested via intelburn//realbench/prime), it easily holds 4.2ghz during stress & in DX11 so the problem is with DX12 only.
This weird DX12 behaviour would also explain why the game runs much better with windows power options set to high performance(force max clockspeed). But that's just a bandaid fix rather than a real one unless you want your CPU running full bore @ desktop without changing power settings all the time.
I took a direct video of the difference when enabling high performance here: https://youtu.be/tKrdKfdLhQ0
Doesnt happen in other DX12 games and appears to be isolated to Tomb Raiders DX12 API, so the problem would likely carry over to other OS, so set your CPU frequency to max using whatever means possible.
In regards to black skin,, screen space reflections would be one of the most likely culprits. I had a shadow clipping issue with an early release of SotTR that was caused by Screen Space Contact Shadows on High. medium fixed it, but the issue has since been patched. You can see it at the start of the in-game benchmark here: https://youtu.be/9OKVPIOxtMY
In Linux, you could probably use Feral's GameMode daemon to work around this, and set the CPU to performance governor.
I'm curious if anyone who has seen the black flashing skin issue has tried with a DXVK with https://github.com/doitsujin/dxvk/commit/6dd82dfe0317387458c6788dcf51a717422fdb48 and seen whether it resolves that issue.
@pdaniell-nv No, it doesn't resolve that here (nvidia). I think the black patches should be reflection from wet skin. Comparing graphics in Youtube "Let's Play" videos with my setup leads me to think that the skin isn't rendered correctly in many scenes: DXVK introduces color banding on Lara's skin, and it looks dull instead of "sweaty" or "wet" (not sure how to describe it). But this may well be a result of lower graphics settings.
I'm currently using the latest master build here compiled as winelib.
I don't know about all that but I'm playing with ultra settings, but to not have flashing black skin I must turn off Motion Blur Screen Space Reflections and Ambient Occlusion Not sure about that last one to be honest. Also to keep the FPS above 100 and to not notice any lag in heavy populated areas I set the CPU to Performance Governor The game runs great. On my second run through now :)
@mixalis1987 I'm using motion blur because I like that effect very much - it looks more natural and makes a better immersion during fast camera movements, so I never played without it. I tried with and without SSR but it didn't remove the black patches. I also really don't like turning off AO because everything looks too flat without it. But AFAIR I've ran the benchmarks without AO and the black patches were still there. This leaves us with motion blur but I don't see how that could create such an effect. Maybe it's a specific combination of those settings (and others, too, since you use ultra quality).
@kakra Hmm indeed turning on AO and setting it to HBAO+ removes the black skin however the other one BTAO will bring the black skin. Motion Blur and SSR will bring the black skin.
@mixalis1987 I tried HBAO+ and it didn't help here... There's some effect on Lara's skin that's causing it. It can also be seen with some NPCs but only during a few cutscenes.
@kakra I've been playing for over an hour with HBAO+ on and it looks fine with NPC's. Motion Blur and SSR still off though.
Now works for me with:
linux 4.20.1 (archlinux)
nvidia 415.25-6
Proton 3.16-6 Beta
Frame rates hover around 80 fps, never below 60 on a GTX 1080. No black artifacts.
It looks like my system is very similar to elimpnick's,
linux 4.20.1 (archlinux)
nvidia 415.25 (does the "-6" mean he has a more recent driver than me?)
proton 3.16-6 Beta
nvidia gtx 1080
but even after I tried matching the graphics settings shown in elimpnick's comment, I still get the black artifacts that so many people have been talking about. Strangely, it only seems to affect Laura and Jonah's skin while all other characters seem to be unaffected. It also seems to get worse when they are closer to the screen, so it may be that it affects other NPCs but haven't got close enough to notice. Besides the artifacts and the "No Display Adapter" warning mentioned by NeptNutz, the game seems to run fine for me.
nvidia 415.25 (does the "-6" mean he has a more recent driver than me?)
That part of the version number is not nvidia but arch specific. It's a subversion/revision, instance/build, or "generation" number - not really interesting for the driver itself. It's only some arch-internal versioning scheme.
@kakra Thank you for the clarification. In that case, I'm at a loss as to why elimpnick is able to get rid of the artifacts and I'm not. I'd like to do something help resolve this but I'm pretty new to both linux and programming, so I'm not sure where to start.
@shandstp I'm also seeing the artifacts no matter which settings I chose. Almost all NPCs will show these artifacts in cut scene close-ups, it's not only Lara and Jonah. It may be a driver/hardware combo thing. I'm running on a GTX 1050 Ti 4GB, FHD resolution.
The artifacts are still there with the same settings as elimpnick.
I am running kernel 4.19.14-300, nvidia drivers 425.27 and proton 3.16-6 beta.
I have a GTX 1080 too by my framerates are between 50 and 80, with the governor set to performance.
yea black artifacts still there, using wine 4.0-rc5 and nvidia 415.25 GTX 1080ti framereates around 80ish max settings.
I updated the game via steam, video drivers to 418.30 and the kernel to 4.20.6-200 and the black artifacts are gone. Same game settings.
@topolittle Thanks! Good to know. Once those drivers are out of beta I'll be updating :)
@topolittle I can confirm that the black artifacts are gone. I wonder if this also fixes the black pixel bleeding happening sometimes when TAA is turned on.
No longer working for me.
This is on Linux 5.0.5-arch1-1-ARCH, nvidia 418.56-3 and both proton 3.16.8 and 4.2-1.
Basically, the initial splash screen loads as a black screen, then the game exits.
If I add the following launch option: PROTON_USE_WINED3D=1 %command%, I can get into the game, but it is unplayable (graphic errors and very low FPS). According to a user report here: https://www.protondb.com/app/750920, it seems it may be caused by a recent raytracing update in the game.
FWIW, it works for me when I dump the debug scripts via export PROTON_DUMP_DEBUG_COMMANDS=1 and then run it with /tmp/proton_andreas/run. It doesn't work by clicking the play button in steam.
Don't really have time to dig further, but maybe this helps someone else figure out what's going on.
Couldn't help but notice this is tagged NVIDIA yet the original report mentions AMD :)
Can confirm the PROTON_DUMP_DEBUG_COMMANDS=1 method works. and does so better than running with PROTON_USE_WINED3D=1.
2019-04-14T06:48:31.136[I] DllMain.cpp:22 Attached GfeSDK.dll
Setting breakpad minidump AppID = 750920
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198060810003 [API loaded no]
AL lib: (WW) GetSymbol: Failed to load jack_error_callback: /home/mvl/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64/libjack.so.0: undefined symbol: jack_error_callback
AL lib: (WW) jack_msg_handler: Cannot connect to server socket err = No such file or directory
AL lib: (WW) jack_msg_handler: Cannot connect to server socket
AL lib: (WW) jack_msg_handler: jack server is not running or cannot be started
AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x11
AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"
Timed out waiting for game mapping!
AL lib: (WW) ReleaseContext: 0x7fd1c400a290 released while current on thread
AL lib: (EE) ReleaseThreadCtx: Context 0x7fd1c400a290 current for thread being destroyed, possible leak!
AL lib: (WW) ReleaseContext: 0x7fd1c4009a20 released while current on thread
AL lib: (EE) ReleaseThreadCtx: Context 0x7fd1c4009a20 current for thread being destroyed, possible leak!
AL lib: (EE) ReleaseThreadCtx: Context 0x7fd1c4009a20 current for thread being destroyed, possible leak!
seems to have something todo with jack or audio libraries having a memory leak?
Also game no longer works in proton 4.2 for me
I tried @ah- 's method, it worked and indeed it remains very playable. Thanks for the workaround.
To recap, I did this:
- Set launch options in Steam with
PROTON_DUMP_DEBUG_COMMANDS=1 %command%. - Start game from Steam. Continue at "no display error" then crashes after black intro screen.
- Run
/tmp/proton_$USER/run($USERis your login).
Tested on Linux 5.0.7-arch1, nvidia 418.56-7, proton 4.2-2.
Hello @themvl, you may have encountered https://github.com/ValveSoftware/steam-for-linux/issues/6045. Please opt into Steam's beta client and/or go to Steam -> Library dropdown -> tools and verify that Proton 4.2 is installed in the list.
Oh that was it. Now @ah- technique also works with proton 4.2-2 for me on manjaro fully updated.
/home/mvl/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64/libjack.so.0: undefined symbol: jack_error_callback
Looks like a different problem. Are you using jack?
Just a quick update, with proton 4.2-3, it's back to working normal again, no launch option workaround needed (at least for me). Yay!
I am getting the "no display adapter" warning with AMD drivers
Any way I can manually set DX12, since it is grayed out?
Does anyone experiencing massive stutter and audio lag?
I'm using Arch with kernel 5.1.14 and the latest proton 4.2.x. My GPU is RX 470 8GB.
The game have pretty playable framerate, hitting 60-70 on closed space and 30 on the festival. But the massive stuttering/lagging and audio lagging when in cut scene really make this unplayable.
I haven't been able to get this game work on new Ryzen 3800X computer via Proton (works fine on Windows).
Tried same files as on old 5820k computer and brand new installation, but unfortunately neither works.
Staring without launcher (-no-launcher) also didnt help.
Other installed games on Steam works correctly, but Uplay Assassins Creed Odyssey also behaves similarly in wine.
Link to log file from PROTON_LOG=1 https://mega.nz/#!9Y5SWIzI!SIGApSwav001LLiEBP4e7kIxBgwAOc_Zyyh3rxcsEpU
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 3800X 8-Core Processor
Video Card:
Driver: NVIDIA Corporation GeForce GTX 1080 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 430.26
Operating System Version:
"Manjaro Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 5.2.2-1-MANJARO
X Server Vendor: The X.Org Foundation
X Server Release: 12005000
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20190711.3
@aaulia the stuttering is caused by shader compilation and therefore normal. You could try using mesa-aco-git to improve things a bit, but the problem won't go away.
Shadow of the Tomb Raider works fine
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3045.
@darkfinedelight posted on 2019-09-08T05:38:06:
Whitelist Request
- Name of the game to be whitelisted: Shadow of the Tomb Raider
- Steam AppID of the game: 750920
System Information
- GPU: GTX1050Ti
- Driver/LLVM version: 4.6.0 NVIDIA 435.21
- Distro version: Kubuntu 18.04
- Link to full system information report as Gist: https://gist.github.com/darkfinedelight/b86fbfa688d4853bd210e83f73c43e7f
- Proton version: 4.11-3
I confirm:
- [ ##] that pressing the
Playbutton in the Steam client is sufficient. - [ ] that runtime config options are necessary to run the game.
- [ ] that no workarounds other than PROTON_* env variables are necessary.
Issues
- [ ##] I haven't experienced any issues.
- [ ##] There are no issues left open for this game.
- [ ] Although I consider the gaming experience equal to Windows there are remaining issues:
Hello @zeitt, in case you haven't happened across it yet, please give #2927 a read.
Is anyone experiencing an issue with this game and Proton 4.11 that would block it from being whitelisted?
@kisak-valve,
I am against, since the one year glitch still not fixed: the bushes where Lara can hide at the end of survival instincts for a moment becomes purple.
Here is RenderDoc https://mega.nz/#F!Mp5n2AhT!6ZfR3UcpsF8tKKNwDVDk9w I hope it helps to fix this long-playing issue.
Live demonstration: https://youtu.be/-AHirWCo_QA and https://youtu.be/eSn-REg6PBI
Hello @zeitt, in case you haven't happened across it yet, please give #2927 a read.
Is anyone experiencing an issue with this game and Proton 4.11 that would block it from being whitelisted?
I'm not sure if I can call it an "issue", but a native Vulkan port is coming. https://steamdb.info/app/750920/history/?changeid=6828397
Valve should tell Feral to hurry up.
There's a report for the purple color issue on the DXVK bug tracker: https://github.com/doitsujin/dxvk/issues/1152
Turns out that it only happens on Linux (on all drivers, so I think we can rule that out as well). When using DXVK on Windows it works fine. Not sure what the problem is (using native d3dcompiler doesn't fix the problem, already tested that).
After a while, the screen gets black. I can still move and get to the menu. Restarting the game from menu works and I get my screen back. And then again, after a while when playing the screen gets black.
Anyone else with same symptoms?
System:
GPU: GTX 1080
Kernel: 5.3.1
Proton: 4.11-6
Nvidia driver: 435.24.02
does the black fade in like smoke?
@xexpanderx I've never seen nor heard of that problem. Did this already happen on an older Proton version or an older Nvidia driver? And how long is "a while" exactly?
does the black fade in like smoke?
Exactly like this!
I just reinstalled the NVIDIA-driver, it may have been because of a new mesa upgrade which probably overrided my NVIDIA drivers. So, I reinstalled NVIDIA and so far no "fading black smoke".
I have not played in ages but for me last time I played after playing for like an hour or so the screen would start to go black starting from like a pixel and gradually getting bigger spreadig like a water affect, untill all the screen was black and you cant see anything. You could still open menu and navigate the menu but graphics was just black. To fix this I had to go into the graphic menu and lower a specific setting but can't rememember what one. I think something to do with TAA or somehting. If you changed the setting back and forth and kept it on its high setting the game would still work and the screen would reset back to normal so you can see but after some time it would do it again.
The best thing to do, so not to happen would be just to lower the setting a bit. But I'm not sure if that is the same problem that user is having.
Oh and mine was nvidia drivers that I'm using.
Currently, not playable on the current Proton version, while on that one before.
4.11.9
And then, some fallback menu to set the graphics and so on appears:
Once clicking on "Play" the game doesn't start, so it simply crashes silently.
4.2.9
Same issue here, but game is actually starting.
Hello @ShalokShalom, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Separately, can you check if adding WINEDLLOVERRIDES="dxgi=n" %command% to the game's launch options has an effect on Proton 4.11-9?
Hi there :hugs:
EDIT2: I think I just forgot to reboot my system, shame on me (if my memory serves me well, this happened some time ago)
~~PROTON_LOG=1 %command% does not do anything here, so I am probably doing something wrong. No such file appears in my home directory.
WINEDLLOVERRIDES="dxgi=n" %command% is working. I still get the grey text boxes and fallback menu, while the game starts.
EDIT: It is about 4-6 frames slower in the build-in benchmark as 4.2.9.
Anything else there I can do?~~
I know there is a Linux port using Vulkan, but the trial version wasn't ported and it doesn't work in DX12 mode.
steam-974630.log
Hello @CSahajdacny, please open a separate compatibility report for the demo so that issues with it can be tracked properly.
proton 5.13 dx12 crash on start
Game refuses to work with Proton 5.13, which sucks because I'm at a place on the native version where there's a game breaking bug so the Proton version is the only way I can get past it and go back to the native version. But the game won't start.
The game works with Proton-VKD3D + DXVK's dxgi.dll on Windows with Nvidia. It still silently crashes on Linux with D3D12/VKD3D-Proton when using Proton Experimental.
Worked after protontricks d3dcompiler_42 d3dcompiler_43 d3dcompiler_47 d3dx11_42 d3dx11_43. It probably was d3dcompiler_47? A bit peculiar that this is still necessary at this point, even with Proton Experimental.
Game seems to work fine native and with proton-experimental.
I wanted to try the game with DLSS and DXR, so I added:
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command%
as the launch commands, but the game won't get past the initial loading screen when passing VKD3D_CONFIG=dxr. DLSS is still grayed out as well.
Game seems to work fine native and with proton-experimental.
I wanted to try the game with DLSS and DXR, so I added:
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command%
as the launch commands, but the game won't get past the initial loading screen when passing VKD3D_CONFIG=dxr. DLSS is still grayed out as well.
That's because dxvk-nvapi/vkd3d-proton's DLSS support isn't compatible with DLSS 1. Only DLSS 2 is supported. I got this from the dxvk-nvapi developer (https://github.com/jp7677/dxvk-nvapi/issues/45#issuecomment-933844150)
About DLSS not being available, this is indeed due to DLSS version 1 being used. According to Discord conversation, only DLSS version 2.x+ is supported by Proton.
Ah this is what I assumed already.
But, I'd assume DXR would be enabled if I passed VKD3D_CONFIG=dxr along. I also build VKD3D with DXR 1.1 support and passed VKD3D_CONFIG=dxr11. In both situations you crash after the initial loading screen.
I know this is very much work in progress, I'll try this commit to see if I get any further https://github.com/jp7677/dxvk-nvapi/commit/a3e0ecce70ce0eccf45bcd5d270411faa8befce8
Same behavior observed after the DLSS 2.2 patch.
You need to get the logs (go look at the dxvk-nvapi GH repo for info on how to log dxvk-nvapi) and report the issue to the dev there as well then.
Just for reference, DLSS is confirmed to work now after recent game updates, see also https://github.com/jp7677/dxvk-nvapi/issues/53#issuecomment-972847021
Shadow of the Tomb Raider showing corruption with Proton 7.0-6 - Works with 7.0-5
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6566.
@LegiossOrig posted on 2023-02-24T21:17:42:
Compatibility Report
- Name of the game with compatibility issues: Shadow of the Tomb Raider
- Steam AppID of the game: 750920
System Information
- GPU: AMD 6800XT
- Driver/LLVM version: AMDVLK 22.3.0
- Kernel version: 5.19-0.32-generic
- Link to full system information report as Gist:
https://gist.github.com/LegiossOrig/938e6bbb37ff35287de6ffc60009057e - Proton version: 7.0-6
I confirm:
- [ ] 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.
Symptoms
I have been using Shadow of the Tomb Raider shortly after 7.0-5 went public. The game was fine in DX11 mode, no corruptions seen. But 7.0-6 was released and now the characters clothing have black triangles on them. I cannot roll back to 7.0-5 as this is not an available option. I am using the open source amdvlk vulkan driver. The AMD vulkan Pro driver shows the same issues. RadV is unaffected.
Reproduction
Start Shadow if the Tomb Raider in DX11 mode, go to the settings and run the benchmark. You will see all the characters have black triangles on them.
Hello @LegiossOrig, since mesa/RADV is unaffected, this issue should be mentioned to your video driver vendor.
Hi @kisak-valve, this is not driver specific as it happens with all public AMD drivers from 22.20 forward. The change from Proton 7.0-5 to 7.0-6 seems to be the issue as something has changed.
I was using an internal build for Vulkan Pro and did not make any changes to the driver when this issue popped up. The only thing that happened was Proton updated prior to running the game. And this was observed on Feb 03,2023.
NVIDIA had a similar issue on the characters skin in earlier versions of DXVK, and this was fixed in DXVK since then. So maybe it's a problem with a change in DXVK between 7.0-5 and 7.0-6?
hi @kakra, that is my expectation as driver versions that did work with 7.0-5, now no longer work with 7.0-6 for this title.
Very similar issue. I get strange "glare" artifacts everywhere. Sometimes, they only begin to appear after loading again in a point where Lara dies. Is like it were memory corruption or similar, not sure.
I remember similar issue on Nvidia years ago with this game.
That's what surprised me the most, that I'm using a last generation Radeon card with the drivers for my distro. In some cases, those color flashing effects appear from the start, and I don't know what to try anymore.
Just so people are aware, this game uses different saves for Windows and Linux which are not compatible between platforms(!).
The native version also seems to be running behind in versions of the game than Windows.
While game currently works mostly fine with Proton Experimental (Everything maxed out, including ray traced shadows, benchmark completed no issues at all) the game will crash along with entire OS when ray traced shadows are on in the first interactive cutscene when light from the phone is being lit to Lara's face.
I tried kernel 6.6 LTS and 6.9 both the same result. Ray traced shadow setting crashes on both normal and high settings. I tried few different versions of proton result is exactly the same.
My GPU is Radeon RX 6700 XT on Mesa 24.0.9.
Does anyone experience similar problem?
@hyperstown You may like to add if you are using Wayland or X11.
@ShalokShalom good suggestion. I'm running plasma 6.0 on Wayland but I also tried X11 and it also froze entire os. Worth mentioning is that I tried to run this game on windows with exact same settings and it didn't crash.
I don't know if this is important but crash was somewhat different on X11. On Wayland game freezes and few seconds later entire desktop follows, on X11 however everything immediately froze.
I would reboot, reproduce the issue, and then post the content of journalctl -b
Log
Jun 17 12:32:30 desktop-pc plasmashell[3425]: (12:32:30) ERROR: [Legendary]: Error Getting Info from Epic API
Jun 17 12:32:31 desktop-pc xdg-desktop-portal-kde[1913]: xdp-kde-settings: Namespace "org.gnome.desktop.interface" is not supported
Jun 17 12:32:31 desktop-pc xdg-desktop-portal-kde[1913]: xdp-kde-settings: Namespace "org.gnome.desktop.interface" is not supported
Jun 17 12:32:31 desktop-pc xdg-desktop-portal-kde[1913]: xdp-kde-settings: Namespace "org.gnome.desktop.interface" is not supported
Jun 17 12:32:31 desktop-pc xdg-desktop-portal-kde[1913]: xdp-kde-settings: Namespace "org.gnome.desktop.interface" is not supported
Jun 17 12:32:34 desktop-pc syncthing[1086]: [OU4KC] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
Jun 17 12:32:36 desktop-pc baloo_file_extractor[4240]: kf.idletime: Could not find any system poller plugin
Jun 17 12:32:36 desktop-pc baloo_file_extractor[4240]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:32:36 desktop-pc baloo_file_extractor[4240]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:32:47 desktop-pc kernel: usb 3-4: 2:1: cannot get freq at ep 0x1
Jun 17 12:32:47 desktop-pc kernel: usb 3-4: 1:1: cannot get freq at ep 0x81
Jun 17 12:33:04 desktop-pc baloo_file_extractor[4588]: kf.idletime: Could not find any system poller plugin
Jun 17 12:33:04 desktop-pc baloo_file_extractor[4588]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:33:04 desktop-pc baloo_file_extractor[4588]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:33:10 desktop-pc systemd[1]: libvirtd.service: Deactivated successfully.
Jun 17 12:33:10 desktop-pc systemd[1]: libvirtd.service: Unit process 1398 (dnsmasq) remains running after unit stopped.
Jun 17 12:32:36 desktop-pc baloo_file_extractor[4240]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:32:36 desktop-pc baloo_file_extractor[4240]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:32:47 desktop-pc kernel: usb 3-4: 2:1: cannot get freq at ep 0x1
Jun 17 12:32:47 desktop-pc kernel: usb 3-4: 1:1: cannot get freq at ep 0x81
Jun 17 12:33:04 desktop-pc baloo_file_extractor[4588]: kf.idletime: Could not find any system poller plugin
Jun 17 12:33:04 desktop-pc baloo_file_extractor[4588]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:33:04 desktop-pc baloo_file_extractor[4588]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:33:10 desktop-pc systemd[1]: libvirtd.service: Deactivated successfully.
Jun 17 12:33:10 desktop-pc systemd[1]: libvirtd.service: Unit process 1398 (dnsmasq) remains running after unit stopped.
Jun 17 12:33:10 desktop-pc systemd[1]: libvirtd.service: Unit process 1399 (dnsmasq) remains running after unit stopped.
Jun 17 12:33:18 desktop-pc syncthing[1086]: [OU4KC] INFO: Joined relay relay://192.168.11.111:443
Jun 17 12:33:38 desktop-pc baloo_file_extractor[4945]: kf.idletime: Could not find any system poller plugin
Jun 17 12:33:38 desktop-pc baloo_file_extractor[4945]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:33:38 desktop-pc baloo_file_extractor[4945]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:35:27 desktop-pc plasmashell[1846]: [h264 @ 0x56e88a996000] No support for codec h264 profile 100.
Jun 17 12:35:27 desktop-pc plasmashell[1846]: [h264 @ 0x56e88a996000] Failed setup for format vaapi: hwaccel initialisation returned error.
Jun 17 12:36:02 desktop-pc baloo_file_extractor[6417]: kf.idletime: Could not find any system poller plugin
Jun 17 12:36:02 desktop-pc baloo_file_extractor[6417]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:36:02 desktop-pc baloo_file_extractor[6417]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:36:04 desktop-pc baloo_file_extractor[6444]: kf.idletime: Could not find any system poller plugin
Jun 17 12:36:04 desktop-pc baloo_file_extractor[6444]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:36:04 desktop-pc baloo_file_extractor[6444]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:36:05 desktop-pc kernel: gmc_v10_0_process_interrupt: 59 callbacks suppressed
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32804)
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: in process SOTTR.exe pid 4139 thread vkd3d_queue pid 4456
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800438919000 from client 0x1b (UTCL2)
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101031
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x1
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32804)
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: in process SOTTR.exe pid 4139 thread vkd3d_queue pid 4456
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: in page starting at address 0x0000800438919000 from client 0x1b (UTCL2)
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: MORE_FAULTS: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: WALKER_ERROR: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: PERMISSION_FAULTS: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: MAPPING_ERROR: 0x0
Jun 17 12:36:05 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: RW: 0x0
Jun 17 12:36:05 desktop-pc plasmashell[1846]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce.
Jun 17 12:36:11 desktop-pc baloo_file_extractor[6532]: kf.idletime: Could not find any system poller plugin
Jun 17 12:36:11 desktop-pc baloo_file_extractor[6532]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:36:11 desktop-pc baloo_file_extractor[6532]: qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Jun 17 12:36:30 desktop-pc syncthing[1086]: [OU4KC] INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
Jun 17 12:36:30 desktop-pc syncthing[1086]: [OU4KC] INFO: quic://0.0.0.0:22000 resolved external address quic://192.168.11.111:22000 (via stun.syncthing.net:3478)
Jun 17 12:37:06 desktop-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring comp_1.2.1 timeout, signaled seq=14854, emitted seq=14855
Jun 17 12:37:06 desktop-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process SOTTR.exe pid 4139 thread vkd3d_queue pid 4456
Jun 17 12:37:06 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset begin!
Jun 17 12:37:10 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: failed to suspend display audio
Jun 17 12:37:10 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: MODE1 reset
Jun 17 12:37:10 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GPU mode1 reset
Jun 17 12:37:10 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GPU smu mode1 reset
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:10 desktop-pc kernel: snd_hda_intel 0000:0c:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset succeeded, trying to resume
Jun 17 12:37:11 desktop-pc kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Jun 17 12:37:11 desktop-pc kernel: [drm] VRAM is lost due to GPU reset!
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: PSP is resuming...
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: reserve 0xa00000 from 0x82fd000000 for PSP TMR
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413e00 (65.62.0)
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: SMU is resumed successfully!
Jun 17 12:37:11 desktop-pc kernel: [drm] DMUB hardware initialized: version=0x02020020
Jun 17 12:37:11 desktop-pc kernel: [drm] kiq ring mec 2 pipe 1 q 0
Jun 17 12:37:11 desktop-pc kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Jun 17 12:37:11 desktop-pc kernel: [drm] JPEG decode initialized successfully.
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: recover vram bo from shadow start
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: A graphics reset not attributable to the current GL context occurred.
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: recover vram bo from shadow done
Jun 17 12:37:11 desktop-pc kernel: amdgpu 0000:0c:00.0: amdgpu: GPU reset(1) succeeded!
Jun 17 12:37:11 desktop-pc plasmashell[1846]: amdgpu: The CS has been rejected (-125).
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: kwin_scene_opengl: 0x3: GL_CONTEXT_LOST in context lost
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: OpenGL vendor string: AMD
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: OpenGL renderer string: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 17.0.6, DRM 3.57, 6.9.3-3-MANJARO)
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: OpenGL version string: 4.6 (Core Profile) Mesa 24.0.9-manjaro1.1
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: OpenGL shading language version string: 4.60
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: Driver: Unknown
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: GPU class: Unknown
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: OpenGL version: 4.6
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: GLSL version: 4.60
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: Mesa version: 24.0.9
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: Requires strict binding: no
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: Virtual Machine: no
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: Timer query support: yes
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: BlurConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: GlideConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: KscreenConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: OverviewConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: SlideConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: SlidingPopupsConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: WindowViewConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc kwin_wayland[1600]: ZoomConfig::instance called after the first use - ignoring
Jun 17 12:37:11 desktop-pc systemd[1]: Started Process Core Dump (PID 7134/UID 0).
Jun 17 12:37:17 desktop-pc systemd-coredump[7139]: Process 1846 (plasmashell) of user 1000 dumped core.
Stack trace of thread 1880:
#0 0x000077bed42a8e44 n/a (libc.so.6 + 0x94e44)
#1 0x000077bed4250a30 raise (libc.so.6 + 0x3ca30)
#2 0x000077bed42384c3 abort (libc.so.6 + 0x244c3)
#3 0x000077bec66f20e3 n/a (radeonsi_dri.so + 0x8f20e3)
#4 0x000077bec66f4b32 n/a (radeonsi_dri.so + 0x8f4b32)
#5 0x000077bec5e75434 n/a (radeonsi_dri.so + 0x75434)
#6 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1885:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1947:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1883:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2452:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bdba4960ce n/a (radeonsi_drv_video.so + 0x960ce)
#3 0x000077bdba8f729c n/a (radeonsi_drv_video.so + 0x4f729c)
#4 0x000077bdba49602d n/a (radeonsi_drv_video.so + 0x9602d)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2423:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077beabfde9b7 n/a (libpulse.so.0 + 0x339b7)
#2 0x000077beabfc845c pa_mainloop_poll (libpulse.so.0 + 0x1d45c)
#3 0x000077beabfd261c pa_mainloop_iterate (libpulse.so.0 + 0x2761c)
#4 0x000077beabfd26d1 pa_mainloop_run (libpulse.so.0 + 0x276d1)
#5 0x000077beabfe2bf2 n/a (libpulse.so.0 + 0x37bf2)
#6 0x000077beabf802b7 n/a (libpulsecommon-17.0.so + 0x5c2b7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1949:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1882:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2535:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bed4ace0c0 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce0c0)
#3 0x000077bed6219cca n/a (libQt6Quick.so.6 + 0x419cca)
#4 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2470:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2466:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2467:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1995:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2475:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2472:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1898:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1866:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a3a4e0 _ZN7QThread4execEv (libQt6Core.so.6 + 0x23a4e0)
#6 0x000077bed5775dfe n/a (libQt6DBus.so.6 + 0x2ddfe)
#7 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#8 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#9 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1871:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed6e02277 n/a (libQt6WaylandClient.so.6 + 0x60277)
#2 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1881:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2490:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2489:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2493:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2488:
#0 0x000077be78ae8c2a n/a (libavcodec.so.60 + 0x2e8c2a)
#1 0x000077be78b36a11 n/a (libavcodec.so.60 + 0x336a11)
#2 0x000077be78b3759c n/a (libavcodec.so.60 + 0x33759c)
#3 0x000077be78b3f1c9 n/a (libavcodec.so.60 + 0x33f1c9)
#4 0x000077be78de1855 n/a (libavcodec.so.60 + 0x5e1855)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1895:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2551:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1846:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bed4ace0c0 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce0c0)
#3 0x000077bed621641d n/a (libQt6Quick.so.6 + 0x41641d)
#4 0x000077bed604e060 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x24e060)
#5 0x000077bed66fc55c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc55c)
#6 0x000077bed4944e38 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144e38)
#7 0x000077bed4fbc7dc _ZN15QPlatformWindow20deliverUpdateRequestEv (libQt6Gui.so.6 + 0x1bc7dc)
#8 0x000077bed498c0ff _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c0ff)
#9 0x000077bed66fc55c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc55c)
[#10](/issue/ValveSoftware/Proton/10) 0x000077bed4944e38 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144e38)
[#11](/issue/ValveSoftware/Proton/11) 0x000077bed49451fb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1451fb)
[#12](/issue/ValveSoftware/Proton/12) 0x000077bed4ba460c n/a (libQt6Core.so.6 + 0x3a460c)
[#13](/issue/ValveSoftware/Proton/13) 0x000077bed347aa89 n/a (libglib-2.0.so.0 + 0x5ca89)
[#14](/issue/ValveSoftware/Proton/14) 0x000077bed34dc9b7 n/a (libglib-2.0.so.0 + 0xbe9b7)
[#15](/issue/ValveSoftware/Proton/15) 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
[#16](/issue/ValveSoftware/Proton/16) 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
[#17](/issue/ValveSoftware/Proton/17) 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
[#18](/issue/ValveSoftware/Proton/18) 0x000077bed494945d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14945d)
[#19](/issue/ValveSoftware/Proton/19) 0x000056e86fa492a3 n/a (plasmashell + 0x272a3)
[#20](/issue/ValveSoftware/Proton/20) 0x000077bed4239c88 n/a (libc.so.6 + 0x25c88)
[#21](/issue/ValveSoftware/Proton/21) 0x000077bed4239d4c __libc_start_main (libc.so.6 + 0x25d4c)
[#22](/issue/ValveSoftware/Proton/22) 0x000056e86fa49a65 n/a (plasmashell + 0x27a65)
Stack trace of thread 1896:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2461:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2330:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 3374:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2495:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1870:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed6e02277 n/a (libQt6WaylandClient.so.6 + 0x60277)
#2 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2216:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2494:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1963:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2004:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2499:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1958:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2464:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1899:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2497:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2218:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2479:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bdba4960ce n/a (radeonsi_drv_video.so + 0x960ce)
#3 0x000077bdba8f729c n/a (radeonsi_drv_video.so + 0x4f729c)
#4 0x000077bdba49602d n/a (radeonsi_drv_video.so + 0x9602d)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2553:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2213:
#0 0x000077bed4327e9d syscall (libc.so.6 + 0x113e9d)
#1 0x000077bec5e6c81b n/a (radeonsi_dri.so + 0x6c81b)
#2 0x000077bec5e74ff1 n/a (radeonsi_dri.so + 0x74ff1)
#3 0x000077bec66d9b16 n/a (radeonsi_dri.so + 0x8d9b16)
#4 0x000077bec641fe51 n/a (radeonsi_dri.so + 0x61fe51)
#5 0x000077bec5f06937 n/a (radeonsi_dri.so + 0x106937)
#6 0x000077bec5e320fb n/a (radeonsi_dri.so + 0x320fb)
#7 0x000077bece72dff9 n/a (libEGL_mesa.so.0 + 0x24ff9)
#8 0x000077bece72245b n/a (libEGL_mesa.so.0 + 0x1945b)
#9 0x000077bece715c09 n/a (libEGL_mesa.so.0 + 0xcc09)
[#10](/issue/ValveSoftware/Proton/10) 0x000077becf8b01da _ZN15QtWaylandClient17QWaylandGLContext11swapBuffersEP16QPlatformSurface (libQt6WaylandEglClientHwIntegration.so.6 + 0xa1da)
[#11](/issue/ValveSoftware/Proton/11) 0x000077bed52c912d n/a (libQt6Gui.so.6 + 0x4c912d)
[#12](/issue/ValveSoftware/Proton/12) 0x000077bed516ebce _ZN4QRhi8endFrameEP13QRhiSwapChain6QFlagsINS_12EndFrameFlagEE (libQt6Gui.so.6 + 0x36ebce)
[#13](/issue/ValveSoftware/Proton/13) 0x000077bed621977a n/a (libQt6Quick.so.6 + 0x41977a)
[#14](/issue/ValveSoftware/Proton/14) 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
[#15](/issue/ValveSoftware/Proton/15) 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
[#16](/issue/ValveSoftware/Proton/16) 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2478:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bdba4960ce n/a (radeonsi_drv_video.so + 0x960ce)
#3 0x000077bdba8f729c n/a (radeonsi_drv_video.so + 0x4f729c)
#4 0x000077bdba49602d n/a (radeonsi_drv_video.so + 0x9602d)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2501:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2219:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 3375:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1999:
#0 0x000077bed431c39d __poll (libc.so.6 + 0x10839d)
#1 0x000077bed34dc8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
#2 0x000077bed3479f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
#3 0x000077bed4ba28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
#4 0x000077bed494f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
#5 0x000077bed4a40e00 _ZN7QThread3runEv (libQt6Core.so.6 + 0x240e00)
#6 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#7 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#8 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2492:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2485:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bdba4960ce n/a (radeonsi_drv_video.so + 0x960ce)
#3 0x000077bdba8f729c n/a (radeonsi_drv_video.so + 0x4f729c)
#4 0x000077bdba49602d n/a (radeonsi_drv_video.so + 0x9602d)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2540:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2262:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2263:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 6455:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2332:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2496:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2469:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077be78de19ae n/a (libavcodec.so.60 + 0x5e19ae)
#3 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#4 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2541:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2329:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bed4ace0c0 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce0c0)
#3 0x000077bed6219cca n/a (libQt6Quick.so.6 + 0x419cca)
#4 0x000077bed4ac96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 1886:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 3370:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bec5e975ae n/a (radeonsi_dri.so + 0x975ae)
#3 0x000077bec5e7535c n/a (radeonsi_dri.so + 0x7535c)
#4 0x000077bec5e974dd n/a (radeonsi_dri.so + 0x974dd)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
Stack trace of thread 2457:
#0 0x000077bed42a34e9 n/a (libc.so.6 + 0x8f4e9)
#1 0x000077bed42a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
#2 0x000077bdba4960ce n/a (radeonsi_drv_video.so + 0x960ce)
#3 0x000077bdba8f729c n/a (radeonsi_drv_video.so + 0x4f729c)
#4 0x000077bdba49602d n/a (radeonsi_drv_video.so + 0x9602d)
#5 0x000077bed42a6ded n/a (libc.so.6 + 0x92ded)
#6 0x000077bed432a0dc n/a (libc.so.6 + 0x1160dc)
ELF object binary architecture: AMD x86-64
I truncated this log a little since I think the imporatnt part starts when I started the game. If whole log is needed please let me know.
Hello @hyperstown, there's a decent chance that you're seeing a video driver issue.
Please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
@hyperstown Any chance you can try Mesa 24.1? I think it should fix the issue you describe.
Upgrading to Mesa 24.1 solved the issue! Thanks @pixelcluster for the solution and everyone for help! Game now works flawlessly.
Current Proton Experimental (Proton: 1722351075 experimental-9.0-20240730) appears to have introduced a regression for Shadow of the Tomb Raider DX12 at least on mesa radv, initially reported at https://github.com/HansKristian-Work/vkd3d-proton/issues/2054 but apparently has nothing to do with vkd3d-proton despite the misleading error message about not being able to compile the shaders (note: vkd3d != vkd3d-proton).
Three days ago, with the previous Proton Experimental build (https://github.com/ValveSoftware/Proton/releases/tag/experimental-9.0-20240719) the game ran without any issue on DX12 as it does when switching to Proton 9.0-2. On current Proton Experimental only DX11 version still works.
Please see https://github.com/HansKristian-Work/vkd3d-proton/issues/2054 for logs and details.
Edit: Add references to the vkd3d bump potentionally causing/introducing the issue:
- https://github.com/ValveSoftware/Proton/commit/9682fbb46472940222338c4221432fda30d6b952
- https://github.com/ValveSoftware/vkd3d/compare/a16b9dffda9becb1dbcad476c38b78f2144f35b4...68b7f9df310a27fb8e4ebac48a1452570263ac08
- https://github.com/ValveSoftware/Proton/wiki/Changelog/_compare/dc18954e489159ef74204c96a2776a78a62623ae...40018f3cc5aa56867e80448532a45800fbd1f52c#diff-c275fec9c453c2a42515bc5ab47e30fa4130ff1426aef2f6e000a9a34e122cb8R15
Updated vkd3d-shader to vkd3d-1.12-89-[g68b7f9df]
For searchability:
err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
err:d3dcompiler:D3DCompile2 Shader log:
err:d3dcompiler:D3DCompile2 <anonymous>:1:167: E5015: Multiple buffers bound to space 0, index 0.
err:d3dcompiler:D3DCompile2 <anonymous>:1:97: Buffer ColorConstantBuffer is already bound to space 0, index 0.
err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4.
err:d3dcompiler:D3DCompile2 Shader log:
err:d3dcompiler:D3DCompile2 <anonymous>:1:167: E5015: Multiple buffers bound to space 0, index 0.
err:d3dcompiler:D3DCompile2 <anonymous>:1:97: Buffer ColorConstantBuffer is already bound to space 0, index 0.
err:d3dcompiler:D3DCompile2
@tgurr Thank you for the regression report! I was easily able to repro and we are looking into it :)
With Proton 9.0-3 being out I tested this game again (DX12) and it now regressed compared to 9.0-2 where it was perfectly playable for me though not as much compared to Proton Experimental where it currently still crashes right away (due to the above mentioned https://github.com/ValveSoftware/vkd3d/compare/a16b9dffda9becb1dbcad476c38b78f2144f35b4...68b7f9df310a27fb8e4ebac48a1452570263ac08). With 9.0-3 it now got some strange texture flickering: https://github.com/user-attachments/assets/9dde73e5-db91-4ecf-9a2f-0afd39466354
There sadly doesn't seem to be an easy way to roll back to 9.0-2 in Steam for testing to make sure it's indeed a Proton 9.0-3 regression. I last started the game on 9.0-2 some time ago and there of course have been updates to other parts on my system in the meantime like the kernel, mesa, linux-firmware so that ones can't be ruled out either. Since vkd3d-shader hasn't been updated for 9.0-3 this might also indeed be an issue with vkd3d-proton instead of vkd3d-shader this time. Please verify and advise if I need to report a bug to vkd3d(-proton) about it.
Edit: adding additional infos about system: 7800xt, kernel-6.11.0, mesa-24.2.3 (radv), linux-firmware-20240909
Started playing under Proton. It appears that, at least on Steam Deck LCD, the Level of Detail is semi-broken ,as you'll see the fade-in becoming flickery, potentially affected by the lighting.
https://github.com/user-attachments/assets/e1dda450-1b5e-4a16-b956-46da46fa6305
This affects the current Proton 9.3 and GE-Proton 13.
Current workaround: set Level of Detail to High or Ultra, the bugged LoD still appears but should be lessen at a higher distance.
I just checked the LoD setting and I already had it on HIGH for the video attached above, setting it to ULTRA also doesn't make any difference for me as in it does flicker no matter what LoD setting I set on my machine.
@AL2009man another workaround would be to disable the DX12 usage in the launcher settings, the DX11 version works fine. No idea about the performance difference though especially in the regards to to Steam Deck where every percent counts. But could be worth a try as well.
With Proton 9.0-3 being out I tested this game again (DX12) and it now regressed compared to 9.0-2 where it was perfectly playable for me though not as much compared to Proton Experimental where it currently still crashes right away (due to the above mentioned ValveSoftware/[email protected]). With 9.0-3 it now got some strange texture flickering: https://github.com/user-attachments/assets/9dde73e5-db91-4ecf-9a2f-0afd39466354
This particular issue is resolved with https://github.com/HansKristian-Work/vkd3d-proton/pull/2127 and has been cherry-picked to 9.0-3. The just released 9.0-3c contains the fix.
Shadow of the Tomb Raider
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8611.
@witchlliee posted on 2025-04-16T23:18:08:
Compatibility Report
- Name of the game with compatibility issues: Shadow of the Tomb Raider
- Steam AppID of the game: 750920
System Information
- GPU: RX 6650 XT
- Video driver version: Mesa 25.0.3-2
- Kernel version: Linux 6.14.2-2-cachyos
- Link to full system information report as Gist: https://gist.github.com/witchlliee/acfa6672b69699b22716eeea70991652
- Proton version: GE-Proton9-27
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.
Symptoms
The game freezes at this exact spot and continue in this state for a few seconds before running again:
Reproduction
I'm here to report a regression using the dualsense in the game. Now the camera move all the way by itself and Lara aims the weapon, all by itself, basically analog R and L2 button are working by themselves. Here is a log:
Proton versions
ge-proton9-27x1 2025-04proton experimentalx8 2024-09proton 9.0-3x2 2024-09proton 9.3x1 2024-09proton 9.0-2x1 2024-08proton 7.0-5x1 2023-02proton 7.0-6x1 2023-02proton 5.13x2 2020-12proton 4.11-9x1 2019-12proton 4.11x2 2019-09proton 4.2x3 2019-06proton 4.2-3x1 2019-04proton 4.2-2x2 2019-04proton 3.16x4 2019-03proton 3.16-6x3 2019-01
Launch options
PROTON_LOG=1x3 2024-06VKD3D_CONFIG=dxrx3 2021-10VKD3D_CONFIG=dxr11.x1 2021-10PROTON_ENABLE_NVAPI=1x2 2021-10PROTON_HIDE_NVIDIA_GPU=0x2 2021-10VKD3D_CONFIG=dxr.x2 2021-10WINEDLLOVERRIDES="dxgi=n"x2 2019-12PROTON_LOG=1`x1 2019-07PROTON_DUMP_DEBUG_COMMANDS=1x2 2019-04PROTON_USE_WINED3D=1.x1 2019-04PROTON_DUMP_DEBUG_COMMANDS=1`x1 2019-04PROTON_USE_WINED3D=1x1 2019-03
Launch lines
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command%x2 2021-10WINEDLLOVERRIDES="dxgi=n" %command%x2 2019-12PROTON_USE_WINED3D=1 %command%x1 2019-03
Upstream links
- ValveSoftware/Proton/issues/8611x1 2025-04
- HansKristian-Work/vkd3d-proton/pull/2127x1 2024-09
- HansKristian-Work/vkd3d-proton/issues/2054x1 2024-08
- ValveSoftware/Proton/issues/6566x1 2023-02
- doitsujin/dxvk/issues/1152x1 2019-09
- ValveSoftware/Proton/issues/3045x1 2019-09
- ValveSoftware/steam-for-linux/issues/6045x1 2019-04
- ValveSoftware/Proton/issues/1739x1 2018-10
DLLs
dxgi.dllx1 2021-07gfesdk.dllx1 2019-04
Compatibility Report
System Information
I confirm:
steam-750920.log
Symptoms
Low FPS on 4K normal preset (20-30 FPS)
Random crashes when I launch the game.
Reproduction
Gameplay video
https://youtu.be/lVjLifLc2g0
https://youtu.be/mCZK73dmJzg