Can't print after Slack 10.1 upgrade.

[Gallienus]

Not that long ago I upgraded from slack 10 to 10.1. Now cups is no longer working. all I get when I try to access cups at http://localhost:/631 is connection refused.

I've done a few searches here and on the web but nothing seems to apply. I've also tried ./cups restart cups restart and that didn't seem to help either.

Has there been a configuration change from slack 10 to 10.1 that affects cups starting?

any help is appreciated.

[Hayl]

in this case (as in all others) the first thing you should do is refer to the cups log files (and any other relevant system logfiles).

if they are not detailed enough, then look in the cups configuration files and see if you can up the level of logging and then relook at them.

if you can't figure it out fom the logs, perhaps post the logs for people on here to look through in case they see something that you miss.

also, perhaps the config gets overwritten (to some default that is not optimal for whatn you want) when upgraded under slack?? i dunno. look through the cups config and check for anything that restricts users/groups who can / can't print or even system names/ip address, etc that may be restricted.

[soulestream]

have you tried reinstalling cups?

soule

[MMYoung]

1. Make sure CUPS is running.
2. If it ain't then make sure /etc/rc.d/rc.cups is set to load at boot. It has to be executable. You can do that by issuing this command from a root terminal:
chmod 755 /etc/rc.d/cups
3. If it ain't running, and you've made it executable as in 2, then just issue this command, again from a root terminal:
/etc/rc.d/rc.cups start

You should get a message saying that the cupsd scheduler has started. Close the terminal and open your browser and see if you can open localhost:631 now.

HTH,
MMYoung

[Gallienus]

After poking around the directories of two different slack pc's my machine and the one downstairs, which had a botched upgrade and the cups and alsa problems, I found the trouble.
For whatever reason the rc.cups file was not marked executable. Once I did that I had no problems getting the computer to print.