Bug ID 1202057
Summary fcitx stopped running (and being started at startup) for no reason
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Tumbleweed
Status NEW
Severity Major
Priority P5 - None
Component Other
Assignee screening-team-bugs@suse.de
Reporter php4fan@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Ages ago I had troubles with a particular application (PhpStorm) not being able
to type dead keys (^, `, ���, ���, etc.) nor the unicode composite characters that
start with them such as ���, ���, etc. because PhpStorm has some known issue with
dBus that they haven't been able to figure out in 12 years.

So I uninstalled iBus and installed Fcitx, which had been known to work for
some users, and it actually worked for me. From that point, I was able to use
dead keys in PhpStorm (and every other application, but those worked with iBus
too).

Recently dead keys stopped working again in PhpStorm and at first I thought it
was an update of theirs, but it wasn't.

Then I noticed that when I go to KDE's "System Settings -> whatever -> Input
Method" it says "Cannot connect to Fcitx by DBus, is Fcitx running?" (btw I
just had to TYPE this ****ing error message by hand. Please make every ****ing
thing that is ever displayed on screen copy-pastable).

So finally I ran fcitx-diagnose and it says:

``````
3.  process:

    **Fcitx is not running.**
    **Please check the Configure link of your distribution in [Beginner's
Guide](http://fcitx-im.org/wiki/Beginner%27s_Guide) for how to setup fcitx
autostart.**
``````

I never touched any of that, so there's no valid reason for fcitx to have
stopped running.

Something that I don't understand is that, despite that, in ALL applications
except for PhpStorm, dead keys still work regardless.

Also I had never tried fcitx-diagnose before so I cannot tell for sure that the
process had EVER been running. But what I can tell is that PhpStorm used to
work and one of the things that PhpStorm's staff asked me to check is that the
process is running.


When I first uninstalled iBus and before I installed Fcitx, I remember that
dead keys did stop working in ALL applications, and they only started working
again once I installed fcitx.


So, my guess at this point is (but I'm totally guessing):
- Fcitx is more than just a daemon process. It installs stuff _and_ a daemon. 
- Some applications (e.g. PhpStorm) need the daemon, some others (e.g.
everything else I ever use) don't, though they do need the other stuff that
fcitx is made of
- the daemon process used to be running and isn't anymore. And that would be
the bug.

That's the only explanation I can come up with, that doesn't lead to a bunch of
other contradictions and unanswered questions.


You are receiving this mail because: