https://bugs.kde.org/show_bug.cgi?id=509870
--- Comment #9 from [email protected] --- (In reply to steve_garnier from comment #8) > (In reply to David Redondo from comment #7) > > Sorry I can't tell you a way to check if something has crashed I am not > > using kubuntu please check somewhere else how to see crash reports on > > Kubuntu. Without a bakxtrace this is sadly not actionable for us > > I understand, David. I went to askubuntu.com to ask and saw that they have > an AI assistant in the left sidebar. I clicked on that and was taken to > stackoverflow.ai where I very carefully described the issue and asked about > this debug problem. The AI gave me a lot of detailed > information/instructions, so I will try to find the time to do this. > > All that being said, I've been doing a lot of reading and listening to other > users at kubuntuforums.net, and I suspect this is an issue with Wayland and > my Nvidia driver. (I suspect that the Nvidia issue might be a system issue, > which is why it hasn't core dumped.) I've been told by one user who was > seeing similar issues that he went to Nvidia and downloaded and installed > the latest Nvidia driver to correct a lot of issues. I've also heard that > Wayland was fixed, too, but those fixes haven't trickled down into Kubuntu > yet, which would imply that the issues I am seeing have already been > addressed elsewhere. > > My motherboard is an MSI PRO B650-VC WIFI III and my GPU is an Nvidia > GeForce RTX 5070, so this is pretty new hardware. It might take a little > time for software/firmware to catch up. > > I'll let you know if I generate a core dump. If not, I'm not going to fret > too long. I just won't depend on Wayland until there's a fix. > Thanks, > Steve I did my best to allow user AND system-level core dumps to occur. This included ensuring the installation of systemd-coredump, modifying /etc/systemd/system.conf and /etc/systemd/user.conf while setting DefaultLimitCORE=infinity, ensuring that /etc/systemd/coredump.conf included [Coredump] Storage=external MaxUse=2G (or greater) , ensuring that /proc/sys/kernel/core_pattern contained |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %e , ensuring "ulimit -c unlimited" is applied and enforced, then executing sudo systemctl daemon-reexec sudo systemctl restart systemd-coredump sudo systemctl daemon-reload So I'm going to assume that I did pretty much everything I could do to enable core dumps from user and system processes. I then recreated the problem issue. I then verified that there were no core dumps using "coredumpctl list". I performed "ps uax" and grep'd the output for [Pp]lasma and [Ww]ayland. I executed "top" and saw nothing out of the ordinary. Nothing slapped me in the face as a problem, other than the disgusting problem issue was still present, making working inside Wayland to be between a PITA and impossible. And after doing all this, I executed sudo journalctl -b 0 -r and observed many replicants of the following line Oct 04 15:59:41 <hostname> systemd[13365]: drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system). As such, I must assume that debugging this issue is beyond my current capability and knowledge. -- You are receiving this mail because: You are watching all bug changes.
