| Summary: | Spectacle Crash sometimes.... | ||
|---|---|---|---|
| Product: | [Applications] Spectacle | Reporter: | Dhirendra Pal Singh <mazanand1976> |
| Component: | General | Assignee: | Noah Davis <noahadvs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kde, quinnj |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 23.08.5 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Dhirendra Pal Singh
2025-09-08 09:06:00 UTC
Unfortunately, you do not have debug symbols installed, so there isn't much information that can be gathered from the backtrace (notice all the lines containing "in ???") 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 This must be a miracle that I have this email with the bug info. See, in reality, my laptop had frozen, and I was unable to file this bug. The process got hung, and after letting it run for 1 day in the hopes that this bug filing would be complete, I finally had to close the bug filing process, without getting any bug ID. I am at shock and awe. Might I suggest that, please, close this bug, and when I get this problem again in future, I will try to refile and will attach the debug symbols for sure. If I can close this bug, I would do it gladly myself. Tons of Thanks as well as Tons of Regards Dhirendra ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Created attachment 185457 [details]
New crash information added by DrKonqi
spectacle (23.08.5) using Qt 5.15.13
Ubuntu 24.04
I was trying to take a screenshot. This is the first time I've hit this crash. I didn't have debug symbols installed either unfortunately.
-- Backtrace (Reduced):
#4 0x00005783a793b417 in ??? ()
#5 0x00007bbb105171aa in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007bbb1050624b in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007bbb11d6bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8 0x00007bbb104d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
I've installed qt5core debug symbols to hopefully capture more data if it happens again. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. |