Bug 495347 - Plasmashell always crashes on Dirt-Rally 2.0 (Proton verison 7.0-6)
Summary: Plasmashell always crashes on Dirt-Rally 2.0 (Proton verison 7.0-6)
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.2.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-10-25 15:24 UTC by Ethan
Modified: 2024-10-28 03:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (165.77 KB, text/plain)
2024-10-25 15:24 UTC, Ethan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ethan 2024-10-25 15:24:06 UTC
Application: plasmashell (6.2.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.7.2
Frameworks Version: 6.7.0
Operating System: Linux 6.11.4-201.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Forty)"
DrKonqi: 6.2.2 [CoredumpBackend]

-- Information about the crash:
Game will run fine, but as soon as you load into a rally stage and graphics are being rendered, it's prone to crash in the next few seconds. 
I have never got it to work after it began happening. Plasma 6.2 may have been the update that broke this game for me, but not entirely confident in saying that.

Some extra information:
 - Game has failed to run on other proton verisons (tried on proton 8 and experimental, and some GE-15)

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007f92c56a86d3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x00007f92c564fc4e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f92c5637902 in __GI_abort () at abort.c:79
#9  0x00007f92a9746240 in amdgpu_ctx_set_sw_reset_status (rwctx=<optimized out>, status=status@entry=PIPE_INNOCENT_CONTEXT_RESET, format=format@entry=0x7f92aa715088 "amdgpu: The CS has cancelled because the context is lost. This context is innocent.\n") at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:459


Reported using DrKonqi
Comment 1 Ethan 2024-10-25 15:24:07 UTC
Created attachment 175233 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-10-28 03:13:39 UTC
Thread 1 (Thread 0x7f92a8c006c0 (LWP 2373)):
[KCrash Handler]
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x00007f92c56a86d3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x00007f92c564fc4e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f92c5637902 in __GI_abort () at abort.c:79
#9  0x00007f92a9746240 in amdgpu_ctx_set_sw_reset_status (rwctx=<optimized out>, status=status@entry=PIPE_INNOCENT_CONTEXT_RESET, format=format@entry=0x7f92aa715088 "amdgpu: The CS has cancelled because the context is lost. This context is innocent.\n") at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:459
#10 0x00007f92a97496b0 in amdgpu_cs_submit_ib<false> (job=job@entry=0x7f91e8012d30, gdata=gdata@entry=0x0, thread_index=thread_index@entry=0) at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:1653
#11 0x00007f92a8e857e1 in util_queue_thread_func (input=input@entry=0x55cd36efd210) at ../src/util/u_queue.c:309
#12 0x00007f92a8ea886c in impl_thrd_routine (p=<optimized out>) at ../src/c11/impl/threads_posix.c:67
#13 0x00007f92c56a66d7 in start_thread (arg=<optimized out>) at pthread_create.c:447
#14 0x00007f92c572a60c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Comment 3 Nate Graham 2024-10-28 03:16:33 UTC
The crash backtrace indicates that the problem is in the AMD Mesa graphics drivers. Please read https://docs.mesa3d.org/bugs.html and submit a bug report for the Mesa developers. Thanks!