Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 497946 - ibus-daemon should not fail silently
Summary: ibus-daemon should not fail silently
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: imsettings
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
 
Reported: 2009-04-28 02:44 UTC by Warren Togami
Modified: 2009-10-08 12:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-08 12:24:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Warren Togami 2009-04-28 02:44:20 UTC 
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"
Comment 1 Peng Huang 2009-05-08 06:35:59 UTC 
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.
Comment 2 Akira TAGOH 2009-05-08 08:37:08 UTC 
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.
Comment 3 Peng Huang 2009-05-25 09:15:07 UTC 
(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.
Comment 4 Bug Zapper 2009-06-09 14:41:32 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Akira TAGOH 2009-08-20 10:21:57 UTC 
Fixed in imsettings-0.107.1-2.fc12.
Note You need to log in before you can comment on or make changes to this bug.