Created attachment 358445 [details] .imsettings.log Description of problem: With the latest ibus and imsettings in rawhide a bubble is appearing for me at startup that ibus startup failed because of spawning too many ibus processes. Version-Release number of selected component (if applicable): imsettings-0.107.1-2.fc12 ibus-1.2.0.20090812-1.fc12 How reproducible: every time Steps to Reproduce: 1. login to desktop Actual results: warning bubble appears Expected results: ibus to be running normally
Meant to add after (re)booting ibus works on first login and then stops on further desktop sessions. After I logout I see an "ibus-daemon --xim" process.
probably imsettings fault. Though the process of "ibus-daemon --xim" should has deps of X, I'm not sure why it still keeps running even after X is killed.
Confirmed. I can reproduce this issue and can see ibus-daemon running even after logging out the desktop.
Is process ibus-x11 alive after logout?
(In reply to comment #4) > Is process ibus-x11 alive after logout? Yes, and it just restarted because ibus process has been gone with the disconnect signal before imsettings is aware of it. FWIW I found the interesting log in .imsettings.log for the first session: IM-Settings-Daemon[2646]: WARNING **: Main Input Method process for IBus died with the signal 11, but unexpectedly. restarting... This means ibus-x11 process that still keeps running was surely brought up by imsettings again though, but it killed by SIGSEGV. there may be a bug in ibus on the handling of the disconnect signal or so. Anyway, I got a fix for this issue, testing now.
IBus has a problem during finalizing. It has been fixed in upstream. I will build new ibus version soon.
https://koji.fedoraproject.org/koji/taskinfo?taskID=1637248 A scratch build, please test it.
Looks good. no segfault with the disconnect signal anymore but just exit with the status 0 now. thanks! Anyway, the root cause of this issue should be fixed in imsettings-0.107.2-1.fc12.