https://bugs.kde.org/show_bug.cgi?id=498427
--- Comment #6 from Mark Elston <melston1...@gmail.com> --- The backtrace from `coredumpctl gdb` doesn't look too promising: (gdb) bt #0 0x0000715b136780df in g_log_structured_array () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x0000715b136783cc in g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x0000715b13678670 in g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x0000715b13678953 in g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x0000715b0fe81422 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x0000715b101d11fa in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x0000715b101d1b98 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x0000715b101d3bc3 in g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x0000715b101d3f4f in g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 -- You are receiving this mail because: You are the assignee for the bug.
