View previous topic :: View next topic |
Author |
Message |
rommel Veteran
Joined: 19 Apr 2002 Posts: 1145 Location: Williamsburg Virginia
|
Posted: Fri Jun 07, 2002 6:13 pm Post subject: printer wont print |
|
|
well seems like somehow i lost the ability to print...i ahve tried reinstalling cups adn uninstalling and reinstalling the printer and driver but when i hit test the printer sounds like its initiating but then just never prints...the data led only blinks once when it is sent a job....the printer does work i reloaded windows on a machine to test it...i am clueless as to where to look ...anyone have a suggestion?
thanks
rommel |
|
Back to top |
|
|
FINITE Guru
Joined: 10 May 2002 Posts: 449
|
Posted: Fri Jun 07, 2002 6:24 pm Post subject: |
|
|
What type of printer is it? Make, model, usb or paralell? Do you have the device file lp0 in /dev/usb or /dev/printers? Is the usb module you recompiled the kernel with loading up correctly? Have you tried running cupsd in /etc/init.d to restart cups and then try and reconfigure the printer? Have you tried removing your printer all together and setting it back up? Have you checked to make sure your driver in /usr/share/cups/models is still there and didn't get modified somehow. Just some suggestions, hope this helps. If the printer was working fine and suddenly stopped you have to have changed something (things VERY RARELY happen just out of the blue). So if you did change something, what? Or should I ask, right before the printer stopped what was the last change you made? Its shouldn't be to difficult to take care of. |
|
Back to top |
|
|
rommel Veteran
Joined: 19 Apr 2002 Posts: 1145 Location: Williamsburg Virginia
|
Posted: Fri Jun 07, 2002 6:39 pm Post subject: |
|
|
its a parallel port printer...samsung laser b/w....i dont print very opften...just went to print a confirmation of an online order i had placed and it initiated...but then never printed....thats what it has been doing ever since...i have changed some things i am sure...like i think kde has been upgraded ...but i dont really remember when the last time it worked so i am not sure what i have added since....but i will check the things you suggested...i am sure it is something i have done but it is strange that it sounds as though it is recieving the print job then fails....so it is seen but then something goes wrong from there
edit: here is the output of the error log from cups.
I [07/Jun/2002:14:53:03 -0500] Job 6 queued on 'samsung' by 'root'.
I [07/Jun/2002:14:53:03 -0500] Started filter /usr/lib/cups/filter/pstops (PID 3696) for job 6.
I [07/Jun/2002:14:53:03 -0500] Started filter /usr/lib/cups/filter/cupsomatic (PID 3697) for job 6.
I [07/Jun/2002:14:53:03 -0500] Started backend /usr/lib/cups/backend/parallel (PID 3698) for job 6.
E [07/Jun/2002:14:53:04 -0500] PID 3697 stopped with status 32!
so it looks like its a filter configuration problem...but i am not sure how to correct it...yet...lol
edit again:....i was able to get a test page printed by unmerging ghostscript 7.xx and emerging the 6.53 version....but after i tried to print from an text edito in kde i got his error.
A print error occured. Error message received from system:
cupsdoprint -P 'samsung' -J 'modules.conf' -H 'localhost:631' -U 'root' -o ' copies=1 multiple-document-handling=separate-documents-collated-copies orientation-requested=3' '/tmp/kde-root/kdeprint_YKJfrnN' : execution failed with message:
client-error-not-possible
last edit:...well user error seems to be the issue again...uuuuggghh...the printer initiating but not completeing the print job was apparently due to the ghostscript upgrade....the second error messege was due to an idiot at the keyboard...i didnt reset the tab to allowed users in the printer setup and added myself and root to the denied user list...lol...its all working now...sorry for the post |
|
Back to top |
|
|
sarcaman n00b
Joined: 01 Aug 2002 Posts: 17
|
Posted: Sat Nov 22, 2003 12:15 am Post subject: |
|
|
Well I guess we are both stupid.
I had the exact same prob, but I was sure I had entered myself in Allowed users.
Turns out (on my kde 3.1.4 setup anyhow) that anyone entered in Allowed users is also entered in Denied users.... bizarre
Best thing seems to be to remove all from allowed and denied. |
|
Back to top |
|
|
|