On 4/17/06, Tom Worley <[EMAIL PROTECTED]> wrote: > > I had this exact same problem when doing a fresh install on unstable, I > managed to get around it by just doing: "apt-get remove discover" > As mentioned earlier, it must be a discover problem in the script. > Apparently this also gets around bug #363021
Thanks! Indeed this worked around the problem for me. I was hit by #362891. -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein
