Le dimanche 23 juin 2013 18:43:14, Osamu Aoki a écrit : > Hi, > > On Sun, Jun 23, 2013 at 05:17:56PM +0200, Thomas Preud'homme wrote: > > Le dimanche 23 juin 2013 16:21:22, Thomas Preud'homme a écrit : > > > Package: im-config > > > Version: 0.22-2 > > > Severity: normal > > > Tags: patch upstream > > > > > > It seems that 20_ibus.rc is ultimately sourced by the user's shell. > > Really? Why?
I don't know, as said I didn't manage to track down the cause. Maybe I'm wrong and it's executed by sh but the ls was not working on my system (the loop was not entered) exactly like zsh would. I assumed it was because the script is run at some point by zsh but I might be wrong and maybe dash act differently when sourcing something than when run in interactive mode (I made my debugging with dash in interactive mode). > > im-config is bash script. Being sourced ultimately by /etc/X11/Xsession.d/70im-config_launch, it should be a sh script. > > Isn't your X boot process uses /bin/sh? It does I think since the first version of the patch was not working with dash and prevented me from booting. As I said, somehow the file is read twice. > > There is no need to read im-config related file from .profile etc. I didn't do anything of that sort. As far as X is concerned, my system is untouched (at least AFAIK). I tried to display /proc/$PPID/exe from that file and redirecting the output in a file on /tmp but the file was empty so I can't know for sure what's happening exactly. Best regards, Thomas
signature.asc
Description: This is a digitally signed message part.
