Bug 130177

Summary:	yast2 printer config hangs
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Aaron Williams <aaronw>
Component:	YaST2	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Aaron Williams 2005-10-23 08:03:02 UTC

I just upgraded from 9.3 to 10 and when attempting to configure the printer in 
YaST2 it hangs when it says "Load current settings" and hogs the CPU. 
 
I see the following in the logs: 
 
 
2005-10-23 00:55:51 <1> squeeky(16883) [YCP] Printerdb.ycp:318 Checking 
foomatic database 
2005-10-23 00:55:52 <3> squeeky(16883) [Interpreter] Printer.ycp:1010 Parsing 
file '/var/lib/YaST2/printers' failed 
2005-10-23 00:55:52 <3> squeeky(16883) [Interpreter] Printer.ycp:1010 
SCR::Read() failed

Comment 1 Aaron Williams 2005-10-23 08:04:14 UTC

Note that I had my system configured for an HP Laserjet 4/4M Plus Postscript printer.  Also, on startup, lsoptions was running and also consuming all of the CPU.

Comment 2 Michael Gross 2005-10-24 12:47:58 UTC

Please also attach the yast-logfiles.

Comment 3 Aaron Williams 2005-10-24 16:45:26 UTC

Unfortunately I no longer have them.  I do have some more information though.  When I attempted to start CUPS I would always get the error message inside cups that it could not bind to port 631 because it was already bound.  This was rather strange because netstat showed that the port was free.

I reinstalled all the CUPS packages and the YaST printer support with no luck.

Eventually I rebooted my system and after rebooting YaST began behaving properly and I was able to configure my printer.

I then ran into problems with the sound support with ALSA.  YaST sound would not allow me to edit or delete my sound card and could not otherwise configure it.  My sound card is a Sound Blaster PCI 128 OEM card (es1370).  In the process of attempting to get that working I nuked the YaST2 log file, and again, after a couple of hours managed to get it to finally work, though I don't remember the exact sequence that led to it working.  I believe I had to delete some of the hardware files to force it to re-detect everything.

-Aaron

Comment 4 Michael Gross 2005-10-25 13:36:51 UTC

So this is no longer traceable for us. Hence closing it.
If you can provide the logfiles anyway (e.g. by repeating/reproducing this), attach them and reopen the bug. Thanks.