[Pkg-ime-devel] Bug#784199: Bug#784199: fcitx-rime: Cannot enable rime in fcitx

[GUO Yixuan]

Control: merge -1 784200
Control: reassign -1 src:librime
Control: tag -1 + pending
Control: clone -1 -2
Control: reassign -2 libyaml-cpp0.5
Control: retitle -2 dependency problem breaks librime
Control: severity -2 important

Hi,

On Sun, May 03, 2015 at 04:40:23PM -0700, Hong Xu wrote:
> Package: fcitx-rime
> Version: 0.3.1-1
> Severity: grave
> Tags: newcomer
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
> 
> Enable rime in fcitx.
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> Open fcitx dialog, add a new IM, and choose rime to add.
> 
>    * What was the outcome of this action?
> 
> Fcitx stopped working, the list of IM is made to be blank. The following
> message were printed:
> 
> (fcitx-config-gtk3:12415): GLib-GIO-CRITICAL **:
> g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)'
> failed
> =========================
> FCITX 4.2.8.5 -- Get Signal No.: 11
> Date: try "date -d @1430693030" if you are using GNU date ***
> ProcessID: 12355
> fcitx[0x4015fb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x35180)[0x7f01d1ae4180]
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZNSsC1ERKSs+0xb)[0x7f01ce99926b]
> /usr/lib/librime.so.1(_ZN4rime10ConfigData15ConvertFromYamlERKN4YAML4NodeE+0x4d2)[0x7f01c44c4eb2]
> /usr/lib/librime.so.1(_ZN4rime10ConfigData12LoadFromFileERKSs+0x16a)[0x7f01c44c56aa]
> /usr/lib/librime.so.1(_ZN4rime18InstallationUpdate3RunEPNS_8DeployerE+0x14b)[0x7f01c45da51b]
> /usr/lib/librime.so.1(_ZN4rime8Deployer7RunTaskERKSsN5boost3anyE+0x9e)[0x7f01c44b950e]
> /usr/lib/librime.so.1(RimeStartMaintenance+0xa1)[0x7f01c44aebf1]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-rime.so(+0x2157)[0x7f01c4866157]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-rime.so(+0x2666)[0x7f01c4866666]
> /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x115c7)[0x7f01d26b65c7]
> /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x14780)[0x7f01d26b9780]
> /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x1311c)[0x7f01d26b811c]
> /usr/lib/x86_64-linux-gnu/libfcitx-
> core.so.0(FcitxInstanceUpdateIMList+0x25d)[0x7f01d26b844d]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-ipc.so(+0x300d)[0x7f01c62cf00d]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-ipc.so(+0x5e4c)[0x7f01c62d1e4c]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-ipc.so(+0x35c2)[0x7f01c62cf5c2]
> /lib/x86_64-linux-gnu/libdbus-1.so.3(+0x1e5ff)[0x7f01d13535ff]
> /lib/x86_64-linux-
> gnu/libdbus-1.so.3(dbus_connection_dispatch+0x3b4)[0x7f01d1345194]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-dbus.so(+0x22d8)[0x7f01d157f2d8]
> /usr/lib/x86_64-linux-gnu/fcitx/fcitx-dbus.so(+0x23e9)[0x7f01d157f3e9]
> /usr/lib/x86_64-linux-gnu/libfcitx-core.so.0(+0x9fe6)[0x7f01d26aefe6]
> /usr/lib/x86_64-linux-gnu/libfcitx-
> core.so.0(FcitxInstanceRun+0x210)[0x7f01d26af710]
> fcitx[0x400fb6]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f01d1ad0b45]
> fcitx[0x401029]
> 
> ** (fcitx-config-gtk3:12415): WARNING **:
> GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
> (timeout by message bus)
> 
> (fcitx-config-gtk3:12415): GLib-CRITICAL **: g_variant_unref: assertion 'value
> != NULL' failed
> 
> ** (fcitx-config-gtk3:12415): WARNING **:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.fcitx.Fcitx-0 was not provided by any .service files
> 
> 
>    * What outcome did you expect instead?
> 
> Rime should be enabled and usable.
> 
> I suspect this is a recent break in librime after libyaml-cpp is upgraded to
> 0.5.2, as shown in an ArchLinux bug: https://bugs.archlinux.org/task/44428


Thanks for this report. A rebuild indeed fixes this bug, which
indicates some problem with libyaml-cpp's shlib, so I'm cloning this
bug for libyaml-cpp.

Regards,
Yixuan