Bug 496546

Summary: libimsettingss-xim-WARNING **: Child sequence won't be matched.: <Multi_key> <apostrophe> <cedilla> <C> : "Ḉ" U1E08 # LATIN CAPITAL LETTER C WITH CEDILLA AND ACUTE
Product: [Fedora] Fedora Reporter: morgan read <mstuff>
Component: imsettingsAssignee: Akira TAGOH <tagoh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: i18n-bugs, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-20 08:44:05 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
Bug report as re Description
Bug report as re Description none

Description morgan read 2009-04-19 22:08:37 EDT
Created attachment 340272 [details]
Bug report as re Description

Description of problem:
Not quite sure, got a but-report & saved them.  Now posting bug-reports.  From the reports it's something to do with libimsettings

Version-Release number of selected component (if applicable):
See bug report

How reproducible:
I've disabled input method feature, but got the two bug reports attached before I did

Steps to Reproduce:
1. Enable IM 
Actual results:
Bug reports

Expected results:
No bug reports

Additional info:
Comment 1 morgan read 2009-04-19 22:09:46 EDT
Created attachment 340273 [details]
Bug report as re Description
Comment 2 Akira TAGOH 2009-04-20 04:10:06 EDT
Which version of imsettings and libgxim do you use? try rpm -q imsettings libgxim.
Comment 3 morgan read 2009-04-20 05:32:17 EDT
Hmm, good question...  Those attachments have been on my Desktop for a good few weeks now.

This is what I have now:
$ rpm -q imsettings
$ rpm -q libgxim

I keep stuff fairly up to date, looking at my logs it seems the above version of imsettings was installed 31/3/09, and there's no updates before that - so, it's almost certain the bug reports were generated for the version immediately prior to the above.

Seems libgxim updated:
Mar 03 21:43:14 Updated: libgxim-0.3.2-3.fc10.i386
And, then to the above version on 5/3/09.  So, quite possibly the bug reports were generated for the above libgxim (libgxim-0.3.2-4.fc10.i386).

Hmm, shame bug-buddy doesn't include the version in it's reports...  (Kind'a a bug in it's self...)
Comment 4 Akira TAGOH 2009-04-20 08:44:05 EDT
Great. then you just need to restart your desktop or imsettings-applet correctly to apply the changes happened with those updates. that warning has been gone on the updates.