Aha! I just got it thanks your email and another helpful email from Gerd Hei�e. Once I'd finished the install in the chroot, I'd rebooted my machine fully into Debian.
I didn't have my network interfaces file set up correctly (I wasn't setting up the loopback interface (shows my inexperience with debian). I must have gotten the basis for my interfaces file from somewhere, but oh well. Here's what I added, maybe it's your problem too. auto lo iface lo inet loopback Good luck! -Scott On Mon, 2003-03-17 at 03:57, David Mccowan wrote: > I have had the same problems, with no luck at all in finding a solution. > > Have you found solution since your mail on the 14th? > > I personally am starting to believe that the reason gnome-session can > not > connect with gnome-smproxy is a hostname thing for the following reaons: > > 1. Most people do not have this problem. > 2. I can not get dict to connect dictd on my system. > 3. I can not get http://127.0.0.1/ to point to my system with apache or > any > other webserver running. > 4. Privoxy no longer runs. > > Every other system wide programm seems to runing fine and despite > checking my > hostname files I am still not entirely sure why gnome-session and the > above do > not work. > >
