https://bugs.kde.org/show_bug.cgi?id=458452
--- Comment #5 from Steven <stvnw...@yahoo.com> --- (In reply to Nate Graham from comment #4) > I'm afraid that's not a backtrace. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. Ah my fault! Sorry still new to this, I read over carefully and I believe I have it here: (gdb) backtrace #0 0x00007fffa47d1b67 in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #1 0x00007fffa47db7dc in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #2 0x00007ffff6223e86 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #3 0x00007ffff72701a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #4 0x00007ffff620017a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #5 0x00007ffff6200c79 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #6 0x00007ffff6247558 in () at /usr/lib/libQt5Core.so.5 #7 0x00007ffff4a9cf13 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #8 0x00007ffff4af30d9 in () at /usr/lib/libglib-2.0.so.0 #9 0x00007ffff4a9a485 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #10 0x00007ffff624b45a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #11 0x00007ffff61f845b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #12 0x00007ffff6203ba7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #13 0x0000555555568950 in () #14 0x00007ffff5bb7b25 in __libc_start_main () at /usr/lib/libc.so.6 #15 0x000055555556931e in () (gdb) Quit -- You are receiving this mail because: You are watching all bug changes.
