Installed printer won't print after first shutdown

bylsteel · 03-16-2008, 11:05 PM

A successfully installed and printing HP psc 1350 will not print an reboot after shutdown, or even if turned off and on again.

I think it has something to do with the printer queue

cmnorton · 03-17-2008, 08:19 AM

Which distro are you running?

Have you tried starting a browser and entering localhost:631 and logging in as root where prompted?

jsurles · 03-17-2008, 11:41 AM

did you restart cups after the reboot?

cmnorton · 03-17-2008, 02:31 PM

Quote:

Originally Posted by jsurles

did you restart cups after the reboot?

Unless CUPS wasn't chkconfig'd why would a manual restart be needed?

jsurles · 03-17-2008, 11:46 PM

Quote:

Originally Posted by cmnorton

Unless CUPS wasn't chkconfig'd why would a manual restart be needed?

I'm really not sure what "chkconfig'd" is.. but unless there is an rc script setup to start it up, it's not going to start at boot. I guess unless chkconfig is something that is done through the gui maybe?

On all my machines I use rc scripts to start/stop services at the appropriate runlevels.. except for gentoo.. I guess they are essentially the same, bu they aren't called "rc" scripts.. heh. I don't think.

tredegar · 03-18-2008, 07:27 AM

Is cups running?

Code:

ps -A | grep cups

will tell you. An output something like this

Code:

5722 ?        00:00:00 cupsd

means that it is.

cmnorton · 03-18-2008, 08:19 AM

Quote:

Originally Posted by jsurles

I'm really not sure what "chkconfig'd" is.. but unless there is an rc script setup to start it up, it's not going to start at boot. I guess unless chkconfig is something that is done through the gui maybe?

On all my machines I use rc scripts to start/stop services at the appropriate runlevels.. except for gentoo.. I guess they are essentially the same, bu they aren't called "rc" scripts.. heh. I don't think.

On rpm-based systems chkconfig is used to set establish that a daemon starts and stops automatically and also sets the affected run-level for that to happen. On Debian-based systems, use update-rc.d. Some daemons actually have the checkconfig line built in. This is ours to get the Informix daemon to run: # chkconfig: 2345 12 78

I would have thought CUPS would be scripted to start and stop by the installation program.

bylsteel · 03-21-2008, 11:39 AM

Appreciate discussion on the "won't print" printer
on openSuse 10.3 /Linux 2.6.22.17
RESPONDS to ps -A | grep cups WITH 3328 ? 00.00.00 = CUPS RUNNING
so far so good, but
localhost: 631 revealed a long list of jobs on hold.
Cannot find the way to release printer, and keep it that way.

tredegar · 03-21-2008, 12:16 PM

Quote:

localhost: 631 revealed a long list of jobs on hold.

Then the first thing to do is probably delete them, or you'll be deluged with paper when you do get it working!

Make sure your printer is Online (Check the On/Resume light)

Perhaps your printer has been "Disabled" somewhere in cups. Login to http://localhost:631 and have a thorough nosy around the menus.

Have you seen here: http://www.linuxprinting.org/show_pr...um=HP-PSC_1300

And here: http://www.linux-foundation.org/en/O...SDocumentation
-- Particularly [7] "Avoid your print queue being automatically disabled....This makes the behaviour of CUPS on errors during the communication with the printer (e. g. printer turned off) configurable instead of CUPS simply disabling the queue. "

If nothing there, try re-installing your printer with the Cups Administration - Add Printer menus.