Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=497946
--- Comment #3 from Huang Peng <phuang(a)redhat.com> 2009-05-25 05:15:07 EDT ---
(In reply to comment #2)
Well, imsettings is capable to catch up the fail but in this case it
won't
grabs so that it happens later. imsettings needs to watch the child status
during it's alive then. aside from that, there are no clients to display the
error so far since applet isn't running by default. I'm not quite sure if
contacting to notification-daemon directly from the dbus service is the right
design.
Anyway, in either cases, what it can says is, "Input Method died unexpectedly.
I don't know why. the error code was blahblahblah. over." we may need any way
to know the detailed human-readable reason for usability.
I think imsetting could log input method's error output in a file, and ask user
to check it.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.