Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Summary: ibus-daemon should not fail silently
https://bugzilla.redhat.com/show_bug.cgi?id=497946
Summary: ibus-daemon should not fail silently Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: ibus AssignedTo: phuang@redhat.com ReportedBy: wtogami@redhat.com QAContact: extras-qa@fedoraproject.org CC: phuang@redhat.com, fedora-i18n-bugs@redhat.com Estimated Hours: 0.0 Classification: Fedora Target Release: ---
ibus-1.1.0.20090423-1.fc11
Currently ibus-daemon can fail to startup under certain circumstances like socket directory owned by another user. It currently fails silently, so the user has no idea why it failed.
ibus-daemon should pop-up and tell the user it failed to start, and why.
ibus-daemon should probably run: ibus-x11 --fail "fail message here"
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
Huang Peng phuang@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tagoh@redhat.com
--- Comment #1 from Huang Peng phuang@redhat.com 2009-05-08 02:35:59 EDT --- What's kind of message should be show to uers? need detail of fail reason?
I have another suggestion, let im-settings to show the error messages to user. It will benefit scim and other im too.
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 #2 from Akira TAGOH tagoh@redhat.com 2009-05-08 04:37:08 EDT --- 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.
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@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.
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
Huang Peng phuang@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|ibus |imsettings AssignedTo|phuang@redhat.com |tagoh@redhat.com
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
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|11 |rawhide
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
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
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
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |473302(F12Target)
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
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED
--- Comment #5 from Akira TAGOH tagoh@redhat.com 2009-08-20 06:21:57 EDT --- Fixed in imsettings-0.107.1-2.fc12.
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
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |CLOSED Resolution| |RAWHIDE
i18n-bugs@lists.fedoraproject.org