[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

ACK: withdrawal of scim NMU



Hi,

On Sat, Oct 18, 2008 at 01:22:52PM +0800, Deng Xiyue wrote:
> Indeed.  The really problem resides in libX11, and the libX11 patch in
> the same bug report is the real fix.  The one I mentioned is just a
> workaround in scim side.  See below.
> 
> > As I reread your bug report, massive tab is the case you expeienced
> > input locking.  Is this SCIM problem?  Are you sure?  Did you make some
> > analysys using GDB to prove it? 
> > 
> > I have sort-of freeze situation sometimes but that is when I have
> > keyboard accessibility enabler capability via keyboard option set.  Of
> > course by discarding input queue, system will not cause such problem but
> > that is not right thing to do.  Just unclick gnome option for that or
> > carefully shrink windows to find prompt from accessibility program and
> > disable its activation.  (I know it was annoying ...)
> > 
> > As I also see that libX11 issue.  It has been updated since then.  Do
> > you know the situation?
> 
> Sorry for this, as I'm not subscribed to bug#437437, which I should, and
> #434180 is not blocked by it, I wasn't aware the proper fix has gone in
> libx11, where the really cause located.  

Not everyone uses all the fancy features of recent BTS. :-)

This means this is fixed.  I am closing this bug.

> Plus the feedback in launchpad bug report, and other BTS such as
> fedora, I think now this bug can be reassigned to libx11 and marked as
> done with
>  
> Source-Version: 2:1.1.4-1
> 
> As for the accessibility problem you mention, it might because the fix
> for libx11 side is incomplete, but I'm not the expert in this regard.

I was not clear but let's leave it now.  It is not a bug.

Osamu


Reply to: