I don't know how to consistently reproduce the problem, but it is happening too often. I cannot input anything with a Chinese IME (the default Chinese Pinyin IME on Windows 10) after using the software for a while. Restarting the GnuCash can resolve this, but after inputting one or two transactions, it stops working again. This only happens when I am editing the transactions. If I try to edit account, then the IME works OK. When the problem appears, I can use nothing appears in the texts box after I confirm the IME's candidate. I cannot input anything in Chinese. I changed my locale to en_US as soon as I installed GnuCash. Never tried if this also happens in the zh_CN locale.
With which https://wiki.gnucash.org/wiki/Locale_Settings are you running a) your system b) GnuCash? You might find a hint in your https://wiki.gnucash.org/wiki/Tracefile I suspect it might be related to a wrong code page.
Created attachment 371195 [details] trace files
Created attachment 371196 [details] trace file
Created attachment 371197 [details] trace file
Created attachment 371198 [details] trace file
I found several trace file on that day, as I have closed and opened the program for several times.
OK, there are CJK letters in the path of the data file: * WARN <gnc.gui> Unable to read mtime for file D:\Trans\D_Drive\Documents\百度云同步盘\Sync\misc\finance\pxml.gnucash we have several occurences of * CRIT <GLib> g_variant_new_string: assertion 'g_utf8_validate (string, -1, NULL)' failed often followed by * CRIT <GLib> g_key_file_free: assertion 'key_file != NULL' failed or * WARN <Pango> Invalid UTF-8 string passed to pango_layout_set_text()
> OK, there are CJK letters in the path of the data file Ah, this might be connected to bug 795134.
I've just pushed a fix for bug 795134. Please try tommorrow's nightly build (if nothing goes wrong it should appear at https://code.gnucash.org/builds/win32/maint).
Created attachment 371272 [details] trace file I tried https://code.gnucash.org/builds/win32/maint/gnucash-3.0-2018-04-23-git-3.0-87-g14c30344c+.setup.exe . The problem remains. I'm uploading new trace file, but I am wondering whether the information in it is really related to this problem. (I've also met other problems, with there is at least there is a workaround for that.) Now I think I somehow found to pattern to how this problem appears: if I open a file and directly go to the textbox to edit the description, then the IME works. I can input Chinese Characters. But when I changed the date, or anything else, I cannot input anything into the description with IME anymore. The IME seems to be working normally, but the characters will not appear in the textbox. But I can still input without the IME, but without IME I can input only letter and numbers, not Chinese characters.
I ran into this problem too. My environment is: GnuCash 2.7.4 or GnuCash 3.0 Windows 10 1803
2.6.21 is working OK for me.
A similar input method problem has manifested on MacOS as well, see https://lists.gnucash.org/pipermail/gnucash-user/2018-May/077206.html and following. This is now covered in bug 796423.
3.0 can't use Chinese IME input as well
3.1 can't use Chinese IME input as well
(In reply to fefe.wyx from comment #10) > Now I think I somehow found to pattern to how this problem appears: if I > open a file and directly go to the textbox to edit the description, then the > IME works. I can input Chinese Characters. But when I changed the date, or > anything else, I cannot input anything into the description with IME > anymore. The IME seems to be working normally, but the characters will not > appear in the textbox. But I can still input without the IME, but without > IME I can input only letter and numbers, not Chinese characters. That did the trick, I was able to reproduce it that way. I think that this is fixed in maint. Please test with tomorrow's (i.e. 2018-06-05) nightly at https://wiki.gnucash.org/builds/win32/maint/.
Note the "latest" is the one dated most recently, not with the highest version number! (There's currently a bad build with number 3.900, but you'll want to test the most recent 3.1 build).
I'm still unable to reproduce this with https://code.gnucash.org/builds/win32/maint/gnucash-3.2-2018-09-17-git-3.2-276-g83b1b8adf+.setup.exe. Please do test!
I tried the versions 3.2 and 3.3 downloaded from the official website. The problem does not exist in these versions.
Excellent. Thanks for following up.
