Compatibility Report

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

System Information

GPU: RX 7900 XTX
Driver/LLVM version: Mesa 22.3.4; LLVM 15.0.7 (also tested latest mesa 23.1-devel)
Kernel version: 6.1.10-zen1
Link to full system information report as Gist: https://gist.github.com/kzdixon/939144ca6c2c3a1928b90c38b0f05b59
Proton version: Experimental (Bleeding Edge), GE-Proton7-49

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.

Proton Log (had to compress, took a bit to get it to crash but the incorrect shaders on close NPCs was consistently appearing the entire time): steam-990080.log.zip

Symptoms

Very often, characters will load in their shaders for clothes, etc., and when getting closer to the player will have them unload and become completely black. This typically persists forever unless a scene reloads, but there is another issue with loading scenes after seeing this occur...
Loading scenes (especially so after seeing the black shaders) seems to oftentimes lead to a complete crash of the game. This means loading for a quest, fast travel, or going to the main menu to try and reload a save.

Reference Pictures:

![2023-02-07-17:54:53-screenshot](https://user-images.githubusercontent.com/10300293/217394257-1d6d5da0-acde-4de9-80c3-1de4d9bb8bb1.png) ![2023-02-07-19:00:29-screenshot](https://user-images.githubusercontent.com/10300293/217394531-0bc0f156-1cc7-4c56-9ef0-1366132930c9.png) ![2023-02-07-19:00:36-screenshot](https://user-images.githubusercontent.com/10300293/217394544-0a0e42b2-b15d-4162-8ae6-8fd0b532b2a9.png)

Reproduction

Simply playing the game on a RX 7900 XTX with Proton using the latest stable driver release seems to result in this issue pretty regularly.

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

Anyone any ideas what's happening here?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The game is almost perfect right now.

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

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

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

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

Hopefully that helps others

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

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

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

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

Using no options with Proton Experimental and the mmap fix. However the game seems to cause a driver crash every hour or two. I have an Asrock Radeon RX 6900XT OC FORMULA and an AMD Ryzen 7700X.

``` Feb 19 21:41:29 hotbox kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=39657845, emitted seq=39657847 Feb 19 21:41:29 hotbox kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 57110 thread HogwartsLegacy. pid 57110 Feb 19 21:41:29 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin! Feb 19 21:41:29 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: free PSP TMR buffer Feb 19 21:41:29 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset Feb 19 21:41:29 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset Feb 19 21:41:29 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset Feb 19 21:41:29 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume Feb 19 21:41:29 hotbox kernel: [drm] VRAM is lost due to GPU reset! Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming... Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1 Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done Feb 19 21:41:30 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(2) succeeded! Feb 19 21:41:30 hotbox kernel: amdgpu_cs_ioctl: 73 callbacks suppressed Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:41:30 hotbox kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 19 21:42:59 hotbox kernel: [drm] amdgpu kernel modesetting enabled. Feb 19 21:42:59 hotbox kernel: amdgpu: vga_switcheroo: detected switching method \_SB_.PCI0.GP17.VGA_.ATPX handle Feb 19 21:42:59 hotbox kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Feb 19 21:42:59 hotbox kernel: amdgpu: Virtual CRAT table created for CPU Feb 19 21:42:59 hotbox kernel: amdgpu: Topology: Add CPU node Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007) Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT Feb 19 21:42:59 hotbox kernel: amdgpu: ATOM BIOS: 113-EXT800221-L02 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented. Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented. Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used) Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF Feb 19 21:42:59 hotbox kernel: [drm] amdgpu: 16368M of VRAM memory ready Feb 19 21:42:59 hotbox kernel: [drm] amdgpu: 15610M of GTT memory ready. Feb 19 21:42:59 hotbox kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: STB initialized to 2048 entries Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully! Feb 19 21:42:59 hotbox kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart Feb 19 21:42:59 hotbox kernel: amdgpu: sdma_bitmap: ffff Feb 19 21:42:59 hotbox kernel: amdgpu: HMM registered 16368MB device memory Feb 19 21:42:59 hotbox kernel: amdgpu: SRAT table not found Feb 19 21:42:59 hotbox kernel: amdgpu: Virtual CRAT table created for GPU Feb 19 21:42:59 hotbox kernel: amdgpu: Topology: Add dGPU node [0x73af:0x1002] Feb 19 21:42:59 hotbox kernel: kfd kfd: amdgpu: added device 1002:73af Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: SE 4, SH per SE 2, CU per SH 10, active_cu_number 80 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: amdgpu: Using BOCO for runtime pm Feb 19 21:42:59 hotbox kernel: [drm] Initialized amdgpu 3.49.0 20150101 for 0000:03:00.0 on minor 0 Feb 19 21:42:59 hotbox kernel: fbcon: amdgpudrmfb (fb0) is primary device Feb 19 21:42:59 hotbox kernel: amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: enabling device (0006 -> 0007) Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: Fetched VBIOS from VFCT Feb 19 21:42:59 hotbox kernel: amdgpu: ATOM BIOS: 102-RAPHAEL-006 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: PCIE atomic ops is not supported Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF Feb 19 21:42:59 hotbox kernel: [drm] amdgpu: 512M of VRAM memory ready Feb 19 21:42:59 hotbox kernel: [drm] amdgpu: 15610M of GTT memory ready. Feb 19 21:42:59 hotbox kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: PSP runtime database doesn't exist Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: PSP runtime database doesn't exist Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: Will use PSP to load VCN firmware Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: RAS: optional ras ta ucode is not available Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: RAP: optional rap ta ucode is not available Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: smu driver if version = 0x00000004, smu fw if version = 0x00000005, smu fw program = 0, smu fw version = 0x00544900 (84.73.0) Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: SMU driver if version not matched Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: SMU is initialized successfully! Feb 19 21:42:59 hotbox kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart Feb 19 21:42:59 hotbox kernel: amdgpu: sdma_bitmap: 3 Feb 19 21:42:59 hotbox kernel: amdgpu: HMM registered 512MB device memory Feb 19 21:42:59 hotbox kernel: amdgpu: SRAT table not found Feb 19 21:42:59 hotbox kernel: amdgpu: Virtual CRAT table created for GPU Feb 19 21:42:59 hotbox kernel: amdgpu: Topology: Add dGPU node [0x164e:0x1002] Feb 19 21:42:59 hotbox kernel: kfd kfd: amdgpu: added device 1002:164e Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 2, active_cu_number 2 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 Feb 19 21:42:59 hotbox kernel: [drm] Initialized amdgpu 3.49.0 20150101 for 0000:6b:00.0 on minor 1 Feb 19 21:42:59 hotbox kernel: amdgpu 0000:6b:00.0: [drm] Cannot find any crtc or sizes Feb 19 21:43:00 hotbox kernel: snd_hda_intel 0000:6b:00.1: bound 0000:6b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) Feb 19 21:43:00 hotbox kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) Feb 19 21:43:00 hotbox systemd[1]: Starting Detect the available GPUs and deal with any system changes... Feb 19 21:43:00 hotbox systemd[1]: gpu-manager.service: Deactivated successfully. Feb 19 21:43:00 hotbox systemd[1]: Finished Detect the available GPUs and deal with any system changes. Feb 19 21:43:00 hotbox kernel: amdgpu 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none Feb 19 21:43:00 hotbox kernel: amdgpu 0000:6b:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none Feb 19 21:43:02 hotbox dbus-daemon[1131]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' requested by ':1.45' (uid=1000 pid=2004 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev") (using servicehelper) Feb 19 21:43:02 hotbox dbus-daemon[1131]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper' ```

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

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

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

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

PS5 controller on Hogwarts Legacy

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6553. @sdtsj posted on 2023-02-21T07:51:29:

Hello, Not 100% sure if someone reported this or not or if this is a proton problem but it is worth a try. When playing Hogwarts Legacy on PC (Windows 10) with PS5 controller connected with bluetooth, the game shows normal PS glyphs since the game supports them natively. However when I run the game on SteamDeck and connect the same controller to it, the game shows xbox glyphs. I have tried different layouts and even at one point I tried disabling the steam input to try to force the game to show PS glyphs but with no help. Thank you in advance in looking into this :)

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

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

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

Some examples (Proton Experimental):

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

I noticed that the gamepad name differs:

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

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

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

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

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

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

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

:astonished: My GPU has 16 GiB Screenshot_20230225_171837

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

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

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

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

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

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

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

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

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

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

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

~~Also tried the following:~~

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

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

Edit: had to delete RADV_DEBUG=hang

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

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

Increasing vm.max_map_count did not resolve my issue.

Full log here:

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

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

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

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

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

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

Hogwarts Legacy (990080) - Long loading times/ Blank screen

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6593. @NicolaiVdS posted on 2023-03-04T11:51:29:

Compatibility Report

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

System Information

GPU: RTX 3070
Driver/LLVM version: nvidia 525.89.02
Kernel version: 6.2.1-arch1-1
Link to full system information report as Gist: https://gist.github.com/NicolaiVdS/a5b6d847efe5f43cc91506985e7e7ac3
Proton version: GE-Proton7-49

I confirm:

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

steam-990080.log.zip

Symptoms

the game either takes ages to load to the main menu -> 5Min+ or it loads up i can hear the music but the screen is just blank

Reproduction

Simply playing the game on a RTX 3070 with Proton using the latest stable driver release seems to result in this issue pretty regularly.

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

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

This part stuck out:

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

Journal log from the moment I got kicked out:

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

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

Question:

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

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

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

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

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

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

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

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

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

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

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

I am on Arch linux on a nvidia2060 laptop

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

I am on Arch linux on a nvidia2060 laptop

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

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

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

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

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

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

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

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

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

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

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

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

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

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

steam-990080.log

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

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

@Blisto91

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

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

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

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

Did I do something wrong?

Edit: Steam System Information Gist

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

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

Here is the Gist Gist also included in Post above.

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

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

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

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

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

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

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

ValveSoftware / Proton

Hogwarts Legacy (990080) #6510

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction