[Pkg-ime-devel] Bug#683950: Bug#683950: im-config: alter the way of starting during Xsession startup

Osamu Aoki osamu at debian.org
Wed Aug 8 13:11:37 UTC 2012


Hi,

On Wed, Aug 08, 2012 at 12:35:59AM +0800, Aron Xu wrote:
...
> Actually the patch I've given you is a work of 2 hours... There must
> be things can be improved a lot. I haven't tried to see if using
> `exec` at the end can work, and this is a good point for me to try
> out.

... but this makes me feel uncomfortable to aim for wheezy, though.
 
> As for the loop at the end, it doesn't cause any more CPU load because
> the actual wait command is "read -p > /dev/null", and the while loop
> is just in case that the `read` call terminates unexpected.

I see
 
> > By the way what is the process tree of your system?  My system around gdm3 and ibus are:
> > $ ps auxf |less
> > ....
> 
> > I do not have time to do more testing.... sorry.
> >
> 
> I'm away from my working computer for about a week, and now using an
> old Ubuntu 10.10 installation with im-switch, it's hard to test out
> the new stuff right now. There should be only a im-launch process left
> running background with almost no CPU load, and a minimal memory
> consumption of a dash process (< 2MiB). The `exec` idea may help us
> save this 2MiB, though.

I think memory saving is not so critical issue.  The most critical issue
is side effects of changes.  

Have you studies dbus-launch code?  There is some interesting comment in
the source of dbus: dbus-1.6.2/tools/dbus-launch.c

Once we do this, we may be able to make stable update case strongly.

I do not have much time now.  So I want to go slow on this update.

By the way, are you aware of some case where IM daemon go crazy not
finding dbus.  Most of them wait for some time.  So this should not be a
serious bug and that was why we never got to work on this.

Osamu




More information about the Pkg-ime-devel mailing list