https://bugs.kde.org/show_bug.cgi?id=501987
--- Comment #3 from Rehat Singh <rehatsingh2...@gmail.com> --- Hello, the issue seems to have been gone after a recent kernel+driver update Kernel-6.14(compiled from source) Driver-nvidia proprietary 570.133.07 On Wed, Mar 26, 2025, 2:29 AM TraceyC <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=501987 > > TraceyC <kde...@tlcnet.info> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |BACKTRACE > CC| |kde...@tlcnet.info > Status|REPORTED |NEEDSINFO > > --- Comment #2 from TraceyC <kde...@tlcnet.info> --- > Thank you for the bug report. Unfortunately the backtrace is incomplete and > missing debug symbols for the following lines that we need to figure out > exactly what's going wrong: > > 9 0x00007f88852376cc in ??? () at /usr/lib/libwayland-client.so.0 > #11 0x00007f88836d0721 in ??? () at /usr/lib/libQt6WaylandClient.so.6 > #12 0x00007f88826f223b in ??? () at /usr/lib/libQt6Core.so.6 > > Could you please install debug symbols and attach a new symbolicated > backtrace > generated by using `coredumpctl gdb` in a terminal window? See > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. Thanks again! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.