Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mozc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
Title:
Japan
** Changed in: mozc (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
Title:
Japanese hiragana input fails after first keypress in anki
To manage notifica
** Also affects: mozc (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
Title
Thanks Gunnar,
I have filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228
** Bug watch added: Debian Bug tracker #991228
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991228
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Thanks for your report and your research!
However, the upstream commit which is said to fix it is huge, and does
not apply to the version of the source in Debian/Ubuntu.
mozc is packaged at Debian. It would be great if you could file a bug to
Debian too, so the maintainer can consider the best wa
** Package changed: anki (Ubuntu) => mozc (Ubuntu)
** Description changed:
This was working fine before I upgraded to 21.04. Since then I am seeing
what appears to be a bad interaction between the Japanese input method
and anki or anki's underlying widget set. Hiragana input works by typing
This issue has now been fixed in mozc under issue 510 above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
Title:
Japanese hiragana input fails after first keypress in anki
To manage notifi
c.f. https://github.com/google/mozc/issues/510
** Bug watch added: github.com/google/mozc/issues #510
https://github.com/google/mozc/issues/510
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931554
As far as I can tell line 207 above fails due to the text being the
empty string "", but the cursor_pos and anchor_pos are both 1, so line
207 is trying to assign the string from position 1 to position 0 within
the empty string. That makes some sense given how the input method
works. At the time of
mozc_engine.cc:207 appears to be source of an exception in a C++ string, so
surrounding_text.end - selection_end_it < 0...
(gdb) list
202 const size_t selection_length = abs(info->relative_selected_length);
203 const auto &selection_start_it = surrounding_text.begin() +
selection_star
I think I'm narrowing down on the source of the issue. I'm seeing crashes in
ibus-engine-mozc as part of package ibus-mozc
After building from source and installing debug symbols the key parts of the
stack trace appears to be as follows
#10 std::__cxx11::basic_string,
std::allocator >::assign<_
c.f. https://github.com/ankitects/anki/issues/1239
** Bug watch added: github.com/ankitects/anki/issues #1239
https://github.com/ankitects/anki/issues/1239
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
12 matches
Mail list logo