re Daniel's comments: Under Intrepid my machine used to get the same message from lsusb...it listed the "Prolific..." string as you indicated. When I upgraded to Karmic that disappeared. There is no listing identifying the Prolific chip specifically like this at all. As I understand it this ID would be "downstream" of the print driver, making the choice of driver irrelevant until cleared.
Under Intrepid recognition of the printer wasn't reliable. I sometimes had to reboot, or unplug / replug the usb connection or turn the printer off and back on to get the computer to realize it was there. Push the threshold a bit and you get the behaviour I'm seeing now. I wouldn't think this would be a software problem, but the effort on Karmic involved speeding it up. That could have introduced faster timing for handshaking, and the older Prolific chips became marginal or simply too slow. A guess. The following should be taken as coming from someone who has used computers for a long time, but is not familiar with CUPS at the detail level involved here: re the failure after one print: this is a wild shot on my part, but I just had a similar problem with Open Office spreadsheet. It was resolved by removing the old configuration directory (which apparently contained a corrupted file) and letting OO generate a new one. Is it possible there is a similar problem in, say, a spool directory for you? By way of possible clues: does the lockup clear if you turn the printer off and restart it? If so that suggests a handshake signal isn't making it through or is not being processed to clear the print status. I've had this happen, for example, if an end-of-page isn't sent to the printer when the job is complete. The computer "thinks" the job is done, but the printer is waiting for the "Tha's All Folks" signal to tidy up. Adding the EOP automatically is usually set as an option in the printer (driver) config, sometimes in an editor config. re Geoff's comment: having trouble with networked printers, in the context of the flaky Prolific recognition, suggests the hardware recognition problem may be more generic than just the Prolific chip. Whatever it is something changed in the jump from Intrepid to karmic in this area. the "fault" is persistent and reproducible. Hope this is helpful, and not ridiculous in context. A price of learning is to risk being seen as foolish! -- cups fails on usb-parallel printer https://bugs.launchpad.net/bugs/427653 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
