FedoraThis forum is for the discussion of the Fedora Project.
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.
Just upgraded from FC5 to FC6, and previously I had printing working fine. I have a virtual PDF printer installed, and a Lexmark E232 Laser (uses the generic PCL6 driver). Both printers worked well under FC5, now after the upgrade the virtual PDF printer still works ok, however printing to the Lexmark doesn't work. CUPS says that the job is processing, but after a time it says that the "printer is not connected, will retry in 30 seconds.."
I tried uninstalling the printer, unplugging, replugging (where it is detected properly - lsusb shows it up and it appears in the printer list in CUPS to install as a USB connected Lexmark International E232, which is correct..) and reinstalling, the restarting CUPS. Same result.
After installing the printer it shows up as - Make and Model: Generic PCL 6/PCL XL Printer Foomatic/pxlmono (recommended)
Printer State: idle, accepting jobs, published.
Device URI: usb://Lexmark/E232
I'm not sure what I'm looking at in the error log, which is set to debug, but this appears frequently - D [24/Dec/2006:21:30:35 +1100] cupsdUpdateCUPSBrowse: Refused 180 bytes from <my local machine name edited out>
I'm not really sure where to start on this one, it finds the printer OK, it was working fine previously - both locally and shared over Samba (which is working OK as well, I can still see and use all the other shares and the PDF printer device). SELinux is disabled. I was also getting the printer showing up twice, one copy created automatically by HAL, but I deleted that one and disabled the HAL daemon for now. Using the HAL created one also returned errors.