SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone.
Last night, I upgraded slackware-current. But today, when I launch fcitx, it gives me the following message and now I can't use fcitx to type:
Have you tried to recompile fcitx? A fresh compiled fcitx is working fine here under slackware64-current.
Yes,I have recompiled fcitx from source, but in openbox, it still couldn't launch. But surprisingly, I can use the same fcitx in KDE or XFCE.
Does it have something to do with the desktop environment?
I think KDE and Xfce automatically launch a dbus session. In OpenBox, as far as I know, this isn't the case. Try launching fcitx with dbus-launch and see if it works:
to have an active consolekit session with dbus in -current with openbox, you have to modify slightly your ~/.xinitrc.
in the last lines of the file you have the session start in a line like this
to have an active consolekit session with dbus in -current with openbox, you have to modify slightly your ~/.xinitrc.
in the last lines of the file you have the session start in a line like this
I think KDE and Xfce automatically launch a dbus session. In OpenBox, as far as I know, this isn't the case. Try launching fcitx with dbus-launch and see if it works:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.