Bug 234535

Summary:	YaST2 Printer Configuration/y2base Hangs CPU at 99%
Product:	[openSUSE] openSUSE 10.2	Reporter:	Mike Wells <mike_wells>
Component:	YaST2	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	auxsvr
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	strace -p `pidof y2base` output

Description Mike Wells 2007-01-13 20:20:43 UTC

After reinstalling my hp-deskjet 6540 (hplip/hpijs) via CUPS (http://localhost:631/) the YaST2 Printer Configuration utility hangs at the 4% mark when building the driver database (y2base) and CPU usage remains at 99.X% until the process is killed. The printer was originally installed via YaST2 but apparently incorrectly because the hp-toolbox could not be launched after manually starting hplip and was outputting an error message to install the printer via CUPS. The CUPS installation was successful with the exception of having to manually activate (enable) the hplip service via YaST2 System Services. After installation of the "new" printer in CUPS the original printer installation (via YaST) was deleted using CUPS. The "broken" YaST2 Printer Configuration utility was noticed when attempting to double check the "new" printer installation.

Comment 1 Matej Horvath 2007-01-15 09:18:08 UTC

Please attach your yast logs.
http://en.opensuse.org/Bugs/YaST

Comment 2 Peter B 2007-01-15 17:35:46 UTC

I can confirm this, I have attached yast logs and strace output of the running y2base.

Comment 3 Peter B 2007-01-15 17:53:23 UTC

Created attachment 113018 [details]
strace -p `pidof y2base` output

Comment 4 Peter B 2007-01-15 18:11:37 UTC

The yast logs are very big (7.5 MiB), so you can get them from http://auxsvr.dyndns.org/~petros/y2logs.tgz. Please notify me when you don't need them anymore so as to remove them.

Comment 5 Matej Horvath 2007-01-17 08:37:19 UTC

I was not able to find the buggy yast module or any other source of the problem, so I'm going to reassing it by my guess to the yast-printer maintainer.

Comment 6 Matej Horvath 2007-01-17 13:30:44 UTC


*** This bug has been marked as a duplicate of bug 229231 ***