... or spinning its wheels (not sure which).

Here's some background: I've been having nothing but trouble getting a collection of systems to be able to print reliably via CUPS. (Pages shifted down on the page and getting the bottom chopped off is the biggest problem but that probably best left to another thread.) A variety of SuSE versions are in use on the LAN (9.0, 9.2, and 10.0). The CUPS print server is running 9.0 and will have to for the foreseeable future (older, smaller system that I'm not sure would be able to handle 10.0).

I was getting fed up and tried to set up LPRng as the printing system instead of CUPS on a system running 10.0. I've had good luck running LPRng for printing in the past but I couldn't get it to even recognize that there was an lpd port alive on the server. When I attempt to go back to CUPS, YaST hangs during the initial "reading settings" phase of the printer setup. I was working on this last night when I got called into work to put out a fire and, this morning, it was still at "68%" and hadn't gotten to the actual configuration screen.

Any ideas on what's causing the printer configuration to get stuck? I'm running an "rpm -qaV" to see if anything obvious shows up but beyond that I'm not sure what else to look at. Re-installation? Seems drastic and I hope to avoid that but I've never seen YaST act this way before.

TIA...

Rick

You may try to reinstall Yast2 itself.

Tried that but that didn't work. I wound up removing everything CUPS-related and then reinstalling the same packages. That seemed to do the trick. A bit scary, though, given all the stuff that's dependent on CUPS. (Are we approaching the Linux equivalent of DLL Hell yet? :-/ )