On Mon, Mar 30, 2009 at 05:06:28PM +0200, Bill Allombert wrote:
> On Mon, Mar 30, 2009 at 04:48:51PM +0200, annonygmouse wrote:
> >
> > Just let you know that it renders my system un-updateable.
> > It's a chroot 32bits into an amd64...
> >
> > aptitude install xeyes
> > E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
> > correct the problem.
> > ....
> >
> > debianmbp:/# dpkg --configure -a
> > Setting up menu (2.1.41) ...
> > perl: warning: Setting locale failed.
> > perl: warning: Please check that your locale settings:
> > LANGUAGE = (unset),
> > LC_ALL = (unset),
> > LANG = "ca_ES.UTF8"
> > are supported and installed on your system.
> > perl: warning: Falling back to the standard locale ("C").
> > Setting up libgnomevfs2-common (1:2.24.0-3) ...
> > close failed: [Errno 9] Bad file descriptor
> > Traceback (most recent call last):
> > File "/usr/sbin/gconf-schemas", line 82, in <module>
> > pids=os.popen('pidof gconfd-2').readlines()[0].split()
> > IOError: [Errno 9] Bad file descriptor
> > dpkg: error processing libgnomevfs2-common (--configure):
> > subprocess post-installation script returned error exit status 1
>
> This is interesting, because /usr/sbin/gconf-schemas alos use popen
> and is get a Bad file descriptor, exactly the same issue than menu
> has.
>
> So this stringly suggest that popen is broken by some libc6/kernel
> version.
>
> I will report that to the libc6 package.
Done: this is bug #521863
I am confused about one point:
You all seems to run kernel 2.6.26-1-amd64, however there are two
such kernels: the debian-amd64 one and the debian-i386 one.
Are you running the kernel from debian-amd64 or debian-i386 ?
Are you running the userland from debian-amd64 or debian-i386 ?
However, I can now reproduce the problem in a debian-i386
chroot on top of the debian-amd64 2.6.26-1-amd64 kernel.
Cheers,
--
Bill. <[email protected]>
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
