|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast printer module hangs up at "Building database of drivers: 4%" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Henryk Hecht <nvbugs> |
| Component: | Printing | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Johannes Meixner <jsmeix> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | andreas.hanke, david, fmfischer, forgotten_1-yzHWP3HO, forgotten_Drfk9mafMw, frede, Frudo1, hans.giebenrat, krange, marcz, mike_wells, oscarpoio, rylan, sebastien.rohaut, shaun_qualheim, the.cars.support, traeuble |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 619266 | ||
| Attachments: |
/var/log/YaST2/y2log for hung yast printer module
Just a screen shot of the user interface when the problem occurs |
||
|
Description
Henryk Hecht
2006-12-17 04:28:21 UTC
Created attachment 110025 [details]
/var/log/YaST2/y2log for hung yast printer module
*** Bug 229198 has been marked as a duplicate of this bug. *** Right now it happens for me with the non-updated cups package.
Therefore it doesn't depend on the cups update package.
And it never happened before for me.
The last lines in /var/log/YaST2/y2log (folded lines) are:
------------------------------------------------------------------------------
2006-12-18 11:57:31 <1> nelson(13882) [YCP] Printerdb.ycp:340
Checking foomatic database
2006-12-18 11:57:31 <1> nelson(13882) [YCP] Printerdb.ycp:343
Database changed
2006-12-18 11:57:31 <1> nelson(13882) [agent-ppd] PPDdb.cc(createdbThread):419
CreateDbThread started
2006-12-18 11:57:32 <1> nelson(13882) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1439 Database file parsed correctly
by YCP parser
2006-12-18 11:57:32 <1> nelson(13882) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1670
Database contents is OK
------------------------------------------------------------------------------
(there are no further messages in y2log) and here it hangs
with the "Building database of drivers" popup at "4%"
while the process "13882" running "/usr/lib/YaST2/bin/y2base printer qt"
continuously uses 100% CPU in this process tree:
------------------------------------------------------------------------------
yast2(13861)---y2base(13882)-+-ag_initscripts(13912)
|-{y2base}(13908)
`-{y2base}(13989)
------------------------------------------------------------------------------
The same hangup happens again and again after killing it.
After
rm /var/lib/YaST2/printers
rm /var/lib/YaST2/ppd_db.ycp
it works again.
As it makes YaST printer useless it is a "major" loss of functionality. Only a guess: The problem may happen only when new software packages are installed which overwrite, replace, or change files under /usr/share/cups/model/. In comment #0 there was an update of the cups package and I had installed the hplip package anew before comment #3. *** Bug 229629 has been marked as a duplicate of this bug. *** *** Bug 225339 has been marked as a duplicate of this bug. *** I have the same problems and even after installing the printers I can NOT print. However (I am using the tcpd) after removing the lines ALL : ALL EXCEPT ..... from the hosts.deny file printing is OK I was just about to report the same bug. Happens to me on a desktop machine but not on a laptop computer! The laptop has no printers configured, though, as opposed to the desktop machine. Maybe this helps to track down the bug. And in support of comment #4 I also think the severity is major. I think #223805 is the same. I installed 10.2 fresh on one laptop and as an update on another. With both, when I went to configure the printers in YaST, it brought my systems to their knees for about 3 minutes. All the memory and swap space was being used and my hd was going to catch fire. After about 3 minutes, everything was back to normal and I was able to find my printers from my server and they work. Not sure if this is related to the current posts. The laptops I did the install on are in client mode. I hope this gives some more info to look at. Workarround: delete /var/lib/YaST2/ppd_db.ycp I will fix it after vacation *** Bug 231247 has been marked as a duplicate of this bug. *** *** Bug 230253 has been marked as a duplicate of this bug. *** fixed in yast2-printer-2.14.17 *** Bug 232080 has been marked as a duplicate of this bug. *** *** Bug 235046 has been marked as a duplicate of this bug. *** *** Bug 234535 has been marked as a duplicate of this bug. *** *** Bug 235051 has been marked as a duplicate of this bug. *** I'm still getting this bug. I have the latest updates from the update service installed. Any ideas? (The workaround does work for me btw... so I can fix it temporarily, but it appears to be coming back after a while.) Created attachment 114227 [details]
Just a screen shot of the user interface when the problem occurs
Sorry, I just checked my packages and appearently I only have 2.14.15-3 for the yast printer stuff. I'll upgrade. :) I had the same problem (and also problems during the start of Suse) and searching on the new I found a solution, I just had to install the package yast2-printer-2.14.17-6 form Factory development versión.... why not to publish an update of yast2-printer to solve this bug? *** Bug 232794 has been marked as a duplicate of this bug. *** SWAMPID is 8106 please submit patch and patchinfo file. thanks thanks, done *** Bug 239430 has been marked as a duplicate of this bug. *** released *** Bug 228148 has been marked as a duplicate of this bug. *** Why isn't this being backported to 10.2? It is one of the "most annoying bugs", right? Reopening, because this is not "fixed" in 10.2. It _IS_ backported for 10.2 only this bug is not assigned as duplicate "that" bug where is info about backporting |