https://bugs.kde.org/show_bug.cgi?id=508534
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |BACKTRACE Status|REPORTED |NEEDSINFO --- Comment #11 from TraceyC <[email protected]> --- (In reply to taormineitor93 from comment #10) > I installed all the required kwin packages, valgrid and everything requested > in the first guide.. I got help from both gemini and chatgpt at the same > time and I installed everything I could install, and I can't install > anything more than that.. I tried other kde distros in the meantime I tried > to enlarge the fonts and the scale and I see that the error only occurs with > nobara. A word of caution about ChatGPT, Gemini and other AI tools. They are known to provide incorrect information sometimes. It looks like the reason the backtrace doesn't have anything is that it was run on a crash that no longer had a crash dump file. It was run on process ID 8207 ··• sudo coredumpctl gdb 8207 However that has no coredump file. You can see this in the coredumpctl --list output ▒▓ 🎩 ▓▒░ ◦•···································································•◦ ░▒▓ 38ms ▓▒░ ··• coredumpctl --reverse Wed 2025-08-27 08:19:19 CEST 8207 1000 1001 SIGSEGV inaccessible /usr/bin/kwin_wayland - You can see there's a dash at the end of the row. That says there is no coredump file. If the coredump file exists, there will be a size at the end of the row, like you can see here: Wed 2025-08-27 08:18:40 CEST 5871 1000 1001 SIGSEGV present /usr/libexec/drkonqi 20.5K Unfortunately, all the crashes shown in the coredumpctl output have no coredump file. Without that, you won't be able to get a good backtrace, and unfortunately we can't investigate without one. Since the crashes aren't happening with other distros, the problem may be in the Nobara setup somewhere. You might try asking the Nobara folks for help. They might also be able to help you get coredump files to properly generate. -- You are receiving this mail because: You are watching all bug changes.
