| Autor | Nachricht | 
  
    |  | 
        
					| Titel:  Verfasst am: 18.07.2006, 05:59 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 05. Dez 2005
 Beiträge: 414
 Wohnort: Auckland, New Zealand
 
 |  | 
        
          | Hmmm didn't seem to stick ... I'll try again. |  
          | _________________
 Linux is evolution, not intelligent design - Linus Torvalds
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 18.07.2006, 12:33 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 05. Dez 2005
 Beiträge: 414
 Wohnort: Auckland, New Zealand
 
 |  | 
        
          | Still didn't work ... tried Piper's full method and still no good for me ... but I tried monkymind's method and it worked for open office (but not for some other apps, but at least I can now print from open office) ... thanks monkymind! |  
          | _________________
 Linux is evolution, not intelligent design - Linus Torvalds
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 18.07.2006, 13:15 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 05. Dez 2005
 Beiträge: 414
 Wohnort: Auckland, New Zealand
 
 |  | 
        
          | Ahhh I missed your post 2radical and when I edited out "Listen /var/run/cups/cups.sock" from /etc/cups/cupsd.conf and then /etc/init.d/cupsys restart ... now it's okay for the other apps like KWrite. 
 I haven't tried reinstalling "cupsys-driver-gutenprint" or "hplip" or "kdeprint" yet.
 |  
          | _________________
 Linux is evolution, not intelligent design - Linus Torvalds
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 19.07.2006, 08:42 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 21. Aug 2004
 Beiträge: 123
 
 
 |  | 
        
          | Swynndla hat folgendes geschrieben:: 
Ahhh I missed your post 2radical and when I edited out "Listen /var/run/cups/cups.sock" from /etc/cups/cupsd.conf and then /etc/init.d/cupsys restart ... now it's okay for the other apps like KWrite.
 I haven't tried reinstalling "cupsys-driver-gutenprint" or "hplip" or "kdeprint" yet.
 I also used 2 radical's tip of commenting out "Listen /var/run/cups/cups.sock" when I edited cupsd.conf to make the local printer accessible across the network but had no idea what I had done, or added, enabled me to print again.
 
 My hplip and kdeprint is working. Probably sheer luck again.
   
 Cheers
 rob
 PS Belated thanks to 2radical
  |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 20.07.2006, 12:27 Uhr |  | 
  
    | 
        
          | Team Member 
  
  
 Anmeldung: 04. Apr 2006
 Beiträge: 153
 Wohnort: Melbourne, Australia
 
 |  | 
        
          | For those of you whom are still experiencing probems of /var/run/cups/cups.sock still showing up after you have edited etc/cups/cupsd.conf , put a # at the begining of the edited line eg 
 Listen localhost:631
 #
 
 (where the #= what was /var/run/cups/cups.sock
 
 then /etc/init.d/cupsys restart
 
 Only then reinstall hplip and gutenprint (i purged and reinstalled cupsys first, then did the edit followed by a reinstall of  cupsys-driver-gutenprint hplip
 |  
          | _________________
 Kanotix Easter RC4 on a dual boot P4 and a production box  Desktop KDE::
 Kanotix 2006 Easter RC4 on a P2 and  Production Box , Desktop KDE::
 Kanotix EasterRC4 on a MMX 199Mhz lappy
 and  a  Production Box,  Desktop ICEWM::
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 22.07.2006, 07:27 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 05. Dez 2005
 Beiträge: 414
 Wohnort: Auckland, New Zealand
 
 |  | 
        
          | Well, I eventually configured the pc where the printer is connected to allow others to print to it ... ie in https://localhost:631/admin I ticked: - Show printers shared by other systems
 - on Share published printers connected to this system
 - on Allow remote administration
 - on Allow users to cancel any job (not just their own)
 ... and then on the remote pc I when to print from kedit but it had the usual error ... so I did the 'ol trick:
 apt-get remove --purge cupsys
 apt-get install cupsys
 ... and now I can print from the remote pc just fine ... and /etc/cups/cupsd.conf still has "Listen /var/run/cups/cups.sock" uncommented! ... perhaps it doesn't matter on the remote pc.
 |  
          | _________________
 Linux is evolution, not intelligent design - Linus Torvalds
 |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 26.07.2006, 22:26 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 05. Dez 2005
 Beiträge: 414
 Wohnort: Auckland, New Zealand
 
 |  | 
        
          | So in summary, to fix my printing problems, I think I did the equivalent of: 
 Code: 
apt-get remove --purge cups* xprint*
apt-get install printconf hplip libprinterconf0c2a
 ... edited out "Listen /var/run/cups/cups.sock" from /etc/cups/cupsd.conf
 
 Code: 
/etc/init.d/cupsys restart
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 24.11.2006, 02:48 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 17. Okt 2006
 Beiträge: 2
 
 
 |  | 
        
          | I had similar problems after installing Kanotix 2006.1 RC4 on my hard drive. I could not get Kprinter to work. I would get the "cannot create temporary printer" message whenever I got to the test printer stage. I could install a printer using the web interface, but the printers (a parallel port HP9650 and a Smasung Color Laserjet wireless) would not print.
 I had the same problem with a vanilla Debian64 installation.
 I finally took the drastic step of completely removing all cupsys related files using synaptic and all ppd files. This wound up removing most of kde also. But when I reinstalled everything in Kanotix and the Debian64, I can add printers via kprint and they print as advertised.
 I do not know what the root of the problem is, and it would be no fun on a dial-up connection, but that is the only way I know to get everything working properly. At least it worked for me, twice.
 Just my two cents worth.
 
 Glenn
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
  
    |  |