Created attachment 1515354 [details]
File: backtrace

Created attachment 1515355 [details]
File: cgroup

Created attachment 1515356 [details]
File: core_backtrace

Created attachment 1515357 [details]
File: cpuinfo

Created attachment 1515358 [details]
File: dso_list

Created attachment 1515359 [details]
File: environ

Created attachment 1515360 [details]
File: limits

Created attachment 1515361 [details]
File: maps

Created attachment 1515362 [details]
File: mountinfo

Created attachment 1515363 [details]
File: open_fds

Created attachment 1515364 [details]
File: proc_pid_status

(In reply to Mike FABIAN from comment #1)
> Created attachment 1515354 [details]
> File: backtrace

I cannot reproduce the backtrace. Are you still able to reproduce the backtrace?
Seems the previous engine switcher popup was closed unexpectedly and you launched the engine switcher popup again and caused the SEGV because m_loop is NULL.
So it would important how you terminated the previous engine switcher.

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f19d6cb2895 in __GI_abort () at abort.c:79
#2  0x00007f19d6e93de3 in g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x5605383edce8 <__func__.64224> "switcher_run", message=<optimized out>) at gtestutils.c:2596
#3  0x00007f19d6eee6be in g_assertion_message_expr (domain=domain@entry=0x5605383e7011 "IBUS", file=file@entry=0x5605383ed8df "switcher.c", line=line@entry=418, func=func@entry=0x5605383edce8 <__func__.64224> "switcher_run", expr=expr@entry=0x5605383ed945 "m_loop == null") at gtestutils.c:2619
#4  0x00005605383e3c76 in switcher_run (self=0x560539842340, keyval=keyval@entry=32, state=<optimized out>, event=event@entry=0x7f19b4007710, engines=<optimized out>, engines_length1=<optimized out>, index=1, input_context_path=0x5605395b80a0 "") at switcher.c:418
#5  0x00005605383daf17 in panel_handle_engine_switch (reverse=0, event=0x7f19b4007710, self=0x5605395b71b0) at panel.c:3572

Clearing the needinfo for now

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.