Are you on wayland by any chance? I had that same problem and it went away when I changed back to xorg (Debian 12 - KDE - AMD APU)
this post was submitted on 27 Jul 2023
31 points (97.0% liked)
Linux
45479 readers
1422 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I'd be happy to receive feedback on the downvote.
Probably a Winblows lover. I'll try to offset the down vote for you.
Not sure why you got downvoted. Maybe it was the missing period. You know how flaky people can be. Thanks for your comments though and hope life is treating you well otherwise.
that makes me think graphics driver maybe? Check dmesg output right after it happens, you might see something getting reset.
Yes I think I found it, kwin_wayland is segfault'ing randomly, causing the whole session to crash and restart.
Not sure how to fix that though ...
Please start a gdb console for the last crash with coredumpctl debug kwin_wayland, get a backtrace in there with "bt full" and create a bug report with the backtrace at bugs.kde.org
Are you using a distro with fairly recent packages? If not, then possibly you could try looking for supplementary sources that could provide more recent version. Just as an example, someone else mentioned having a similar issue on Debian. Debian tends to be very conservative about updating their packages and they may be quite outdated. (It's possible to be on the other side of the problem, with fast moving distros like Arch but they also tend to fix stuff pretty fast as well.)
Possibly worth considering that hardware can also cause random crashes, faulty RAM, overheating GPUs, CPUs, memory or overclocking stuff beyond its limits. Try checking sensors to make sure temperatures are in a reasonable range, etc.
You can also try to determine if the times it crashes have anything in common or anything unusual is happening. I.E. playing graphics intensive games, hardware video decoding, that kind of thing. Some distros have out of memory process killers set up that have been known to be too aggressive, and processes like the WM that can control a lot of memory will sometimes be a juicy target for them.
As you probably already know if you've been using Linux for a while, diagnosing problems is usually a process of elimination. So you need to eliminate as many other possibilities as you can. Also, it's general hard for people to help you with such limited information. We don't know the specific CPU, GPU, distribution, versions of software, what you were doing when it occurred, anything like that. So we can't eliminate many possibilities to give you more specific help. More information is almost always better when asking for technical help on the internet.
coredumpctl might help, it keeps track of whenever a process just ups and dies hard.
It looks like kwin_wayland is on there as "inaccessible" about the time it last happened
It's definitely kwin_wayland
view more: next ›