Bug 225339 - Yast2 Loading printer database problems
Summary: Yast2 Loading printer database problems
Status: RESOLVED DUPLICATE of bug 229231
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i386 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-01 16:02 UTC by Rylan Cottrell
Modified: 2006-12-19 17:12 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Y2Log (3.13 MB, application/octet-stream)
2006-12-01 16:09 UTC, Rylan Cottrell
Details
ppd_db.ycp file (2.23 MB, application/octet-stream)
2006-12-01 18:10 UTC, Rylan Cottrell
Details
printers file (257 bytes, application/octet-stream)
2006-12-01 18:10 UTC, Rylan Cottrell
Details
Back Trace of Yast2 printer (27.22 KB, application/octet-stream)
2006-12-01 18:50 UTC, Rylan Cottrell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rylan Cottrell 2006-12-01 16:02:47 UTC
When I loaded Yast2 to add another printer it is hanging on check database for printers. With a progress bar "The list of installed drivers has changed. Building database of drivers." And has been stuck at 4%

The last entries in the y2log are

2006-12-01 08:48:44 <1> on(5165) [YCP] Printerdb.ycp:340 Checking foomatic database
2006-12-01 08:48:44 <1> on(5165) [YCP] Printerdb.ycp:343 Database changed
2006-12-01 08:48:44 <1> on(5165) [agent-ppd] PPDdb.cc(createdbThread):419 CreateDbThread started
2006-12-01 08:48:56 <1> on(5165) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1439 Database file parsed correctly by YCP parser
2006-12-01 08:48:56 <1> on(5165) [agent-ppd] PPDdb.cc(loadPrebuiltDatabase):1670 Database contents is OK


Which gives me the impression that something else is causing yast2 to hang.
Comment 1 Rylan Cottrell 2006-12-01 16:09:48 UTC
Created attachment 107899 [details]
Y2Log
Comment 2 Michal Zugec 2006-12-01 17:13:50 UTC
Attach files /var/lib/YaST2/ppd_db.ycp and /var/lib/YaST2/printers
Also make a backtrace, please
After that you can solve it by backarround - delete /var/lib/YaST2/ppd_db.ycp and start printer module again
Comment 3 Rylan Cottrell 2006-12-01 18:10:42 UTC
Created attachment 107915 [details]
ppd_db.ycp file
Comment 4 Rylan Cottrell 2006-12-01 18:10:59 UTC
Created attachment 107916 [details]
printers file
Comment 5 Michal Zugec 2006-12-01 18:30:40 UTC
I can't reproduce it 
Attach backtrace please
Comment 6 Rylan Cottrell 2006-12-01 18:50:46 UTC
Created attachment 107933 [details]
Back Trace of Yast2 printer
Comment 7 Juan Erbes 2006-12-04 02:15:06 UTC
(In reply to comment #0)
> When I loaded Yast2 to add another printer it is hanging on check database for
> printers. With a progress bar "The list of installed drivers has changed.
> Building database of drivers." And has been stuck at 4%
> 
> The last entries in the y2log are
> 
> 2006-12-01 08:48:44 <1> on(5165) [YCP] Printerdb.ycp:340 Checking foomatic
> database
> 2006-12-01 08:48:44 <1> on(5165) [YCP] Printerdb.ycp:343 Database changed
> 2006-12-01 08:48:44 <1> on(5165) [agent-ppd] PPDdb.cc(createdbThread):419
> CreateDbThread started
> 2006-12-01 08:48:56 <1> on(5165) [agent-ppd]
> PPDdb.cc(loadPrebuiltDatabase):1439 Database file parsed correctly by YCP
> parser
> 2006-12-01 08:48:56 <1> on(5165) [agent-ppd]
> PPDdb.cc(loadPrebuiltDatabase):1670 Database contents is OK
> 
> 
> Which gives me the impression that something else is causing yast2 to hang.
> 

I got a similar problem, but after the last update, mi printer do'nt works, and the I try to reconfigure the printer, and got the same results: is hanging on check database for
printers. With a progress bar "The list of installed drivers has changed.
Building database of drivers." And has been stuck at 4%.
After deletting the files /var/lib/YaST2/ppd_db.ycp and /var/lib/YaST2/printers the yast printer module works ok.
Comment 8 Michal Zugec 2006-12-04 14:29:34 UTC
Sorry, but this is strace not backtrace.
Backtrace you can create when set "ulimit -c unlimited" and after crash there will be core file or core.$PID (dumped core) in your current directory.
Next start "gdb /usr/lib/YaST2/bin/y2base core" and attach here output
Comment 9 Shaun Qualheim 2006-12-15 00:48:09 UTC
Same 4% deal here... let me know what I can do to help.
Comment 10 Rylan Cottrell 2006-12-18 18:37:10 UTC
Sorry about the late reply I was off in Mexico getting Married.

I have updated to 10.2 GM which seems to have fix problem. I have been unable to reproduce the problem to supply the back trace. 
Comment 11 Shaun Qualheim 2006-12-19 03:20:22 UTC
I can supply a backtrace of my machine doing it.  Can someone give me a link to instructions on how to create a backtrace?

Thanks!
Shaun
Comment 12 Michal Zugec 2006-12-19 17:12:22 UTC

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