Application: kpat (21.12.3) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-78-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I had just finished a Mod3 patience game and closed the app by clicking on the window close (X) box. At this point the application crashed. I was also using the MS Edge browser and Thunderbird. The crash can be reproduced sometimes. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault [KCrash Handler] #4 0x00007f57082137c0 in ?? () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #5 0x00007f5708214f29 in KSharedDataCache::find(QString const&, QByteArray*) const () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #6 0x00007f5708763777 in ?? () from /lib/x86_64-linux-gnu/libkcardgame.so #7 0x00007f570701441e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f5707b21713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x00007f5706fe6e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f5706fe9f27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f5707040a67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f5704a32d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007f5704a88258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007f5704a303e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007f57070400b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f5706fe575b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f5706fedcf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00005632299e0333 in ?? () #19 0x00007f5706816d90 in __libc_start_call_main (main=main@entry=0x5632299ddff0, argc=argc@entry=3, argv=argv@entry=0x7ffd4a2b6608) at ../sysdeps/nptl/libc_start_call_main.h:58 #20 0x00007f5706816e40 in __libc_start_main_impl (main=0x5632299ddff0, argc=3, argv=0x7ffd4a2b6608, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd4a2b65f8) at ../csu/libc-start.c:392 #21 0x00005632299e16e5 in ?? () [Inferior 1 (process 8751) detached] Reported using DrKonqi
Thank you for the bug report! Unfortunately the backtrace is incomplete since it is missing debug symbols and I cannot reproduce the bug myself. Could you please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. Thanks again!
Good evening Noah. Thank you for your reply. I have played 3 to 4 kpat/Mod 3 games per day hoping for a crash. Sadly I have not succeeded yet. I suspect that I might have to be patient until I get a crash. In the meantime I have been learning how to put the backtrace process together so when I do have a crash I'll be ready. Cheers James PS Is this one of those rare situations where you want to have a crash???! Noah Davis: > https://bugs.kde.org/show_bug.cgi?id=473136 > > Noah Davis <noahadvs@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > CC| |noahadvs@gmail.com > > --- Comment #1 from Noah Davis <noahadvs@gmail.com> --- > Thank you for the bug report! Unfortunately the backtrace is incomplete since > it is missing debug symbols and I cannot reproduce the bug myself. > Could you please install debug symbols, reproduce the crash, and attach a new > symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports > for details about how to do this. > Thanks again! > > -- > You are receiving this mail because: > You reported the bug.
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!
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!