Your message dated Mon, 11 May 2015 22:34:47 +0000
with message-id <e1yrwhf-0004n4...@franck.debian.org>
and subject line Bug#784199: fixed in librime 1.2+dfsg-2
has caused the Debian Bug report #784199,
regarding librime: need to rebuild against new libyaml-cpp
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 ow...@bugs.debian.org
immediately.)


-- 
784199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


*** reportbug-fcitx-rime-20150503-14715-_FLLAp
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hong Xu <h...@topbug.net>
Cc: h...@topbug.net
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: fcitx-rime: Cannot enable rime in fcitx after a recent update
Message-ID: <20150503230321.14715.1196.reportbug@hong-macbook>
X-Mailer: reportbug 6.6.3
Date: Sun, 03 May 2015 16:03:21 -0700

Package: fcitx-rime
Version: 0.3.1-1
Severity: grave
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

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fcitx-rime depends on:
ii  fcitx-bin      1:4.2.8.5-2
ii  fcitx-data     1:4.2.8.5-2
ii  fcitx-modules  1:4.2.8.5-2
ii  libc6          2.19-18
ii  librime-data   0.35-1
ii  librime1       1.2+dfsg-1

Versions of packages fcitx-rime recommends:
ii  fcitx  1:4.2.8.5-2

fcitx-rime suggests no packages.

-- no debconf information



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fcitx-rime depends on:
ii  fcitx-bin      1:4.2.8.5-2
ii  fcitx-data     1:4.2.8.5-2
ii  fcitx-modules  1:4.2.8.5-2
ii  libc6          2.19-18
ii  librime-data   0.35-1
ii  librime1       1.2+dfsg-1

Versions of packages fcitx-rime recommends:
ii  fcitx  1:4.2.8.5-2

fcitx-rime suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: librime
Source-Version: 1.2+dfsg-2

We believe that the bug you reported is fixed in the latest version of
librime, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guo Yixuan (郭溢譞) <culu....@gmail.com> (supplier of updated librime package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2015 01:14:42 -0400
Source: librime
Binary: librime1 librime-bin librime-dev librime1-dbg
Architecture: source amd64 all
Version: 1.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team <pkg-ime-de...@lists.alioth.debian.org>
Changed-By: Guo Yixuan (郭溢譞) <culu....@gmail.com>
Description:
 librime-bin - Rime Input Method Engine - utilities
 librime-dev - Rime Input Method Engine, the core library - development files
 librime1   - Rime Input Method Engine - core library
 librime1-dbg - Rime Input Method Engine, the core library - debugging symbols
Closes: 784199
Changes:
 librime (1.2+dfsg-2) unstable; urgency=medium
 .
   * Rebuild with libyaml-cpp0.5, 0.5.2. (Closes: #784199)
   * Updated copyright.
   * Bumped standard version to 3.9.6, no changes needed.
Checksums-Sha1:
 5dafb03d49e88130937877aa98b0244ec8c3aba6 2118 librime_1.2+dfsg-2.dsc
 a3ad25588f4c7608072bb527f5dcc9e8edd81e3c 87568 librime_1.2+dfsg-2.debian.tar.xz
 f25d0ec17bdee7e112b4ee8017d3097d833c1389 731386 librime1_1.2+dfsg-2_amd64.deb
 a447d5cb1a0bba52f1d1fb976c7138d51118df4c 31742 librime-bin_1.2+dfsg-2_amd64.deb
 2b0e9757888c930f182fa87461026431dcaca8ca 14154 librime-dev_1.2+dfsg-2_all.deb
 127bcf386702d37b4682d9a37a7a19249804e9cb 12808628 
librime1-dbg_1.2+dfsg-2_amd64.deb
Checksums-Sha256:
 f398d73c965bea51bfd573fd6249dce061ecf7e628c4265f1b65f146fbc66ba6 2118 
librime_1.2+dfsg-2.dsc
 b5164062ea29b689a5fc08550e2bae894449a879d2dfb00da7a51de20cb1f962 87568 
librime_1.2+dfsg-2.debian.tar.xz
 d8d5857798eecc6bd67bae4d5417007d70e561110de5d1e794399bc406793cea 731386 
librime1_1.2+dfsg-2_amd64.deb
 c144dbbeb4fcd4afb33b81e42406f319f833ef48be2bb2dacff86d4c98905ce4 31742 
librime-bin_1.2+dfsg-2_amd64.deb
 9366c28c03c9e938595f674f9cd26b320c83e86ad72ca452db6bd1c9bb43368f 14154 
librime-dev_1.2+dfsg-2_all.deb
 3c7072c462c9fed43663bb81de8a8c0956e0977782368bd9b95f1a32ec14a570 12808628 
librime1-dbg_1.2+dfsg-2_amd64.deb
Files:
 3aa2d0a13ead34fa31758f2d2113677e 2118 libs optional librime_1.2+dfsg-2.dsc
 aa28831af0c6003566b410bfd62af8fc 87568 libs optional 
librime_1.2+dfsg-2.debian.tar.xz
 332911a7f4ea4587d2dd642344488ccd 731386 libs optional 
librime1_1.2+dfsg-2_amd64.deb
 15c4a37ad63319b1c3d68cb0070777f7 31742 utils optional 
librime-bin_1.2+dfsg-2_amd64.deb
 1230d49a5c0b327f68726614f11998a8 14154 libdevel optional 
librime-dev_1.2+dfsg-2_all.deb
 57f2a5d073cdf68f9a28ddc89e8136a1 12808628 debug extra 
librime1-dbg_1.2+dfsg-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJVUS0gAAoJEPbsVcVkKA0e9SwH/iOpdoYKEPB9njFKB/BpbjW1
MjqfmtJuEuE4icJraChJZunKa5RecSQr0DJqCb1drKIANozwuh94o1AnH6DJxe6j
ajg9u71W5zCAsOhFjbYHXSfsDIJBDAHHCmkb8dAIlRoN0qQJGEx3u9eCC3psenVt
4p4xIS6qC/cjobd5VH7847jwvUXqbrFuh0zZychl01eX3Anobtq43In1qCPXhiGk
nIZoNZ+5IDDhVT5qFhigWNrG5bHG5ugjW298ouQoDhSwLYBomUFfUYMis0bo0UG9
VbVyS1h0zG/rdrhP1yCWEULnjUPPnN2gJXTV9cnzRCP853KT/0QRAupSevCgwpk=
=KhpB
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to