Darryl Gregorash wrote:

On 2007-07-05 09:44, Jim Sabatke wrote:

...

I installed SuSE 10.0 on a friend's machine. He had a fairly frequent problem where all of his jobs got stuck in the print queue. When I checked the queue in Yast, there was always a second printer that had been added (not by a user), that was setup identically to the original entry, except for the printer name.

When I would remove the original printer definition and setup the duplicate, the printer would start working fine again, until the next time it happened.

I upgraded him to 10.2 and the problem surfaced again right away.

I've googled this to death and have found only a few references, the best being a Ubuntu solution which I didn't understand.

Any help out there?

Have you tried deleting both printer definitions to see if a new one shows up on its own?

I'm trying to remember if the installation picked up the printer by itself. I'm hazy on it, but I believe I set it up the first time, so your idea may work. It can't hurt because I can always set it up again through Yast if I need to. Would the detection happen at boot time or when a print queue is needed? BTW, my home system does the same, but the two queues I setup with TurboPrint work just fine with the extra definitions. Thanks much, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Dave Howorth wrote:

On Thu, 2007-07-05 at 10:44 -0500, Jim Sabatke wrote:

...

I've googled this to death and have found only a few references, the best being a Ubuntu solution which I didn't understand.

Perhaps if you posted the URL, somebody might understand it?

Cheers, Dave

OK, here's the link: https://bugs.launchpad.net/hplip/+bug/32302 It initially goes into a sequence for setting up printers with the hplip software, but you will see later on that it is a bug in the gnome-cups-manager that is supposedly fixed in Ubuntu's Edgy. Also, note the tirade at the end of the link as to the degree of knowledge required to patch the problem. I'm no newbie to Linux, but this has had me running in circles, eventually just deleting the handmade printer definition and renaming the auto-generated definition to match the deleted one. It does look like there are some nice HP provided utilities. Now, as for my home system, the printers are on a network server and I'm still auto-detecting similar printers, but as long as I setup ALL printers through the TurboPrint interface, they work just fine. If I use the Yast interface, I run into similar problems. Note: My print server is running SuSE 9.3. My user boxes are running 10.2. TIA, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org