Hi Frans, On Mon, 2008-12-29 at 11:42:46 +0100, Frans Pop wrote: > On Monday 29 December 2008, Raphael Hertzog wrote: > > Yet, it does look like some terminal capability to force caps is > > switched on and AFAIK dpkg doesn't have any code related to terminal > > configuration.
Right, I don't see how dpkg can be the culprit. > That was why I was not immediately worried when it happened for pbuilder. > But Debian Installer is a relatively clean and controlled environment, so > the fact that it happens there too is IMO an indication that some fairly > basic package is broken. You seem to be running it under virtualbox, did you run that pbuilder under some emulator as well, vbox or qemu? Which kind of output are you using, serial? > D-I itself certainly does not do anything strange re terminal > configuration in the /target chroot and I'd be surprised if debconf would > turn out to be responsible. > Also note that in D-I all output is redirected to syslog and not to a > terminal, although I guess terminal settings could still influence it. Who is responsible of redirecting the output to syslog? > > Or is it possible that some special character could be sent to the > > terminal resulting in such a configuration change on the fly? That's a usual login program behaviour, when they "detect" that the terminal is on capslock, or only supports one case, then they switch to map all input to lower case and all output to upper case. > I have no idea. I'm not all that familiar with terminal stuff. > Google tells me that stty does have command line options to change the > case of output. > > Any suggestions how we could debug this? > I guess it must be some script or command that is run in some cases but > not all. If we could find out what that is... Can you always reproduce it, and on the same spot? regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
