Bug 502499 - Plasma Desktop, taskbar panel, and my program crash abruptly
Summary: Plasma Desktop, taskbar panel, and my program crash abruptly
Status: RESOLVED DUPLICATE of bug 493679
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.3.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-04-06 21:46 UTC by JackIV
Modified: 2025-04-07 21:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/121755/events/a9f4b7c3aaf04c458702be11f8676aea/


Attachments
New crash information added by DrKonqi (98.22 KB, text/plain)
2025-04-06 21:46 UTC, JackIV
Details

Note You need to log in before you can comment on or make changes to this bug.
Description JackIV 2025-04-06 21:46:13 UTC
Application: plasmashell (6.3.4)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.12.0
Operating System: Linux 6.13.9-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 41 (KDE Plasma)"
DrKonqi: 6.3.4 [CoredumpBackend]

-- Information about the crash:
When I am palying a modded version of Minecraft (mostly Vanilla but Perforamnce mods + shaders) on a Server when I am diging while udnerwater I sometimes crash. Both my monitors go black for a few seconds and all sound stops briefly. Then my monitors return but are frozen completely, with the sound from my other programs (Vesktop in this case) still working normally.  The enteriety of Plasma crahses shortly after and Minecraft also closes crashed witht he following message that I do not understant: "amdgpu: The CS has cancelled because the context is lost. This context is innocent. \nProcess crashed with exitcode 6." 

This has happened repeatably but randomly not imidiately happening when I mine underwater. I had this issue two or three times IN A ROW a week ago but just updated my system with the Discover app and restarted it without testing if it fixed the problem (I had to go for the evening). I have played minecraft since and done lots of gameplay including mining, but not udnerwater at all. Now I sit down to play some Minecraft and go mining in an underwater cave once again and I get the same halting crash. I restarted minecraft ignoring the crash because I died and wanted to get my items back on the server before they were lost (same as the times prior). I go to the same location and after trying to continue the game by mining more underwater again. I am met with the same crash again. This time I have followed the plasmashell crash prompts.

If you need details about the mods I was using on my minecraft instance I can provide that as many of the affect the game rendering pipeline and other claimed-"optimized" calls directly to the gpu.

This is very disruptive of my gameplay and has lost me lots of time spend on my free time so I am pretty frustrated, but I just want to try to get this fixed.

The crash can be reproduced sometimes.

-- 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  0x00007fd22aa7fbc3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x00007fd22aa26f9e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fd22aa0e942 in __GI_abort () at abort.c:79
#9  0x00007fd205bbec90 in amdgpu_ctx_set_sw_reset_status (rwctx=<optimized out>, status=status@entry=PIPE_INNOCENT_CONTEXT_RESET, format=format@entry=0x7fd206dae420 "amdgpu: The CS has cancelled because the context is lost. This context is innocent.\n") at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:474


Reported using DrKonqi
Comment 1 JackIV 2025-04-06 21:46:14 UTC
Created attachment 180049 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 TraceyC 2025-04-07 20:28:29 UTC
Searchable backtrace

Thread 1 (Thread 0x7fd214ba86c0 (LWP 29205)):
[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  0x00007fd22aa7fbc3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x00007fd22aa26f9e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fd22aa0e942 in __GI_abort () at abort.c:79
#9  0x00007fd205bbec90 in amdgpu_ctx_set_sw_reset_status (rwctx=<optimized out>, status=status@entry=PIPE_INNOCENT_CONTEXT_RESET, format=format@entry=0x7fd206dae420 "amdgpu: The CS has cancelled because the context is lost. This context is innocent.\n") at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:474
#10 0x00007fd205bc2c04 in amdgpu_cs_submit_ib<(queue_type)0> (job=job@entry=0x7fd10c012940, gdata=gdata@entry=0x0, thread_index=thread_index@entry=0) at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:1995
#11 0x00007fd2056b2161 in util_queue_thread_func (input=input@entry=0x5648475a8900) at ../src/util/u_queue.c:294
#12 0x00007fd2056e765c in impl_thrd_routine (p=<optimized out>) at ../src/c11/impl/threads_posix.c:43
#13 0x00007fd22aa7dba8 in start_thread (arg=<optimized out>) at pthread_create.c:448
#14 0x00007fd22ab01b8c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Comment 3 TraceyC 2025-04-07 20:35:44 UTC
It looks like the root cause of this bug is in the AMD driver, based on the backtrace. You could open a bug report about this at [https://gitlab.freedesktop.org/drm/amd/-/issues](https://gitlab.freedesktop.org/drm/amd/-/issues) so the AMD developers can take a look. Unfortunately, I don't think there's anything KDE can do.
Comment 4 Zamundaaa 2025-04-07 21:49:04 UTC
*** This bug has been marked as a duplicate of bug 493679 ***