Application: ibus-ui-emojier-plasma (5.18.5) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-37-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: I've tried opening it through the "start" menu and using the keyboard shortcut (Super + .). Both instances cause the application to crash when trying to open it. - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: Emoji Picker (ibus-ui-emojier-plasma), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c1e7c7900 (LWP 334725))] Thread 4 (Thread 0x7f2c16dee700 (LWP 334732)): #0 0x00007f2c2219a96f in __GI___poll (fds=0x7f2c080025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f2c242061ae in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f2c242062e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f2c22736583 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f2c226dd4db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f2c22515785 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f2c23b271a9 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x00007f2c225169d2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f2c21e7c609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #9 0x00007f2c221a7103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2c17fff700 (LWP 334731)): #0 0x00007f2c2219a96f in __GI___poll (fds=0x7f2c100029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f2c242061ae in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f2c242062e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f2c22736583 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f2c226dd4db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f2c22515785 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f2c2186cefa in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007f2c225169d2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f2c21e7c609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #9 0x00007f2c221a7103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2c1d912700 (LWP 334730)): #0 0x00007f2c2219a96f in __GI___poll (fds=0x7f2c1d911ba8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f2c20e3bc1a in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007f2c20e3d90a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007f2c1e11d298 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007f2c225169d2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f2c21e7c609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007f2c221a7103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2c1e7c7900 (LWP 334725)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x00007f2c220aa859 in __GI_abort () at abort.c:79 #8 0x00007f2c224ddaad in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007f2c23e78065 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x00007f2c23e79157 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007f2c23e79a1d in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x00007f2c22ad29ad in QWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x00007f2c23efb159 in QQuickWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x00007f2c230f6a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x00007f2c231000f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x00007f2c226de93a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f2c22ac8de6 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x00007f2c22ac9014 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x00007f2c22aa335b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x00007f2c1e11e32e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x00007f2c24205fbd in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007f2c24206240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007f2c242062e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007f2c22736565 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007f2c226dd4db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007f2c226e5246 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x00005590739ddd6b in () #28 0x00007f2c220ac0b3 in __libc_start_main (main=0x5590739dd660, argc=1, argv=0x7ffc905acce8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc905accd8) at ../csu/libc-start.c:308 #29 0x00005590739dde3e in _start () [Inferior 1 (process 334725) detached] Possible duplicates by query: bug 423222, bug 422433, bug 421576, bug 420414, bug 419798. Report to https://bugs.kde.org/
>handleContextCreationFailure I bet your systemsettings also crashes along with discover and everything until you reboot and then everything works again?
Yeah you're right
See last comment in linked report. *** This bug has been marked as a duplicate of bug 423494 ***