Hello all, last week I noticed and reported a bug I noticed with Fedora 34 KDE and fcitx. Basically having fcitx loaded causes LibreOffice Impress to segfault. I've seen this on two different machines now run the FL34 KDE Plasma betas, both were upgrades from FL33 where this setup worked fine.
I've also noticed that fcitx will no longer load on login even with fcitx.desktop placed in .config/autostart
Has anyone else noticed issues with fcitx on I'm thinking about switching over to ibus-mozc for Kana Kanji input needs and see if that fixes it.
Bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=1950838
Thanks!
Leander
在 2021-04-23星期五的 23:50 -0400，Leander Hutton via test写道：
Hello all, last week I noticed and reported a bug I noticed with Fedora 34 KDE and fcitx. Basically having fcitx loaded causes LibreOffice Impress to segfault. I've seen this on two different machines now run the FL34 KDE Plasma betas, both were upgrades from FL33 where this setup worked fine.
I've also noticed that fcitx will no longer load on login even with fcitx.desktop placed in .config/autostart
Has anyone else noticed issues with fcitx on I'm thinking about switching over to ibus-mozc for Kana Kanji input needs and see if that fixes it.
Bug report here:
Upstream should have fixed this in a release just now, https://github.com/fcitx/fcitx-qt5/releases/tag/1.2.6 I will update fcitx-qt5 and see if it fixes this problem.
Thanks!
Leander
--
Leander Hutton leander@one-button.org www.one-button.org _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en- US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject. org Do not reply to spam on the list, report it: https://pagure.io/fedora- infrastructure
On 4/24/21 12:06 AM, Qiyu Yan wrote:
Upstream should have fixed this in a release just now, https://github.com/fcitx/fcitx-qt5/releases/tag/1.2.6 I will update fcitx-qt5 and see if it fixes this problem.
Thank you, yes the new package fixed the issue. So far no segfaults out of LibreOffice Impress. Sorry for the delay in replying.
Leander
在 2021-04-23星期五的 23:50 -0400，Leander Hutton via test写道：
I've also noticed that fcitx will no longer load on login even with fcitx.desktop placed in .config/autostart
That is unexpected, to troubleshoot this, could you try copying /usr/share/applications/fcitx.desktop to .config/autostart to replace the current one, and see if problem is still present.
If still present, could you please post the output of: journalctl -b 0 --user | grep fcitx -i to see if fcitx is invoked or not.
On 4/24/21 1:55 AM, Qiyu Yan wrote:
在 2021-04-23星期五的 23:50 -0400，Leander Hutton via test写道：
I've also noticed that fcitx will no longer load on login even with fcitx.desktop placed in .config/autostart
That is unexpected, to troubleshoot this, could you try copying /usr/share/applications/fcitx.desktop to .config/autostart to replace the current one, and see if problem is still present.
If still present, could you please post the output of: journalctl -b 0 --user | grep fcitx -i to see if fcitx is invoked or not.
Yes, replacing the file in .config/autostart generated by KDE Plasma the one from /usr/share/applications was one of the first things I tried when I noticed this. Unfortunately that did not fix the issue. I also have fcitx added to the input modifiers via /etc/profile.d/fcitx.sh:
export XMODIFIERS="@im-fcitx" export QT_IM_MODULE=fcitx export GTK_IM_MODULE=fcitx
That has been in place for several version of Fedora Linux now.
Here is the output from journalctl, it seems it is getting activated but then gets signal 15 (SIGTERM) from somewhere else? If I manually start fcitx in KDE Plasma it will happily stay running until logout.
Thanks.
systemd[3937]: Starting Fcitx... fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-xim.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-keyboard.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-ipcportal.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-xkb.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-freedesktop-notify.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-fullwidth-char.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-chttrans.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-xkbdbus.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-lua.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-unicode.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-quickphrase.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-kkc.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-vk.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-notificationitem.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-ipc.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-kimpanel-ui.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-punc.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-imselector.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-classic-ui.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-dbus.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-spell.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-remote-module.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-clipboard.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-x11.conf fcitx[4427]: (INFO-4427 addon.c:151) Load Addon Config File:fcitx-autoeng.conf fcitx[4427]: ========================= fcitx[4427]: FCITX 4.2.9.7 -- Get Signal No.: 15 fcitx[4427]: Date: try "date -d @1619321222" if you are using GNU date *** fcitx[4427]: ProcessID: 4427 fcitx[4427]: /usr/bin/fcitx(+0x19ef)[0x55eab73789ef] fcitx[4427]: /lib64/libc.so.6(+0x3d310)[0x7f680e308310] fcitx[4427]: /lib64/libc.so.6(__read+0x10)[0x7f680e3bc700] fcitx[4427]: /lib64/libc.so.6(_IO_file_underflow+0x194)[0x7f680e34dc14] fcitx[4427]: /lib64/libc.so.6(_IO_default_xsgetn+0x35)[0x7f680e34f045] fcitx[4427]: /lib64/libc.so.6(fread+0x83)[0x7f680e3414e3] fcitx[4427]: /usr/lib64/fcitx/fcitx-dbus.so(+0x324a)[0x7f680e50324a] fcitx[4427]: /lib64/libfcitx-core.so.0(FcitxModuleLoad+0x1bd)[0x7f680e4e078d] fcitx[4427]: /lib64/libfcitx-core.so.0(+0x155e9)[0x7f680e4de5e9] fcitx[4427]: /lib64/libfcitx-core.so.0(FcitxInstanceRun+0x57)[0x7f680e4df347] fcitx[4427]: /usr/bin/fcitx(+0x14ae)[0x55eab73784ae] fcitx[4427]: /lib64/libc.so.6(__libc_start_main+0xd5)[0x7f680e2f2b75] fcitx[4427]: /usr/bin/fcitx(+0x158e)[0x55eab737858e] systemd[3937]: app-fcitx@autostart.service: Deactivated successfully. systemd[3937]: Started Fcitx.
在 2021-04-24星期六的 23:48 -0400，Leander Hutton via test写道：
export XMODIFIERS="@im-fcitx" export QT_IM_MODULE=fcitx export GTK_IM_MODULE=fcitx
Those are just fine.
Here is the output from journalctl, it seems it is getting activated but then gets signal 15 (SIGTERM) from somewhere else? If I manually start fcitx in KDE Plasma it will happily stay running until logout.
TBH, I have no idea where the SIGTERM is from, either. May be from kde itself? I will look into this later.
在 2021-04-24星期六的 23:48 -0400，Leander Hutton via test写道：
Here is the output from journalctl, it seems it is getting activated but then gets signal 15 (SIGTERM) from somewhere else? If I manually start fcitx in KDE Plasma it will happily stay running until logout.
Try this workaround: edit /etc/xdg/startkderc, comment out systemdBoot=true (or set to false)
On 4/28/21 12:26 PM, Qiyu Yan wrote: a it will happily stay running until logout.
Try this workaround: edit /etc/xdg/startkderc, comment out systemdBoot=true (or set to false)
Setting this to false allows fcitx to load on start up, thanks! I guess this setting changed between FL33 and FL34?
Thanks!
Leander
在 2021-04-29星期四的 11:48 -0400，Leander Hutton via test写道：
On 4/28/21 12:26 PM, Qiyu Yan wrote: a it will happily stay running until logout.
Try this workaround: edit /etc/xdg/startkderc, comment out systemdBoot=true (or set to false)
Setting this to false allows fcitx to load on start up, thanks! I guess this setting changed between FL33 and FL34?
Yes, for KDE&Wayland session (F34's KDE switched to Wayland for default), the autostart desktop files will be started by systemd-xdg- autostart-generator. As fcitx tries to daemonize it self, systemd treats fcitx as exited after exiting of main-process and killes everything in the cgroup, I guess.
That is just a workaround(and to determine the problem), I will try to change the Desktop file to avoid daemonizing. (Or avoid killing by systemd)
Thanks!
Leander
--
Leander Hutton leander@one-button.org www.one-button.org _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en- US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraprojec t.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Fri, Apr 23, 2021 at 11:50:38PM -0400, For testers of Fedora Core development releases wrote:
Hello all, last week I noticed and reported a bug I noticed with Fedora 34 KDE and fcitx. Basically having fcitx loaded causes LibreOffice Impress to segfault. I've seen this on two different machines now run the FL34 KDE Plasma betas, both were upgrades from FL33 where this setup worked fine.
I've also noticed that fcitx will no longer load on login even with fcitx.desktop placed in .config/autostart
Has anyone else noticed issues with fcitx on I'm thinking about switching over to ibus-mozc for Kana Kanji input needs and see if that fixes it.
I've not had this problem with Gnome or openbox. I haven't tried with KDE, though.
(The openbox install was done by choosing minimal at install, then adding on. Gnome was done by a standard live workstation install).
Not sure if this information is any help to you, though.
On 4/24/21 6:18 AM, Scott Robbins wrote:
I've not had this problem with Gnome or openbox. I haven't tried with KDE, though.
(The openbox install was done by choosing minimal at install, then adding on. Gnome was done by a standard live workstation install).
Not sure if this information is any help to you, though.
Thanks, yes I have the same experience in GNOME. It seems it was a specific Plasma or QT5 and fcitx bug.
Thanks!
Leander
-
Leander Hutton -
Qiyu Yan -
Scott Robbins