Your message dated Sun, 15 Jul 2007 13:38:30 +0200 with message-id <[🔎] 200707151338.36092.Martin@Lichtvoll.de> and subject line kdeprint can't connect to cups server through socket seems to be fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kdeprint can't connect to a freshly installed and running CUPS 1.2 server
- From: Martin Steigerwald <Martin@Lichtvoll.de>
- Date: Thu, 15 Jun 2006 11:33:31 +0200
- Message-id: <20060615093330.6063.23156.reportbug@deepdance.home>
Package: kdeprint Version: 4:3.5.3-2 Severity: important Hello, after I found CUPS non working again - problems started with the update to version 1.2 - I decided to create a clean-room environment by purging CUPS, removing all leftovers and re-installing and re-configuring it from scratch. This time it wouldn't print anything (see last tried with kdeprint in debugn bug #335483). The jobs have been queed nicely but then it just didn't print, no messages in error_log despite LogLevel debug. I can't tell more about this, cause I of my clean-room approach to get things working as quickly as possible. This time I used the web interface of CUPS itself to configure the printer, cause I read about problems with kdeprint in another debian bug report (see debian bug 345973). Since CUPS didn't recognize the PPD files from cupsys-driver-gutenprint, I manually choosed and uploaded the right one to the CUPS server on localhost. /usr/share/cups/model/gutenprint/5.0/en/stp-escp2-600.5.0.ppd.gz Now I was able to print the test page and it even worked okay. Thus I wanted to test with kdeprint, too... It said "Initializing manager" and then gave the following error: "Liste der Drucker lässt sich nicht übertragen. Fehlermeldung des Verwaltungsprogramms: Verbindung zu CUPS-Server fehlgeschlagen. Überprüfen Sie, ob der CUPS-Server korrekt installiert wurde und aktiv ist. Fehler: Rechner ist nicht auffindbar." Roughly translated: "List of printers could not be transferred. Error of the manager program: Connection to CUPS server failed. Please check whether it has been installed correctly and is active. Error: Host not found." It showed that error message while CUPS on localhost was happily printing another testpage. The loopback interfaces is available, "localhost" as well as its other name "deepdance" can be pinged. After sending this report I will restart KDE and see whether the problem goes away. This has been the case on my last try with kdeprint. Still I report this now, cause for a novice user this behavior just is extremely irritating. Actually it seems that CUPS is listening just fine: root@deepdance:~ -> netstat -tulpen | grep cups tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 2208530 5725/cupsd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 2208532 5725/cupsd This is the contents of kdeprintrc: martin@deepdance:~/.kde/share/config -> cat kdeprintrc [$Version] update_info=kdeprintrc.upd:kde-3.1-toolbar [General] PrintSystem=cups [Jobs] Size=903,305 I didn't modify the cups configuration files manually, and since I purged them before, they should be distribution standard. This is the printer configuration: # Printer configuration file for CUPS v1.2.1 # Written by cupsd on 2006-06-15 11:06 <Printer EpsonStylusColor600> Info Epson Stylus Color 600 DeviceURI epson:/dev/lp0 State Idle StateTime 1150362311 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer </Printer> This is the CUPS version installed: ii cupsys 1.2.1-2 Common UNIX ii cupsys-bsd 1.2.1-2 Common UNIX ii cupsys-client 1.2.1-2 Common UNIX ii cupsys-driver-gutenprin 4.3.99+cvs20060521-4 printer driv ii libcupsys2 1.2.1-2 Common UNIX ii libcupsys2-dev 1.2.1-2 Common UNIX This all is with an Epson Stylus Color 600 connected to the port replicator for my ThinkPad T23 via parallel interface (the printer doesn't have USB). Regards, Martin -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.7-tp23-sws2-2.2 Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Versions of packages kdeprint depends on: ii enscript 1.6.4-9 Converts ASCII text to Postscript, ii kdelibs4c2a 4:3.5.3-1 core libraries and binaries for al ii libc6 2.3.6-13 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-4 GCC support library ii libqt3-mt 3:3.3.6-2 Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.0-4 The GNU Standard C++ Library v3 ii poster 1:19990428-8 Create large posters out of PostSc ii psutils 1.17-22 A collection of PostScript documen Versions of packages kdeprint recommends: ii evince [postscript-viewe 0.4.0-1 Document (postscript, pdf) viewer ii gnome-gv [postscript-vie 1:2.12.0-1 GNOME PostScript viewer ii gs-esp [postscript-viewe 8.15.1.dfsg.1-2 The Ghostscript PostScript interpr ii gs-gpl [postscript-viewe 8.50-1.1 The GPL Ghostscript PostScript int ii kghostview [postscript-v 4:3.5.3-1 PostScript viewer for KDE -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 373720@bugs.debian.org
- Cc: 373720-done@bugs.debian.org
- Subject: kdeprint can't connect to cups server through socket seems to be fixed
- From: Martin Steigerwald <Martin@Lichtvoll.de>
- Date: Sun, 15 Jul 2007 13:38:30 +0200
- Message-id: <[🔎] 200707151338.36092.Martin@Lichtvoll.de>
Hi! I configured KDEPrint to use /var/run/cups/cups.sock:631 again and printed some images. Seems to work nicely. So apparently this bug is fixed. I am using: shambala:~> echo "kdeprint cupsys cupsys-client libcupsys2 hpijs" | xargs -n1 apt-show-versions kdeprint/sid uptodate 4:3.5.7-2 cupsys/sid upgradeable from 1.2.7-4 to 1.2.11-3 cupsys-client/sid upgradeable from 1.2.7-4 to 1.2.11-3 libcupsys2/sid upgradeable from 1.2.7-4 to 1.2.11-3 hpijs/sid upgradeable from 2.6.10+1.6.10-3 to 2.6.10+1.6.10-4.1 Hmmm... seems there are some updates available. Okay, I upgraded to shambala:~> echo "kdeprint cupsys cupsys-client libcupsys2 hpijs hpijs-ppds" | xargs -n1 apt-show-versions kdeprint/sid uptodate 4:3.5.7-2 cupsys/sid uptodate 1.2.11-3 cupsys-client/sid uptodate 1.2.11-3 libcupsys2/sid uptodate 1.2.11-3 hpijs/sid uptodate 2.6.10+1.6.10-4.1 hpijs-ppds/sid uptodate 2.6.10+1.6.10-4.1 and printed another image. Still works fine. Thus I am closing my bug report. I did not use notfound tag, since actually I do not know whether it is a new kdeprint or a new cups that fixes the bug. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7Attachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---