https://bugs.kde.org/show_bug.cgi?id=499054

            Bug ID: 499054
           Summary: System crash after going to sleep whilst playing game
    Classification: Plasma
           Product: plasmashell
           Version: 6.2.5
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: generic-crash
          Assignee: plasma-b...@kde.org
          Reporter: xicomaia2...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.2.5)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.1
Frameworks Version: 6.10.0
Operating System: Linux 6.12.9-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 41 (KDE Plasma)"
DrKonqi: 6.2.5 [CoredumpBackend]

-- Information about the crash:
If my computer goes to sleep whilst a game is open (has been happening with
Farming Sim 25 on Proton), it just completely crashes when I try to wake it up
and does all sorts of weird things. So far, it has happened 3 times:
First time, it just didn't do anything when I woke it up and I had to manually
reset it. Doing things like alt+f4 and ctrl+alt+del did nothing
Second time, I managed to somehow get back into plasma using the sysrq keys
(not sure which one did the trick). Before I got back into plasma, the computer
was just displaying a white screen or a blank screen with a white box when I
clicked a key or something.
Third time, just now, also a white screen but it apparently (somewhat)
recovered since it managed to show sddm a few minutes after waking it up and
without pressing anything. I managed to log in however it was extremely buggy,
the cursor was just a white box, and it was unbearably laggy until I did
alt+tab which somehow fixed it.

All 3 times, when I manage to get into plasma, I am greeted with a bunch of
crash notices from Plasma, KWin and related services, this one being one of
them.


System Details
Ryzen 7 5700X3D
RX 6700XT
16GB RAM

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  0x00007ff37ca7f163 in __pthread_kill_internal (threadid=<optimized out>,
signo=6) at pthread_kill.c:78
#7  0x00007ff37ca25fde in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x00007ff37ca0d942 in __GI_abort () at abort.c:79
#9  0x00007ff359bbc880 in amdgpu_ctx_set_sw_reset_status (rwctx=<optimized
out>, status=status@entry=PIPE_INNOCENT_CONTEXT_RESET,
format=format@entry=0x7ff35ad3d720 "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

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to