Sorry for my late reply. I think it would be ibus-anthy or ibus's problem.
At Wed, 7 Mar 2012 19:30:21 +0900 (JST), hachisukakorok...@yahoo.co.jp wrote: > And > ls -l /proc/PID/fd > shows like below; > lrwx------ 1 user user 64 2012-03-01 01:38 0 -> /dev/null > lrwx------ 1 user user 64 2012-03-01 01:38 1 -> /dev/null > lr-x------ 1 user user 64 2012-03-01 01:38 10 -> pipe:[12905] > lrwx------ 1 user user 64 2012-03-01 01:38 2 -> /dev/null > lr-x------ 1 user user 64 2012-03-01 01:38 3 -> pipe:[12906] > l-wx------ 1 user user 64 2012-03-01 01:38 4 -> pipe:[12906] > lrwx------ 1 user user 64 2012-03-01 01:38 5 -> socket:[12907] > lrwx------ 1 user user 64 2012-03-01 01:38 6 -> > /home/user/.anthy/last-record2_default.utf8 > lrwx------ 1 user user 64 2012-03-01 01:38 8 -> socket:[12894] > lrwx------ 1 user user 64 2012-03-01 01:38 9 -> pipe:[12905] I'm not familiar about ibus, but it seems a process linked with libanthy remained running, and ibus frontend process would be died. I'll try to make a Debian environment like you, and reproduce the issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
