https://bugs.kde.org/show_bug.cgi?id=509266
Bug ID: 509266
Summary: Spectacle Crash sometimes....
Classification: Applications
Product: Spectacle
Version First 23.08.5
Reported In:
Platform: Ubuntu
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Application: spectacle (23.08.5)
Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.14.0-29-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04.3 LTS
DrKonqi: 5.27.11 [KCrashBackend]
-- Information about the crash:
Hello there,
I am trying to be polite in this information about the crash. I was very much
presented by KDE Crash Handler if I could go through the, previously similar
bug list, and at least try to reduce the ambiguousness for this crash.
Henceforth I have attached the image of the bug list, further below.
I will try to collate again by give the flollowing information:
A) I don't get the error every time I use "Spectacle", that said I would agree
in advance if this is a "race condition" that was removed previously by a patch
and has somehow not made to my computer/machine for some configuration,
required for upgrade, but not "put in place" by me.
B) I don't I have NVidia graphics on my machine as it shows in lspci AMD/ATI
alone, and I like working alone as well.
C) The kernel version that I have running is "6.14.0-29-generic".
The bug list image by sharing screenshot image using photos.google.com is as
follows:
https://photos.app.goo.gl/oadV77ScYfVmdbcP6
Hope I am a good bug report and assist A.I. to properly resolve this bug. (I
don't have the bug number as the filing process is not yet done.)
Thanks as well as Regards
[Dhirendra P. Singh]
The crash can be reproduced sometimes.
-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault
[KCrash Handler]
#4 0x00007732d0004e00 in ??? ()
#5 0x000060bf3b003950 in ??? ()
#6 0x000060bf3b00546e in ??? ()
#7 0x000060bf3afee7d9 in ??? ()
#8 0x00007732ebf12e16 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x000060bf3b01f381 in ??? ()
#10 0x00007732ebf171aa in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007732ebf0624b in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007732ed76bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007732ebed8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007732ebf345ab in QTimerInfoList::activateTimers() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007732ebf34ed9 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007732e86485c5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007732e86a7737 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007732e8647a63 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007732ebf35279 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007732ebed6a7b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007732ebedf3e8 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x000060bf3afcf8d3 in ??? ()
#23 0x00007732eb42a1ca in __libc_start_call_main
(main=main@entry=0x60bf3afceea0, argc=argc@entry=1,
argv=argv@entry=0x7ffdd5524cc8) at ../sysdeps/nptl/libc_start_call_main.h:58
#24 0x00007732eb42a28b in __libc_start_main_impl (main=0x60bf3afceea0, argc=1,
argv=0x7ffdd5524cc8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffdd5524cb8) at ../csu/libc-start.c:360
#25 0x000060bf3afd0865 in ??? ()
[Inferior 1 (process 433529) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
