https://bugs.kde.org/show_bug.cgi?id=405899

            Bug ID: 405899
           Summary: spectacle crashes when taking a screenshot
           Product: Spectacle
           Version: unspecified
          Platform: Debian stable
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: General
          Assignee: m...@baloneygeek.com
          Reporter: oj002...@gmail.com
  Target Milestone: ---

Application: spectacle (18.04.0 - A Dearth of Dank Memes)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-4-amd64 x86_64
Distribution: Debian GNU/Linux buster/sid

-- Information about the crash:
- What I was doing when the application crashed:
I was taking a screenshot froma  amrked area
when the should be able to amrk the area nothing hppend, my screen frozze and
when I left clicked the message spectacle crahsed showed up

The crash can be reproduced every time.

-- Backtrace:
Application: Spectacle (spectacle), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6c4a0bb840 (LWP 29380))]

Thread 4 (Thread 0x7f6c39957700 (LWP 29383)):
#0  0x00007f6c4f093b69 in __GI___poll (fds=0x7f6c34004a00, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f6c4d217136 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6c4d21725c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6c4f5a587b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f6c4f55327b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f6c4f3a2ec6 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f6c501dbc65 in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007f6c4f3acaa7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f6c4dff6fa3 in start_thread (arg=<optimized out>) at
pthread_create.c:486
#9  0x00007f6c4f09e82f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f6c43fff700 (LWP 29382)):
#0  0x00007f6c4f093b69 in __GI___poll (fds=0x7f6c3c004db0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f6c4d217136 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6c4d21725c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6c4f5a587b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f6c4f55327b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f6c4f3a2ec6 in QThread::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f6c4fe8e545 in  () at /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f6c4f3acaa7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f6c4dff6fa3 in start_thread (arg=<optimized out>) at
pthread_create.c:486
#9  0x00007f6c4f09e82f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f6c49926700 (LWP 29381)):
#0  0x00007f6c4f093b69 in __GI___poll (fds=0x7f6c49925c78, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f6c50e60cf7 in  () at /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f6c50e6291a in xcb_wait_for_event () at
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f6c49c42d79 in  () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f6c4f3acaa7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f6c4dff6fa3 in start_thread (arg=<optimized out>) at
pthread_create.c:486
#6  0x00007f6c4f09e82f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f6c4a0bb840 (LWP 29380)):
[KCrash Handler]
#6  0x00007f6c4efdc8bb in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:50
#7  0x00007f6c4efc7535 in __GI_abort () at abort.c:79
#8  0x00007f6c4f36b9a7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f6c5131dc9d in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () at
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007f6c5131ed65 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007f6c5131f615 in  () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007f6c4f90e1d5 in QWindow::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007f6c513992db in QQuickWindow::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x00007f6c5048a4b1 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f6c50491950 in QApplication::notify(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f6c4f5545a9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f6c4f903203 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f6c4f903ead in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x00007f6c4f8de06b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x00007f6c49cd93eb in  () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007f6c4f55327b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f6c4f55b262 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x000056454147c2ea in  ()
#24 0x00007f6c4efc909b in __libc_start_main (main=0x56454147ac90, argc=2,
argv=0x7ffda0b725c8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffda0b725b8) at ../csu/libc-start.c:308
#25 0x000056454147c75a in _start ()
[Inferior 1 (process 29380) detached]

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to