http://bugzilla.novell.com/show_bug.cgi?id=512440 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=512440#c1 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com Summary|Cannot install any printers |yast2-printer fails to |in Yast2, works fine in |create PPD database on one |Control Center |particular system --- Comment #1 from Johannes Meixner 2009-06-12 06:50:26 MDT --- Summary: "Failed to create PPD database" ... "happens always on one system and never on another system." I.e. something is strange on this "one system". yast2-printer calls /usr/lib/YaST2/bin/create_printer_ppd_database which has a 300 seconds timeout to avoid an endless hangup. I assume you prefer the above error message than having just an endless hanging YaST ;-) I don't know why it takes so long on your "one system". Perhaps it helps to increase the value in the MAXIMUM_WAIT="300" line in /usr/lib/YaST2/bin/create_printer_ppd_database to check if it may finish after some more time. What /usr/lib/YaST2/bin/create_printer_ppd_database basically does is to call /usr/sbin/lpinfo -h localhost -l -m Run only this command directly as root on the command line. On my openSUSE 11.1 system it takes less than 4 seconds for 36464 installed printer descriptions ------------------------------------------------------------ root@host# time /usr/sbin/lpinfo -h localhost -l -m | wc -l 36464 real 0m3.675s user 0m1.344s sys 0m0.068s ------------------------------------------------------------ and even after removing CUPS' internal PPD cache (i.e. the situation directly after a new installation) it still takes less than 12 seconds on my machine ------------------------------------------------------------ root@host# rccups stop Shutting down cupsd done root@host# rm /etc/cups/yes/ppds.dat root@host# rccups start Starting cupsd done root@host# lpstat -r scheduler is running root@host# time /usr/sbin/lpinfo -h localhost -l -m | wc -l 36464 real 0m11.948s user 0m1.368s sys 0m0.132s ------------------------------------------------------------ so that a 300 seconds timeout seems to be really enough if the system is o.k. Additionally run directly as root on the command line yast2 printer and check if it works this way. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=512440 User mvidner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=512440#c2 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | --- Comment #2 from Martin Vidner 2009-07-03 00:04:34 MDT --- Anything that looks like YaST can be screened by the YaST team. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=512440 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.