Bug#392052: More info from someone with same problem
Christopher Martin wrote: Could you please upgrade your kdebase (and therefore kdeprint) to the version in Sid/unstable, 3.5.5? Then tell me if the problem persists (I guess you'll have to try printing with both Host=localhost and Host=127.0.0.1). Sorry to be a pain, but I want to be certain whether or not the problem still exists in 3.5.5, given that the Etch release isn't too far off. I was all set to do this, but then I thought why don't I try a normal dist-upgrade on testing first, just to make sure I'm current. That upgraded the following packages this morning: 2006-10-24 12:26:17 upgrade libsqlite0 2.8.16-1 2.8.17-1 2006-10-24 12:26:18 upgrade libslang2 2.0.6-3 2.0.6-4 2006-10-24 12:26:44 upgrade bittorrent 3.4.2-8.1 3.4.2-10 2006-10-24 12:26:48 upgrade devscripts 2.9.21 2.9.22 2006-10-24 12:26:49 upgrade discover1-data 1.2006.01.14 2.2006.10.12-1 2006-10-24 12:26:49 upgrade kdelibs-data 4:3.5.5a-1 4:3.5.5a.dfsg.1-1 2006-10-24 12:26:55 upgrade kdelibs4c2a 4:3.5.5a-1 4:3.5.5a.dfsg.1-1 2006-10-24 12:26:59 upgrade kdelibs 4:3.5.5a-1 4:3.5.5a.dfsg.1-1 2006-10-24 12:27:00 upgrade libggi2 1:2.2.1-4 1:2.2.1-5 2006-10-24 12:27:00 upgrade libgphoto2-2-dev 2.2.1-4 2.2.1-7 2006-10-24 12:27:02 upgrade libgphoto2-port0 2.2.1-4 2.2.1-7 2006-10-24 12:27:04 upgrade libgphoto2-2 2.2.1-4 2.2.1-7 2006-10-24 12:27:05 upgrade libxres1 2:1.0.0-3 2:1.0.1-2 2006-10-24 12:27:05 upgrade sqlite 2.8.16-1 2.8.17-1 2006-10-24 12:27:05 upgrade wwwconfig-common 0.0.46 0.0.47 2006-10-24 13:17:41 upgrade kappfinder 4:3.5.4-2+b1 4:3.5.5a-2 And... the problem has gone away on my machine, *without* upgrading kdebase or kdeprint. Hmmm. So, in an effort to be helpful, I started downgrading the above packages, and eventually found that downgrading kdelibs4c2a from 3.5.5a.dfsg.1-1 to 3.5.5a-1 caused the problem to start happening again. So: kdelibs4c2a 4:3.5.4-3 worked fine. kdelibs4c2a 4:3.5.5a-1 causes the problem. kdelibs4c2a 4:3.5.5a.dfsg.1-1 fixes the problem. This is definitely the case; again, downgrading back to kdelibs4c2a 4:3.5.5a-1 makes the problem start happening again. So, since 4:3.5.5a.dfsg.1-1 is now in testing, it's now solved as far as I'm concerned. Puzzling, though. -- Robert L Mathews, Tiger Technologieshttp://www.tigertech.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392052: More info from someone with same problem
I also recently (2006-10-22) did a dist-upgrade and started experiencing the same problem described here: nothing in KDE would print any more, and I saw the same error when looking at Printers in the KDE Control Center: Connection to CUPS server failed. Check that the CUPS server is correctly installed and running. Error: localhost: read failed (15). However, I am using the testing distribution, so my kdeprint is still version 3.5.4-2+b1, and kdebase is still 3.5.4-2. On other words, kdeprint has not changed for some time on my machine. What *did* change on my machine as a result of the dist-upgrade is most of the other KDE components (to 3.5.5). So I suspect the problem actually lies elsewhere (I don't know where). In response to the last poster, I looked at my ~/.kde/share/config/kdeprintrc file. It also has not changed in a long time, but I started playing with it to see if I could modify it to fix the problem. I found that this line in the [CUPS] section causes it to fail: Host=localhost But if I change that line to this, it works(!): Host=127.0.0.1 My machine has /etc/hosts set up correctly for localhost: $ host localhost localhost has address 127.0.0.1 So. This seems to indicate that some other KDE component in 3.5.5, other than kdeprint, has somehow broken the ability for hostnames to be resolved from kdeprintrc. Does that makes sense? Not to me. Hope it's useful to someone else If anyone cares, I can send along my /var/log/dpkg to show the exact 383 packages that were upgraded when the problem started. -- Robert L Mathews, Tiger Technologieshttp://www.tigertech.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392052: More info from someone with same problem
On Monday 23 October 2006 19:55, Robert L Mathews wrote: I also recently (2006-10-22) did a dist-upgrade and started experiencing the same problem described here: nothing in KDE would print any more, and I saw the same error when looking at Printers in the KDE Control Center: Connection to CUPS server failed. Check that the CUPS server is correctly installed and running. Error: localhost: read failed (15). However, I am using the testing distribution, so my kdeprint is still version 3.5.4-2+b1, and kdebase is still 3.5.4-2. On other words, kdeprint has not changed for some time on my machine. What *did* change on my machine as a result of the dist-upgrade is most of the other KDE components (to 3.5.5). So I suspect the problem actually lies elsewhere (I don't know where). Could you please upgrade your kdebase (and therefore kdeprint) to the version in Sid/unstable, 3.5.5? Then tell me if the problem persists (I guess you'll have to try printing with both Host=localhost and Host=127.0.0.1). Sorry to be a pain, but I want to be certain whether or not the problem still exists in 3.5.5, given that the Etch release isn't too far off. Thanks, Christopher Martin In response to the last poster, I looked at my ~/.kde/share/config/kdeprintrc file. It also has not changed in a long time, but I started playing with it to see if I could modify it to fix the problem. I found that this line in the [CUPS] section causes it to fail: Host=localhost But if I change that line to this, it works(!): Host=127.0.0.1 My machine has /etc/hosts set up correctly for localhost: $ host localhost localhost has address 127.0.0.1 So. This seems to indicate that some other KDE component in 3.5.5, other than kdeprint, has somehow broken the ability for hostnames to be resolved from kdeprintrc. Does that makes sense? Not to me. Hope it's useful to someone else If anyone cares, I can send along my /var/log/dpkg to show the exact 383 packages that were upgraded when the problem started. -- Robert L Mathews, Tiger Technologieshttp://www.tigertech.net/ pgpt2A0z2gLuo.pgp Description: PGP signature
