I've been trying to install an HP PSC 1350 (all in one) printer for the greater part of a month now.
I found new driver package dtd. 5July on the Sourceforge and downloaded it. When I tried to configure it, I kept running into the same error Msg: "Cannot find net-snmp support (or --disable-network-build). I finally figured out that the error Msg. was actually giving me the argument for the ./configure command. But, before I figured that out, I went into YAST and began deleting certain snmp files and the Samba files.
I run a single machine with Suse 9.1 and have no need for networking.
Sorry for the long winded background.
The problem is that after I configured, make, make install, I can't complete the YAST configuration routine. YAST finds the printer ok, it sets up the USB port and necessary driver, files etc. but as soon as I try to test the printer I get:
Error: CUPS daemon died during initialization
or,
If I try to see what printers are installed through the KDE control center I get:
Error:
An error occurred while retrieving the printer list:
Connection to CUPS server failed. Check that the CUPS server is correctly installed and running.
Error: connection refused
Questions:
How would I check that the CUPS server is correctly installed?
How can I resuscitate the CUPS Daemon?
Do I need to run CUPS? Is there an easier way? Is this a permission problem?
Matthew

i have heard lots of horror stories about suse using those crazy tools with printers
even read where reinstall with new printer attached is how to fix which is just absurd
nothing like making something easy hard
try using the same sane tools the rest of us use
make sure cups is running
ps -C cupsd
if you don't get a PID for cupsd
start cups as root
/etc/rc.d/init.d/cups start
or whatever it is for suse (something off the wall no doubt)
then point a web browser to
http://localhost:631/admin
and put in root and password
and use cups to setup your cups printer -- duhhhh -- without yast or whatever as a crooked agent or broken broker a not in the middle middleman.

Thanks for your reply.

(1) The return to ps -C cupsd is:

PID TTY TIME CMD

What does it mean?

I went ahead with the instructions #2 and #3

(2) Attempting to start CUPS as root returned:

linux:/home/user # /etc/rc.d/init.d/cups start
bash: /etc/rc.d/init.d/cups: No such file or directory




(3) pointing a Web browser at http://localhost:631/admin returned:

An error occurred while loading http://localhost:631/admin:
Could not connect to host localhost (port 631)


Matthew

Did you ever resolve this CUPS problem?
I had exactly the same problem a while back and have got it again!
Fixed it last time by un-installing then re-installing CUPS..... not this time though.
CUPS seems about as much use as a chocolate teapot.

I did solve the problem but not in a way that would probably help you. I installed Suse 9.3 to upgrade and finally get my hp 1350 printer working. It was while fiddling around with the latter problem that I managed to kill the daemon.
Matthew

Actually, I have got suse 9.3 and did a clean install on another HDD on this PC, but haven't got around to copying my 9.2 mail folders and other documents across.

The PC giving me the CUPS problem is at work, running 9.2, can I update that to 9.3 without doing a complete re-install? If so, how do I go about it?

This PC is also giving me a printer problem and when I go to localhost:631 I get asked for username and password. I read that it wants root and password, but it fails to accept this. Any ideas?

I have had loads of Cups problems!

Ross

Boy, talk about the blind leading the blind...
You can certainly try to just upgrade your 9.2 to 9.3, I don't think it will hurt anything though I am not sure it will solve your daemon problem. But, it's worth a try. I believe it will just install the 9.3 Kernel though and that might not be enough.
Matthew

Hello,
I had the same problem that you guys had and this is how i went about fixing it....

step 1. Set up a password by entering the following into the console as root

lppasswd -g sys -a CUPS-admin-name

It will then prompt you to enter a new password. Enter your new password and remember it for step 4.

Step 2. You must edit the cupsd.conf file. This file is located in /etc/cups.
open the file with your favorite editor and find the part of the cupsd.conf file that looks like this....

## Anonymous access (default)
##AuthType None

Change the above to look like this....

## Anonymous access (default)
AuthType None

after changing the lines above save the file.

Step 3. Restart the CUPS server by entering the following into the console

rccups restart

Step 4. Try to log into the srever by doing the following into your browser

http://localhost:631/admin

it may prompt you for a username and a password if so entering the following in the fields

username = lp
password = "The new password that you entered in step1"

From here I was able to use the CUPS server. I hope that helps.

Thanks for the recipe. Though I've got the problem sorted at the moment due to the new installation, I've made a note of your advice and will tuck it away for use in resuscitating any future cups daemon deaths I come across.
matthew

Thanks Unmindfulawe, but, sadly nothing much helps for me!

Tried your solution on work computer. When I tried to restart cups I got an error.... blah blah 98. Sorry not at work now and cant remember the details. Google shows it pretty common and no solution that worked for me.

On this computer, it worked up to logging into localhost:631, but would not accept username and new password. Tried more than once.

Managed to delete the unworking printer with Yast, but could not re-install as it was not recognized. Stupid op system found it once and auto installed it but now wants to be told what it is and where it is. How do you know which USB port you are plugged into?

Very glad I kept this machine dual boot. Everything works fine in Win98.
I reckon the Blue Screen of Death is nothing compared with the crap-outs of linux. At least windows starts working again when you reboot. Who gives a toss about security anyway?

I have overcome the problems at work by running Win4lin and installing Win98. Now all my CAD software works fine, and I can print it. And when I do get a crash I can restart windows right away without a reboot.

I would NOT be able to make a living under Linux.
Free is OK, but no support is useless.

I will be installing Win4lin on this PC.

I'm sorry to hear that it didn't work out. Did you use "lp" as the user name to log in? I can understand all of your frustrations with linux. It seems as though once you solve one problem there's another to be dealt with. I'm going to stick with it though and try to get everything solved. I know that things will only become easier to configure down the road.

Yes, used "lp" in username. Used nearly everything I could think of.
Looks like the problem is with the USB port, (works fine under Win98), and USB works fine with mouse and various memory sticks and MP3 player in suse. So don't understand the problem, especially since it was all working fine, then suddenly didn't.
A point of note, Suse 9.3 also stopped accessing this usb printer, when I switched HDD. I have one HDD with 9.2 installed and another with 9.3. So maybe there is something odd with USB, even though I tried in on both the motherboard USB and a PCI addon USB card. And all USB ports work fine on Win98.

It all becomes a bit of a joke!
I am going to try a complete re-install of the printing system when I get home this evening. I've not quite given up - yet.

Ross

The latest issue of Linux magazine notes an error in the CUPS system which causes it to crash. Though I don't really understand what exactly is meant here, this is the quote: "The CUPS provides a portable printing layer for linux operating systems and when processing a PDF file, bounds checking was not correctly performed on some fielsds. Ths could cause the pdftops filter (running as user "lp") to crash.

Matthew

On my PC at work, I did a complete re-install of the printing system, with Yast, logged in as root. As all my printers are attached to a windoze computer somewhere in the building, and none of them were working, I thought I had nothing to lose.

The install went fine, but as expected, I still could not login to localhost:631.
A bit of digging around the CUPS manual area led me to an explanation. I will edit this posting to-morrow and show you the link. It's Article #275 I think.
Apparently, Suse handles the CUPS passwords and username differently to the rest of the world.
I followed the instructions, and now I have been able to log in to localhost:631 and setup my printers again. Hooray!

I will try the same again at home. Not to-night though as my sister is visiting from Portugal and brought over a rather large box of red wine. Hic!

The link, as promised:
http://www.cups.org/articles.php?L275+I0+TFAQ+P1+Q

Best of luck,
Ross

Thanks Ross, I look forward to your explanation. Though my printer problems are now solved with a new intall of Suse 9.3
I know I am going to bump up agains this issue again and would like to understand it.
Where again did I read..."in vino veritas.' ?
Matthew