Re: [Fedora-i18n-list] Using Japanese in KDE Apps Causes System Freeze

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yes, I recently enabled Xinerama, which is probably causing the
problems.  Any idea when there will be a fix?

On Tue, 2004-12-21 at 15:07 +0900, Akira TAGOH wrote:
> Hi,
> 
> >>>>> On Tue, 21 Dec 2004 00:44:12 -0500,
> >>>>> "morpheus" == morpheus <morpheus@xxxxxxxxxxxxxxxx> wrote:
> 
> morpheus> Hi,
> morpheus> I've stumbled across a major problem with iiimf.  Before, it was working
> morpheus> fine, but now when I try to use iiimf in KDE apps (konsole, quanta,
> morpheus> kedit) I get a system freeze and have to shut down my computer.
> morpheus> iiimf is working fine in Gnome apps.
> 
> How about on gtk2 apps? when I enabled Xinerama, I just saw
> the similar problem. and filed as Bug#134930. please follow
> up with your information if you like.
> 
> morpheus> How to Reproduce
> morpheus> -----------------
> morpheus> 1. Open quanta
> morpheus> 2. Press CTRL-SPACE
> morpheus> 3. Type Japanese (like bennkyou= べんきょう)
> morpheus> 4. Press SPACE to convert
> morpheus> 5. You only can see the first kanji displayed, second is blank space
> morpheus> (i.e. 勉)
> morpheus> 6. quanta app is now frozen and will not respond to any keyboard input.
> morpheus> You cannot turn off iiimf by pressing CTRL-SPACE again.  Also, HOME,
> morpheus> Backspace, ESC, CTRL-C, etc. do nothing.
> morpheus> 7. Next go to any other open KDE app (like konsole).  Even if you are
> morpheus> not using IIIMF and just try to type English, you can only type one
> morpheus> character then the app freezes.
> morpheus> 8. From now on all KDE apps are frozen and you must reboot.
> morpheus> 9. If you press CTRL-ALT-F1 to try to log on to a text console, the
> morpheus> system will freeze.
> 
> morpheus> This bug can be reproduced using the above steps 100% of the time.
> 
> morpheus> In /var/log/messages, I get the following errors:
> morpheus> Dec 21 00:20:19 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 6)
> morpheus> Dec 21 00:21:08 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 1)
> morpheus> Dec 21 00:21:08 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 6)
> morpheus> Dec 21 00:21:09 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 1)
> morpheus> Dec 21 00:21:11 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 1)
> morpheus> Dec 21 00:21:12 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 6)
> morpheus> Dec 21 00:21:12 enormousroom htt_server[2719]: Client shut down the
> morpheus> connection owned by im_id(1).
> morpheus> Dec 21 00:21:17 enormousroom htt_server[2719]: Client shut down the
> morpheus> connection owned by im_id(1).
> morpheus> Dec 21 00:21:17 enormousroom htt_server[2719]: status has not been
> morpheus> enabled yet. (1, 6)
> morpheus> Dec 21 00:21:20 enormousroom htt_server[2719]: Client shut down the
> morpheus> connection owned by im_id(1).
> 
> morpheus> The "status has not been enabled yet" happens thousands of times, and I
> morpheus> know there is a bug report open on this one.  But what is "Client shut
> morpheus> down the connection..."?
> 
> morpheus> My /var/log/iiim and /var/log/canna directories are empty.
> 
> morpheus> -m
> 
> 
> 
> 
> morpheus> --
> morpheus> Fedora-i18n-list mailing list
> morpheus> Fedora-i18n-list@xxxxxxxxxx
> morpheus> http://www.redhat.com/mailman/listinfo/fedora-i18n-list
> 
> --
> Fedora-i18n-list mailing list
> Fedora-i18n-list@xxxxxxxxxx
> http://www.redhat.com/mailman/listinfo/fedora-i18n-list
> 
> 



[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux