I noticed that work of Fcitx had a problem in antiX-15 recently.
(Fcitx is an input method of Japanese, Chinese and Korean)
The setting of the export is accomplished definitely.
but it is in a condition not to be able to use Fcitx in application.
but I cannot use Fcitx in much application.
As for the application using GTK, Fcitx is recognized by setting of the IM.
I can input only when I set this.
In addition, I was able to use it in this setting normally until several months ago.
Whether it can be thought by some this problem?
This may occur by the IM other than IBus. (uim and SCIM).
The outbreak of the problem is only antiX-15, and MX Linux does not occur.
(MX Linux (MX-15 and MX-14) sets this in im-config)
topic title: Work of input method (Fcitx) has a problem
-
Posts: 65
- Joined: 27 May 2014
-
Posts: 4,164
- Joined: 20 Feb 2009
#2
Since MX uses xfce and AntiX uses Windows managers.
Does this behavior occur across all window managers like JWM, Icewm, Fluxbox?
Also the icon desktop choices like JWM Rox, JWM Spacefm, Fluxbox Rox, Fluxbox Spacefm,
Icewm Rox, Icewm Spacefm?
Just asking to see if we can narrow down the broken behavior.
Does this behavior occur across all window managers like JWM, Icewm, Fluxbox?
Also the icon desktop choices like JWM Rox, JWM Spacefm, Fluxbox Rox, Fluxbox Spacefm,
Icewm Rox, Icewm Spacefm?
Just asking to see if we can narrow down the broken behavior.
-
Posts: 65
- Joined: 27 May 2014
#3
There is not this problem with the change by the difference of the window manager.
Any window manager occurs.
Any window manager occurs.
-
Posts: 65
- Joined: 27 May 2014
#4
I tried antiX-15.1 alpha1, but this problem continues.
-
Posts: 4,164
- Joined: 20 Feb 2009
#5
More of a bump than help on my end since I do not have a clue on Asian software setup. All I can suggest is run and post the output in this thread
so folks with a better handle on this stuff can look at what it says.
Code: Select all
fcitx-diagnose
-
Posts: 65
- Joined: 27 May 2014
#6
fcitx-diagnose and then outputs a fairly long results.
I will publish the output result here for the:
Incidentally, in the temporary impact of the"LANG=C",
Fcitx might be a place which is output problems.
I will publish the output result here for the:
Incidentally, in the temporary impact of the"LANG=C",
Fcitx might be a place which is output problems.
Last edited by balloon on 29 Nov 2015, 00:53, edited 1 time in total.
-
Posts: 65
- Joined: 27 May 2014
#7
I check the output result, I noticed this:
]I would further investigate this issue.
Code: Select all
3. Addon Libraries:
**Cannot find file `fcitx-xkbdbus.so` of addon `fcitx-xkbdbus`.**
**Cannot find file `fcitx-keyboard.so` of addon `fcitx-keyboard`.**
**Cannot find file `fcitx-mozc.so` of addon `fcitx-mozc`.**
**Cannot find file `fcitx-vk.so` of addon `fcitx-vk`.**
**Cannot find file `fcitx-autoeng.so` of addon `fcitx-autoeng`.**
**Cannot find file `fcitx-x11.so` of addon `fcitx-x11`.**
**Cannot find file `fcitx-classic-ui.so` of addon `fcitx-classic-ui`.**
**Cannot find file `fcitx-notificationitem.so` of addon `fcitx-notificationitem`.**
**Cannot find file `fcitx-quickphrase.so` of addon `fcitx-quickphrase`.**
**Cannot find file `fcitx-fullwidth-char.so` of addon `fcitx-fullwidth-char`.**
**Cannot find file `fcitx-unicode.so` of addon `fcitx-unicode`.**
**Cannot find file `fcitx-spell.so` of addon `fcitx-spell`.**
**Cannot find file `fcitx-xim.so` of addon `fcitx-xim`.**
**Cannot find file `fcitx-freedesktop-notify.so` of addon `fcitx-freedesktop-notify`.**
**Cannot find file `fcitx-clipboard.so` of addon `fcitx-clipboard`.**
**Cannot find file `fcitx-light-ui.so` of addon `fcitx-light-ui`.**
**Cannot find file `fcitx-dbus.so` of addon `fcitx-dbus`.**
**Cannot find file `fcitx-punc.so` of addon `fcitx-punc`.**
**Cannot find file `fcitx-xkb.so` of addon `fcitx-xkb`.**
**Cannot find file `fcitx-imselector.so` of addon `fcitx-imselector`.**
**Cannot find file `fcitx-ipc.so` of addon `fcitx-ipc`.**
**Cannot find file `fcitx-chttrans.so` of addon `fcitx-chttrans`.**
**Cannot find file `fcitx-remote-module.so` of addon `fcitx-remote`.**
**Cannot find file `fcitx-anthy.so` of addon `fcitx-anthy`.**
-
Posts: 65
- Joined: 27 May 2014
#9
I found a bug report of Fcitx that has led to the same state:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/fcitx/fcitx/issues/234"
linktext was:"https://github.com/fcitx/fcitx/issues/234"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/fcitx/fcitx/issues/207"
linktext was:"https://github.com/fcitx/fcitx/issues/207"
====================================
I want to watch the progress.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/fcitx/fcitx/issues/234"
linktext was:"https://github.com/fcitx/fcitx/issues/234"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/fcitx/fcitx/issues/207"
linktext was:"https://github.com/fcitx/fcitx/issues/207"
====================================
I want to watch the progress.
-
Posts: 65
- Joined: 27 May 2014
#10
I changed it to IBus and uim in substitution for Fcitx.
However, the same problem occurred in IBus and uim.
It is in this way clear not to be a problem peculiar to Fcitx.
However, the same problem occurred in IBus and uim.
It is in this way clear not to be a problem peculiar to Fcitx.
-
Posts: 1,445
- Joined: 09 Feb 2012
#12
lightdm depends on libpam-systemd
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/lightdm"
linktext was:"https://packages.debian.org/jessie/lightdm"
====================================
and has a poor track record of vulnerabilities
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2013-4331/"
linktext was:"http://www.cvedetails.com/cve/CVE-2013-4331/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2012-1111/"
linktext was:"http://www.cvedetails.com/cve/CVE-2012-1111/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2012-0943/"
linktext was:"http://www.cvedetails.com/cve/CVE-2012-0943/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2011-3153/"
linktext was:"http://www.cvedetails.com/cve/CVE-2011-3153/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2013-4459/"
linktext was:"http://www.cvedetails.com/cve/CVE-2013-4459/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2011-4105/"
linktext was:"http://www.cvedetails.com/cve/CVE-2011-4105/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ubuntu.com/usn/usn-1950-1/"
linktext was:"http://www.ubuntu.com/usn/usn-1950-1/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ubuntu.com/usn/USN-2012-1/"
linktext was:"http://www.ubuntu.com/usn/USN-2012-1/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bugzilla.redhat.com/show_bug.cgi?id=1049420"
linktext was:"https://bugzilla.redhat.com/show_bug.cgi?id=1049420"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://seclists.org/oss-sec/2015/q4/352"
linktext was:"http://seclists.org/oss-sec/2015/q4/352"
====================================
edit:
sorry ~~ what I posted above is incorrect.
I tested. NO, installing lightdm v1.10.3-3 from debian jessie repository did NOT bring systemd into antix15.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/lightdm"
linktext was:"https://packages.debian.org/jessie/lightdm"
====================================
and has a poor track record of vulnerabilities
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2013-4331/"
linktext was:"http://www.cvedetails.com/cve/CVE-2013-4331/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2012-1111/"
linktext was:"http://www.cvedetails.com/cve/CVE-2012-1111/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2012-0943/"
linktext was:"http://www.cvedetails.com/cve/CVE-2012-0943/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2011-3153/"
linktext was:"http://www.cvedetails.com/cve/CVE-2011-3153/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2013-4459/"
linktext was:"http://www.cvedetails.com/cve/CVE-2013-4459/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.cvedetails.com/cve/CVE-2011-4105/"
linktext was:"http://www.cvedetails.com/cve/CVE-2011-4105/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ubuntu.com/usn/usn-1950-1/"
linktext was:"http://www.ubuntu.com/usn/usn-1950-1/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ubuntu.com/usn/USN-2012-1/"
linktext was:"http://www.ubuntu.com/usn/USN-2012-1/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://bugzilla.redhat.com/show_bug.cgi?id=1049420"
linktext was:"https://bugzilla.redhat.com/show_bug.cgi?id=1049420"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://seclists.org/oss-sec/2015/q4/352"
linktext was:"http://seclists.org/oss-sec/2015/q4/352"
====================================
edit:
sorry ~~ what I posted above is incorrect.
I tested. NO, installing lightdm v1.10.3-3 from debian jessie repository did NOT bring systemd into antix15.
Last edited by skidoo on 02 Dec 2015, 21:41, edited 1 time in total.
-
Posts: 65
- Joined: 27 May 2014
#13
I do not need the unnecessary report. I do not need to be lightdm.
It is good in gdm, kdm, sddm and lxdm...
It is that input method works normally to demand most.
The Asian user comes to be used for im-config commonly now.
The present conditions of antiX become the big factor to avoid use.
distribution which a native language cannot input will not be used.
It is good in gdm, kdm, sddm and lxdm...
It is that input method works normally to demand most.
The Asian user comes to be used for im-config commonly now.
The present conditions of antiX become the big factor to avoid use.
distribution which a native language cannot input will not be used.
-
Posts: 1,445
- Joined: 09 Feb 2012
#14
I do not need the unnecessary vulnerability exposure. Fulfilling your"demand" would affect all users, so my report is"necessary".
-
Posts: 65
- Joined: 27 May 2014
#15
Let's go back up in an original topic:
When we do not solve this problem, the use of Fcitx in antiX-15 may not progress.
This report included progress and confirmed that there was a bug when other users used Fcitx in Debian.balloon wrote:I found a bug report of Fcitx that has led to the same state:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/fcitx/fcitx/issues/234"
linktext was:"https://github.com/fcitx/fcitx/issues/234"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/fcitx/fcitx/issues/207"
linktext was:"https://github.com/fcitx/fcitx/issues/207"
====================================
I want to watch the progress.
When we do not solve this problem, the use of Fcitx in antiX-15 may not progress.