You are not logged in.
Hello,
Sorry I don't know which is the appropriate forum to post in. I assumed this is suitable.
My problem started once I upgraded samba to the latest version, before I was happy to share and print without hassle.
I fought for the shares and I solved, but printing seem very hard to find a clue.
My childs using Arch and Ubuntu, but that isn't the real matter. I found in /var/log/samba this statement
lpr: The printer or class does not exist.
Also when I tried in the shell:
echo hello | lpr -P
The result is the same.
My printer is a HP DeskJet1050 and I've installed hplip for all the computers needing to print.
I've inserted the user:password on the printer address but no printout, even if client states job completed
For what I suppose, the printing reach the server but it is somehow stopped by CUPS or its subsystem.
In the CUPS log
W [12/Jun/2013:10:45:41 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_Deskjet_1050_J410_series-Gray..' already exists
W [12/Jun/2013:10:45:41 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_Deskjet_1050_J410_series-RGB..' already exists
W [12/Jun/2013:10:45:41 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'Virtual_PDF_Printer-Gray..' already exists
W [12/Jun/2013:10:45:41 +0800] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'Virtual_PDF_Printer-RGB..' already exists
E [12/Jun/2013:10:46:06 +0800] Unable to communicate with avahi-daemon: Daemon not running
For avahi I've found that its group was missing, but at moment no printing.
Last edited by TheSaint (2013-06-15 00:42:54)
do it good first, it will be faster than do it twice the saint
Offline
How to release some security tightening?
It's only a matter to print few pages for a family members.
do it good first, it will be faster than do it twice the saint
Offline
That lpr message suggests that the default printer is not set. Have a look at man lpr for a brief discussion of it. You can set the default in the Cups admin, or using one of the methods in the man page.
Alternatively you could try printing to a printer by name (by passing it in as an argument to lpr - again see the man page) as a check that the printer is set up.
Once lpr works locally first, then look at the Samba issue.
Unfortunately I had issues there myself and went to printing to Cups directly via port 631 (though I subsequently think the issue could have been with a damaged Windows printer driver, I haven't moved back as it's all working and I need it for work).
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
My bad.
I set the wrong printer name on the /etc/samba/smb.conf
That was my doubt. The name must reflect the CUPS name, when that printer setup is done.
do it good first, it will be faster than do it twice the saint
Offline