https://bugzilla.novell.com/show_bug.cgi?id=727911 https://bugzilla.novell.com/show_bug.cgi?id=727911#c17 --- Comment #17 from Darren Freeman <dfreeman@ieee.org> 2012-03-06 13:46:04 UTC --- I am running a 4 GHz quad core Phenom II with 8 GB of RAM.. and if this really is the explanation, then it's slow enough that the user needs some feedback to stop them from giving up and/or snapping their SUSE install disc and binning it. It could be as simple as the Microsoft flashlight scanning from side to side - anything to indicate that it's still busy. Simply reporting that there are no drivers is cause for aggravation. You can't save a partial config with no driver and come back to it, so after all this effort to configure the printer you don't want to give up, but it seems like you have to. I usually run the package manager at this point (without closing the printer configurator) and try to figure out what I'm missing, and then I see that I have all of the relevant packages. I check where the files are installed, because I will need one for the manual PPD entry. This still isn't enough time for the problem to be fixed all by itself, so I don't know whether to believe your explanation. It would be worth installing a minimal install into a virtual machine to prove that it fixes itself after a long enough time.. I don't believe that it does. I think the user has to trigger an event. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.