SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Recently I have discovered that I chose the wrong printer driver. Instead of choosing the Color driver, I chose the Monochrome. I discovered this when trying to print a color PDF. Not wanting to mess around with command line options, I decided to try and use Yast Printer management to set it right. However, It hangs when I get to "The driver information has changed. Rebuilding driver list." It stops at 4% and just spins its wheels! And yes, I have let it sit for a while, sometimes up to 6 Hours and it's still at 4%! Please help.
If you have not already found a cure for the above problem then this is the answer.
In openSUSE 10.2 Bugzilla bug number 229231 causes YaST2 to hang in the printer database.
Go to RPMfind.net and select the download for
Install this with zen installer then go to YaST2. Select Hardware and then Printer. Add your printer. It may be a good idea to remove any existing default printer unless you are using more than one printer. You will be able to perform a test print part way through this procedure.
following the link above I've just found yast2-2.15.2-5.i586.rpm and not the release level rpm recomended to solve the problem. Trying to install this rpm (and not yast2-2.14.17...rpm, as recomended above) I have gotten the following error messages from zen:
Updating yast2-2.14.15-3.i586[System packages] to yast2-2.15.2-5.i586[Local packages]
Marking yast2-2.14.15-3.i586[20061225-215639] as uninstallable due to conflicts over y2t_menu from yast2-2.15.2-5.i586[Local packages]
Marking yast2-2.14.15-3.i586[20061226-024804] as uninstallable due to conflicts over y2t_menu from yast2-2.15.2-5.i586[Local packages]
There are no installable providers of yast2-core >= 2.15.1 for yast2-2.15.2-5.i586[Local packages]
yast2-2.14.15-3.i586[System packages] replaced by yast2-2.15.2-5.i586[Local packages]
and I still hang on 4%/40% bug...
Well, this is a replacement for what was posted above:
The link which I provided shows a complete list of rpms in alphabetical order.
The correct rpm, yast2-printer-2.14.17-6.i586.rpm , is clearly listed with the yast2-printer prefix.
You appear to have selected the first yast2 rpm that you came to in the list (without a printer tag) so have another look.
According to various forums some people have used the alternative solution which you mention above. Others have used the yast2-printer etc... fix. They both do the trick. I simply went to the Bugzilla site, made a note of the advised rpm for correcting the printer problem, located it and then installed it. Bugzilla made no mention of an alternative solution but that does not mean an alternative does not exist.
Another way to fix this problem is to go into online updates and download the cups patch. It's supposed to fix the bug that we have been discussing here. I saw it after wiping my system, reinstalling everything, adding a patch database to software management, then updating the software.
Last edited by Madd the Sane; 02-04-2007 at 09:59 PM.