I saw this bug report and noticed it had not been updated since 2006. I just wanted to report that the problem still exists. Spent a lot of time banging my head against a wall trying to figure out what was going on until I had a "duh" moment and checked the old bug reports and found this. Populating the domains file even with a bogus entry (like foo.bar) will take care of the problem, but it can be very frustrating for a user who does not realize it.
Here is the information on the version I am running: Package: squidguard Version: 1.2.0-8.2 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-4-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages squidguard depends on: hi debconf [debconf-2.0] 1.5.11etch2 Debian configuration management sy hi libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries hi libdb4.3 4.3.29-8 Berkeley v4.3 Database Libraries [ hi liburi-perl 1.35-2 Manipulates and accesses URI strin hi libwww-perl 5.805-1 WWW client/server library for Perl hi perl 5.8.8-7etch3 Larry Wall's Practical Extraction hi squid 2.6.5-6etch4 Internet Object Cache (WWW proxy c -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
