Bug 2076817

Summary: [abrt] ibus-anthy-python: __update_anthy_convert_chars(): engine.py:1278:__update_anthy_convert_chars:TypeError: can only concatenate str (not "NoneType") to str
Product: [Fedora] Fedora Reporter: ksuzumur
Component: ibus-anthyAssignee: fujiwara <tfujiwar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: i18n-bugs, red-hat-bugzilla-s0hdudiv, shawn.p.huang, tagoh, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3b1097c2fd780bf7e869a2d688cee7df2cbab8d0
Whiteboard: abrt_hash:adf1428823b5e645d6a3b67bae82a7aaac3b13c8;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 19:04:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 7 fujiwara 2022-04-20 01:51:52 UTC
I cannot reproduce your problem.
Which Hiragana string are you trying converting?

Are you also attach the log of `ibus read-config --engine-id=anthy` to this bug?

Comment 9 fujiwara 2022-04-20 04:35:31 UTC
I don't see any customized settings from your ibus.log.

Which Hiragana string are you trying converting when you get the abort?

Can you reproduce your problem when you move $HOME/.config/anthy to anywhere and restart ibus?

Comment 10 ksuzumur 2022-04-26 06:39:28 UTC
Hi, 

Thank you for your confirmation. Actually, I don't know what string I used. Currently, I don't face the same issue.
If I reproduce it, I will report again.

Comment 11 Kevin Weis 2022-06-22 19:29:12 UTC
For me the crash occured on keboard layout switch from en-us to japanese (anthy).

Comment 12 ksuzumur 2022-08-26 10:30:37 UTC
*** Bug 2121705 has been marked as a duplicate of this bug. ***

Comment 13 fujiwara 2022-08-26 10:37:20 UTC
(In reply to Kevin Weis from comment #11)
> For me the crash occured on keboard layout switch from en-us to japanese
> (anthy).

I cannot reproduce your problem with Super-space key.

Which desktop did you use, GNOME Wayland?

Comment 14 Kevin Weis 2022-09-01 20:13:45 UTC
Yes, GNOME Wayland. I can't either, it seems like a one-time-thing, for me at least.

Comment 15 Ben Cotton 2023-04-25 17:01:58 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 16 Ludek Smid 2023-05-25 19:04:23 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.