Bug 478925 - System randomly crashes
Summary: System randomly crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-23 10:17 UTC by chniucg
Modified: 2024-04-04 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
journal (135.07 KB, text/plain)
2023-12-23 10:17 UTC, chniucg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description chniucg 2023-12-23 10:17:02 UTC
Created attachment 164398 [details]
journal

SUMMARY
Sometimes my system completely freezes, playing the last few seconds of the music stream that was running, and having a black screen.

STEPS TO REPRODUCE
I don't know, it happens twice a day, sometimes more. And for me it seems random.

OBSERVED RESULT
The screen goes black, except for the screen above, which gets green.

EXPECTED RESULT
Not crash!

SOFTWARE/OS VERSIONS
Linux: 6.6.7-arch1-1 (64-bit)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Processor: 6 × Intel® Core™ i5-9600KF CPU @ 3.70GHz
Memory: 62,7 GiB of RAM
Graphics Platform: Wayland
Grahpics Processor: AMD Radeon RX 5600 XT

-- graphics driver
➜  ~ lspci | grep VGA
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev ca)
➜  ~ find /dev -group video
/dev/dri/card1
/dev/fb0
➜  ~ glxinfo | grep -i vendor
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
    Vendor: AMD (0x1002)
OpenGL vendor string: AMD

ADDITIONAL INFORMATION
Journal is in the attachment
Comment 1 chniucg 2023-12-23 10:23:26 UTC
The time it crashed I used: 
Spotify, IntelliJ, Discord, Prismlauncher, Minecraft, Thunderbird and Dolphin.
Note that Spotify as well as Discord were forced to use native wayland windows.

Discord start command: flatpak run --socket=wayland --branch=stable --arch=x86_64 --command=com.discordapp.Discord com.discordapp.Discord --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto

Spotify start command: flatpak run --socket=wayland --branch=stable --arch=x86_64 --command=spotify --file-forwarding com.spotify.Client @@u %U @@ --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations
Comment 2 Nate Graham 2024-02-16 00:13:20 UTC
Is the system still interactive when this happens? E.g. can you change the volume from the keyboard's volume keys?
Comment 3 chniucg 2024-02-16 08:14:57 UTC
(In reply to Nate Graham from comment #2)
> Is the system still interactive when this happens? E.g. can you change the
> volume from the keyboard's volume keys?

No, I can neither change the volume nor switch to another TTY.
I've now switched my setup a bit and since I've never experienced it again.

Before I had 4 screens now I got one.
Comment 4 Bug Janitor Service 2024-03-02 03:46:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 chniucg 2024-03-02 15:10:12 UTC
Just happened again. I noted that it most likely happens when under high load. Like playing a game, or compiling something.
Comment 6 Nate Graham 2024-03-04 17:23:12 UTC
Thanks, and sorry for not noticing your response earlier. Any chance you can upgrade to Plasma 6 and see if it still happens? If so, we can help you g et some logs for it.
Comment 7 chniucg 2024-03-05 07:34:01 UTC
(In reply to Nate Graham from comment #6)
> Thanks, and sorry for not noticing your response earlier. Any chance you can
> upgrade to Plasma 6 and see if it still happens? If so, we can help you g et
> some logs for it.

I encountered this issue on Plasma 5 which is why I enabled the testing repositories and switched to Plasma 6 since the second release candidate. It still occurs, but to a lesser extent than before. I'll try to trigger it.
Comment 8 Bug Janitor Service 2024-03-20 03:45:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2024-04-04 03:47:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!