On Thu, 6 Jun 1996, Ian Jackson wrote:
> This means that SIGPIPE was set to SIG_IGN when dpkg started. For
> reasons too complicated to explain here this means that dpkg can't do
> proper error trapping (it always gets an error indication, and can't
> tell whether it's really an error).
>
> This is a bug in one of:
> Your inetd, telnetd, rlogind, if you're logging in over the
> network (some versions of the Debian netbase and/or netstd
> packages had this problem).
I get that problem when locally su-ing in an xsession
> Your shell (I know of no shells that cause this problem).
I am using tcsh in my user account but when su and root's shell is bash.
> The getty you're using.
> (Some versions of getty_ps are known to have this problem.)
It's an X session, no getty should be involve
> The login you're using (I know of no problem here).
> Any program which started one of the above, or which is in
> the calling chain for dpkg.
>
tcsh -> rxvt/xterm -> su -> bash -> dpkg
so I guess it would either be tcsh or rxvt/xterm.
[stuff removed]
> Alexander Goldstein writes ("Re: gzip and dpkg problem"):
> ...
> > I also often have the same problem sometimes (with some packages). It
> > only happens when su-ing to root. To bypass it, I just login directly as
> > root on a VC. I have 1.1 system and it happened with all versions of dpkg
> > including as far way back as .96R6.
>
> Huh ? `su' does this ? I don't believe it ...
>
> ... no, `su' doesn't. Perhaps you have `sudo' or something else in
> the calling chain.
no, no sudo, but there is either rxvt or xterm and tcsh
>
> Please try to identify what it is that's causing the problem, so that
> we can fix it and/or tell others to avoid it :-).
>
I will try to test it better when I get home.
