Bug 512176

Summary: Spectacle crashed when started
Product: [Applications] Spectacle Reporter: Dhirendra Pal Singh <mazanand1976>
Component: GeneralAssignee: Noah Davis <noahadvs>
Status: NEEDSINFO BACKTRACE    
Severity: crash CC: kde, kdedev
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: What is going on my side of the situation, as explained in bug 509266
24 Hours later its still going on....

Description Dhirendra Pal Singh 2025-11-16 09:41:38 UTC 
Application: spectacle (23.08.5)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.14.0-35-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04.3 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
I think this might be it. I would wait for the developers to lead the way. I would want to build it from source hopefully the same that is with the distribution, and if for some reason not, then TOT. I hope this is the all the info supplied from the user POV.

The crash can be reproduced every time.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x00006142f72f594d in ??? ()
#5  0x00006142f72f746e in ??? ()
#6  0x00006142f72e07d9 in ??? ()
#7  0x000079a04f512e16 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00006142f7311381 in ??? ()
#9  0x000079a04f5171aa in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x000079a04f50624b in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x000079a050d6bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x000079a04f4d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x000079a04f5345ab in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x000079a04f534ed9 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x000079a04bd145c5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x000079a04bd73737 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x000079a04bd13a63 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x000079a04f535279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x000079a04f4d6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x000079a04f4df3e8 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00006142f72c18d3 in ??? ()
#22 0x000079a04ea2a1ca in __libc_start_call_main (main=main@entry=0x6142f72c0ea0, argc=argc@entry=1, argv=argv@entry=0x7ffd299719f8) at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x000079a04ea2a28b in __libc_start_main_impl (main=0x6142f72c0ea0, argc=1, argv=0x7ffd299719f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd299719e8) at ../csu/libc-start.c:360
#24 0x00006142f72c2865 in ??? ()
[Inferior 1 (process 270035) detached]

The reporter indicates this bug may be a duplicate of or related to bug 509266.

Reported using DrKonqi
Comment 1 Dhirendra Pal Singh 2025-11-16 10:15:13 UTC 
Created attachment 186838 [details]
What is going on my side of the situation, as explained in bug 509266

mazanand1976@stangray:~$ date
Sunday 16 November 2025 03:43:44 PM IST
Comment 2 Dhirendra Pal Singh 2025-11-17 11:45:32 UTC 
Created attachment 186881 [details]
24 Hours later its still going on....

I will kill the process once I am done filing this bug.....
Comment 3 TraceyC 2025-11-18 23:33:09 UTC 
Unfortunately, the new backtrace is still missing debug symbols, so there isn't much information that can be gathered from the backtrace 

Take note of 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 explains how to install what you need on Ubuntu
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_(Ubuntu,_Kubuntu,_KDE_Neon,_Linux_Mint)

Please reach out to the Ubuntu forums / support if you need help installing debug packages.
Comment 4 Bug Janitor Service 2025-12-03 03:46:12 UTC 
🐛🧹 ⚠️ 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!
Comment 5 Dhirendra Pal Singh 2025-12-03 08:23:48 UTC 
For Sure, I have an eye for this bug assigned, though I think, the upgrade process might be overwriting the symbols..... maybe.... nonetheless will try again. No worries at all.
Comment 6 Bug Janitor Service 2025-12-18 03:46:13 UTC 
🐛🧹 ⚠️ 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!