[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#960516: marked as done (fcitx crashes when using fcitx-rime)

Your message dated Sun, 03 Oct 2021 11:32:28 -0400
with message-id <b2f92a6a0ff44faa0b50975379a2368bb25f7084.camel@debian.org>
and subject line Mark some binary incompat issues as done
has caused the Debian Bug report #960516,
regarding fcitx crashes when using fcitx-rime
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
960516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960516
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: fcitx-rime
Version: 0.3.2-7

Dear Maintainer,

Yesterday I upgraded my Debian testing system from testing package-sources, unfortunately I found that fcitx-rime had a bug which crashed fcitx today. If fcitx-rime is the default input scheme of fcitx, then fcitx can not launch(Ctrl + Space not work) no matter in Xorg or Wayland Gnome. If fcitx-rime is not the default input scheme, then fcitx will crash once switching to fcitx-rime. However, fcitx will work fine if I use other input scheme rather than fcitx-rime.

This is the error report(from running command `fcitx` then switch to fcitx-rime):

(ERROR-5872 ime.c:432) fcitx-keyboard-in-tel-kagapa already exists
(ERROR-5872 ime.c:432) fcitx-keyboard-cm-mmuock already exists
=========================
FCITX 4.2.9.7 -- Get Signal No.: 11
Date: try "date -d @1589372300" if you are using GNU date ***
ProcessID: 5872
fcitx(+0x1927)[0x55bfebc90927]
/lib/x86_64-linux-gnu/libc.so.6(+0x3b7e0)[0x7f40c13387e0]
/lib/x86_64-linux-gnu/librime.so.1(_ZN4YAML4NodeD1Ev+0x21)[0x7f40b776e121]
/lib/x86_64-linux-gnu/librime.so.1(_ZN4rime10ConfigData12LoadFromFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPNS_14ConfigCompilerE+0x1d7)[0x7f40b776b747]
/lib/x86_64-linux-gnu/librime.so.1(_ZN4rime18InstallationUpdate3RunEPNS_8DeployerE+0x3cd)[0x7f40b784f7dd]
/lib/x86_64-linux-gnu/librime.so.1(_ZN4rime8Deployer7RunTaskERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN5boost3anyE+0xb3)[0x7f40b7727c83]
/lib/x86_64-linux-gnu/librime.so.1(RimeStartMaintenance+0xb6)[0x7f40b7708286]
/usr/lib/x86_64-linux-gnu/fcitx/fcitx-rime.so(+0x2e16)[0x7f40b78ece16]
/usr/lib/x86_64-linux-gnu/fcitx/fcitx-rime.so(+0x34ac)[0x7f40b78ed4ac]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x111ea)[0x7f40c15221ea]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x14388)[0x7f40c1525388]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(FcitxInstanceSwitchIMByIndex+0x95)[0x7f40c1525fb5]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x15083)[0x7f40c1526083]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(FcitxInstanceProcessKey+0x956)[0x7f40c1526f36]
/usr/lib/x86_64-linux-gnu/fcitx/fcitx-ipc.so(+0x6a70)[0x7f40ba424a70]
/lib/x86_64-linux-gnu/libdbus-1.so.3(+0x26c8d)[0x7f40c0f74c8d]
/lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_connection_dispatch+0x334)[0x7f40c0f657e4]
/usr/lib/x86_64-linux-gnu/fcitx/fcitx-dbus.so(+0x28b8)[0x7f40c0fbb8b8]
/usr/lib/x86_64-linux-gnu/fcitx/fcitx-dbus.so(+0x29d1)[0x7f40c0fbb9d1]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0xa38a)[0x7f40c151b38a]
/lib/x86_64-linux-gnu/libfcitx-core.so.0(FcitxInstanceRun+0x57)[0x7f40c151bb27]
fcitx(+0x12bf)[0x55bfebc902bf]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f40c1323e0b]
fcitx(+0x133a)[0x55bfebc9033a]

Package info:

Package: fcitx-rime
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 403
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Architecture: amd64
Multi-Arch: same
Version: 0.3.2-7
Depends: fcitx-bin, fcitx-data (>= 1:4.2.8.1), fcitx-modules, librime-data, libc6 (>= 2.14), libfcitx-config4 (>= 4.2.7), libfcitx-qt5-1 (>= 1.0.0), libgcc-s1 (>= 3.0), libqt5core5a (>= 5.12.2), libqt5gui5 (>= 5.7.0) | libqt5gui5-gles (>= 5.7.0), libqt5widgets5 (>= 5.0.2), librime1 (>= 1.5.3+dfsg1-5~), libstdc++6 (>= 5.2)
Recommends: fcitx (>= 1:4.2.8.1)
Breaks: fcitx (<< 1:4.2.0)

Package: fcitx
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 50
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Architecture: all
Version: 1:4.2.9.7-3
Depends: fcitx-bin, fcitx-data, fcitx-modules
Recommends: fcitx-config-gtk | kde-config-fcitx, fcitx-frontend-all | fcitx-frontend-fbterm, fcitx-ui-classic | fcitx-ui-light, im-config (>= 0.5)
Suggests: fcitx-m17n, fcitx-tools
Conffiles:
 /etc/X11/xinit/xinput.d/fcitx 16f80add1cac78453353a128af575771

I am using Linux version 5.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-11)) #1 SMP Debian 5.6.7-1 (2020-04-29)

Distributor ID:    Debian
Description:    Debian GNU/Linux bullseye/sid
Release:    testing
Codename:    bullseye
APT prefers: testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)



--- End Message ---
--- Begin Message --- 
Version: 0.3.2-9

Closing since the issues are solved.

Thanks,
Boyuan Yang

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: