Thanks, I'll try to find this myself. As for chromium, I'm talking about squeeze one, of course.

// Edit

OK; now I feel ashamed - offending entry about Testing was in /etc/apt/apt.conf. removing file (or it's content) did the trick.

Resolved:

It turned out, that I had spurious file /var/lock/qmount-complete in my ED backup image (which I used to extract ED from). Normally, this file would be deleted on closing chroot, but due to it's existence (and content, originating from using dedicated partition and mounting it as /.debian), qchroot got confused, and skipped whole part of script, responsible for mounting hardware, dbus, and friends.

In itself, it wouldn't be big deal, as spurious file would get deleted on closing chroot, and new one (with correct content) would be created on new start of ED (i closed and opened it many times). Hoever, here interfered effect of my stupid idea, to unpack ED into /home/.debian, yet, create symlink pointing to it, from /.debian - and use the latter as chroot dir.

Yea, I have no idea what I was thinking yesterday - this was completely unnecessary complication, and only reason for it, was that I was using /.debian as mount point for dedicated partition in past, and had it already in .chroot config file. Instead of just changing it to /home/.debian, I created mess by symlinking :stupid: (which was more work than just fixing it in config, anyway, especially, that I had to put "none" for IMG= in config, no matter what...)

Even leaving my stupid idea aside, it *should* work, and worked for most things, *except* for what it was intended for (Maemo knew about symlink, but ED couldn't from it's chroot jail, so, despite having all things mounted to /.debian/*, /home/.debian couldn't use it), *and* closechroot. Method of unmounting things in the latter isn't bulletproof enough to determine symlinks - it checks /proc/mounts for names containing path to chroot (which was symlink), while /proc/mounts have symlinks targets listed there, not symlinks themselves (obviously).

This left me with whole lotta mess of remaining "ghost mounts". I cleared all of it, got rid of symlink, and voila, everything works. Lesson earned - really think twice, before getting such stupid ideas s symlinking chroot dir :P
---

The plus is that, while searching for case, I went through reading all ED (and, generally, easy-chroot) components - refreshing my idea about what is there, and what isn't. It seems, that my knowledge raised much since last time I've seen them - this time, I wasn't having problems understanding what is going on and why (which explains, how pitifully low my level of understanding was back then, few months ago :P ).

As a result, I fixed some routines that were less-than-bulletproof, some trivialities, and added new functionality here or there (like ability to define custom string of filesystem options in .chroot config file, instead of hard-coding it into easy-chroot's guts, everytime we want to use dedicated partition with some optimized mount-time parameters.

IF autobuilder is going to ever start working again, I'll try packaging it up, and releasing first update to easy-debian main package in a years (wooho!). Of course, my little tweaking is just an addition - mostly, it will contain various bugfixes scattered around this thread (like the ones allowing to seamlessly using directory for chroot, instead of dedicated partition or IMG file.)

/Estel