Description of problem:
Tried to switch input methods. No response, pressed the keys again, still no response.
Shortly afterward, I noticed the key sequence was passing through to the application instead, suggesting that something had died.
Shortly after that, a notification popped up on my desktop telling me there was a "problem", and now I'm reporting it :o)
Version-Release number of selected component:
runlevel: N 5
Potential duplicate: bug 1660521
Created attachment 1534474 [details]
Created attachment 1534475 [details]
Created attachment 1534476 [details]
Created attachment 1534477 [details]
Created attachment 1534478 [details]
Created attachment 1534479 [details]
Created attachment 1534480 [details]
Created attachment 1534481 [details]
Created attachment 1534482 [details]
Created attachment 1534483 [details]
Created attachment 1534484 [details]
I need to check why the IMS switcher popup is not launched in your box.
Are you still able to reproduce the backtrace?
(In reply to Bill Crawford from comment #1)
> Created attachment 1534474 [details]
> File: backtrace
I switched to fcitx because I didn't trust ibus after that :o)
If there are specific things I can do to test for you, I am willing to switch back for a while.
I could not understand the backtrace (there seemed to be multiple stack frames for the same function in the main thread).
Right. The same backtrace means the same order of the functions.
If you still reproduce the same backtrace, please comment here.