Hi, I have a major problem with the yast printer configuration. Consistently - each time - Yast stalls trying to load the old printer file[s] configuration which seem to be corrupted. I am forced to `kill' [ctrl-esc] the yast2 threads to get back but cannot rebuild the printer definition. I have reinstalled cups, and the yast-printer [through yast] but to no avail and have changed /etc/cups/ files - nothing doing; it still stalls. How can I clear the current printer definition [files, etc] and have yast start with no printer definition/fresh? [yast should have a clear printer button!] Thanks -- Cheers, Serge [Naggar Consulting]
Hello, On Jul 20 18:16 Serge Naggar wrote (shortened):
Yast stalls trying to load the old printer file[s] configuration which seem to be corrupted.
Regarding CUPS see http://lists.suse.com/archive/suse-linux-e/2004-Jun/4134.html and http://portal.suse.com/sdb/en/2004/07/pohletz_cups_manual_reinstall.html When CUPS works well for you - use the CUPS command line tools, see http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html then it is no CUPS problem. Then it might be a corrupted YaST specific file like /var/lib/YaST2/printers /var/lib/YaST2/ppd_db.ycp These are the file names for Suse Linux 9.3 - for 9.1 the file names may be different. Move or remove those files. YaST will re-create them. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hi, Thanks for your suggestions. I read your url references with much interest and hope; then, tried the approaches. Unfortunately nothing seems to work! I feel that there must be another set of files which Yast goes to when it gets stuck in `load current settings' besides the /etc/cups/* files. Any thoughts or ideas? Taking out the /var/lib/yast2/ [printers & ppd_db.ycp] ges them regenerated without any problem but then Yast-printer gets stuck at the same place! I include some of the results of my efforts in the hopes that you will see more than I can - I am especially intrigued by the messages [at the end] relating to: Child exited with status 1 [failed] then 98 [done]. I was hopeful that the `98' meant it was ok but when I tried yast-printer ... Can you shed any light? Following are some of the actual attempts: west:~ # kill cupsd bash: kill: cupsd: no such pid west:~ # rccups stop Shutting down cupsd done west:~ # rpm -qa | grep ^cups cups-drivers-1.1.20-66.1 cups-1.1.20-108.22 cups-libs-1.1.20-108.22 cups-drivers-stp-1.1.20-60 cups-devel-1.1.20-108.22 cups-SUSE-ppds-dat-1.1.20-98 cups-client-1.1.20-108.22 west:~ # rpm -e cups error: Failed dependencies: cups >= 1.1.15 is needed by (installed) cups-drivers-stp-1.1.20-60 cups >= 1.1.20 is needed by (installed) cups-SUSE-ppds-dat-1.1.20-98 west:~ # rpm -e cups-driver-stp error: package cups-driver-stp is not installed west:~ # rpm -e cups-driver error: package cups-driver is not installed west:~ # rpm -e cups-driver-s error: package cups-driver-s is not installed
I then went through Yast to try to remove the `cups' group but yast identified so many other programs [dependencies] which would have to go [>114] that I didn't dare proceed for fear of totally compromising the installation.
west:~ # rm /etc/cups/* rm: cannot remove `/etc/cups/*': No such file or directory west:~ # chown lp:lp chown: too few arguments Try `chown --help' for more information. west:~ # chown lp:lp /etc/cups/ && chmod 775 /etc/cups/ west:~ # rccups start Starting cupsd Message from syslogd@west at Thu Jul 21 17:25:14 2005 ... west cupsd: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting! cupsd: Child exited with status 1! failed west:~ #
I decided to put the /etc/cups/* files back - I had dragged the /etc/cups/* out of /etc/ and created a blank /etc/cups directory - which failed.
west:~ # rccups start Starting cupsd done west:~ # cupsd: Child exited with status 98! I went back to Yast-printer hoping ... but the `load current settings' just hung there - I left it for about a half-hour then used ctlr-esc to kill the six yast2 & lp processes. I hope that you or somebody else will be able to help. Thanks, On Thu, 2005-07-21 at 04:10, Johannes Meixner wrote:
Hello,
On Jul 20 18:16 Serge Naggar wrote (shortened):
Yast stalls trying to load the old printer file[s] configuration which seem to be corrupted.
Regarding CUPS see http://lists.suse.com/archive/suse-linux-e/2004-Jun/4134.html and http://portal.suse.com/sdb/en/2004/07/pohletz_cups_manual_reinstall.html
When CUPS works well for you - use the CUPS command line tools, see http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html then it is no CUPS problem.
Then it might be a corrupted YaST specific file like /var/lib/YaST2/printers /var/lib/YaST2/ppd_db.ycp These are the file names for Suse Linux 9.3 - for 9.1 the file names may be different. Move or remove those files. YaST will re-create them.
Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/ -- Cheers, Serge [Naggar Consulting]
Hi, I faced tha same problem on Pro 9.1. I built the rpm database and did some other things. Didn't work. If you want to see what I have done may be you can do a search on the list. Then I updated KDE to 3.4 beta through Yast. After that I had no problem. Now I have two printers configured on my system. Well I really don't know if that did the trick or some other tweaking with the system did it. But it worked. My labmate's machine is on the original KDE. It still hangs. See if it may help. Regards, Chaitanya. --- Serge Naggar <naggar@sprintmail.com> wrote:
Hi,
Thanks for your suggestions. I read your url references with much interest and hope; then, tried the approaches. Unfortunately nothing seems to work!
I feel that there must be another set of files which Yast goes to when it gets stuck in `load current settings' besides the /etc/cups/* files. Any thoughts or ideas?
Taking out the /var/lib/yast2/ [printers & ppd_db.ycp] ges them regenerated without any problem but then Yast-printer gets stuck at the same place! [snip]
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Hi, I wish that your suggestion had solved the problem - but unfortunately no miracle occured. I am at kde 3.4 and still the print function stalls at 50% - while loading the current settings. I tried to use the localhost:631 but it never completes. Can somebody please help? On Fri, 2005-07-22 at 16:58, Chaitanya Krishna A wrote:
Hi,
I faced tha same problem on Pro 9.1. I built the rpm database and did some other things. Didn't work. If you want to see what I have done may be you can do a search on the list.
Then I updated KDE to 3.4 beta through Yast. After that I had no problem. Now I have two printers configured on my system. Well I really don't know if that did the trick or some other tweaking with the system did it. But it worked. My labmate's machine is on the original KDE. It still hangs.
See if it may help.
Regards, Chaitanya.
--- Serge Naggar <naggar@sprintmail.com> wrote:
Hi,
Thanks for your suggestions. I read your url references with much interest and hope; then, tried the approaches. Unfortunately nothing seems to work!
I feel that there must be another set of files which Yast goes to when it gets stuck in `load current settings' besides the /etc/cups/* files. Any thoughts or ideas?
Taking out the /var/lib/yast2/ [printers & ppd_db.ycp] ges them regenerated without any problem but then Yast-printer gets stuck at the same place! [snip]
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
-- Cheers, Serge [Naggar Consulting]
participants (3)
-
Chaitanya Krishna A
-
Johannes Meixner
-
Serge Naggar