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.

I have exactly the same problem on 2 out of 3 machines with 10.2 on them.
The problem seems to have just started with the holidays ??!!

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
yast2-printer-2.14.17-6.

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.

Further to my above post, it seems like some people are having problems finding the necessary rpm at Rpmfind.net. Ironic isn't it?

Please try this instead:-

http://download.opensuse.org/distrib...rce/suse/i586/

HI,


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:

Unresolved dependencies:
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:

I went to rpm.pbone.net

{just to simplify:

http://rpm.pbone.net/index.php3?stat....17-6.i586.rpm

}

and had installed the recommended rpm and had my hp F380 network printer correctly installed.

BTW:

I've found a solution that I haven't tested, but the author in

http://www.calivia.com/blog/mike/upg...-opensuse-10-2

says it will correct the problem and if so, it seems to be a simpler way:

sudo rm /var/lib/YaST2/ppd_db.ycp
sudo /etc/init.d/hplip restart
sudo /etc/init.d/cups restart


Best regards

Daniel

Daniel,
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.
Best wishes.

Correct beachboy2,

I've missed the "printer", sorry.

But has anyone tried to use the next solution which seems to be easier?

Best regards

Daniel

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.
Best wishes.

I had the exact same problem and the three sudo commands fixed it. Thanks.

Quote:

sudo rm /var/lib/YaST2/ppd_db.ycp sudo /etc/init.d/hplip restart sudo /etc/init.d/cups restart

I ran those commands on my boxes and it fixed all of them perfectly!!

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.