I've got a strange problem with cups. Last year, I discovered that if I built cups before gtk+, the cups queues would appear in the file->print dialogs, which is good. Built a system in September using linux-2.6.31 headers, udev-146, and cups-1.3.11, all was fine.
At the end of December I tried building a system with cups-1.4 (and udev-149, 2.6.32 headers) - that was a disaster, the cups scheduler appeared to segfault. Reverted to 1.3.11 and rebuilt what I thought was using cups headers, then later found that file->print didn't seem to work (the print box was greyed out). By this stage I'd got other problems (Mesa - now sorted) so I put the printing down to "must have missed rebuilding something". I'm now half-way through my current 6.6 build. Cups testpage works, but printing from file->print is still greyed out. Looking a little more deeply, what is actually happening is that firefox stops repainting its window - so, if I move the dialog it smears a little, and if I then open and close a term over it that area is black. Eventually, the dialog is updated and the print queue is available. Last night, I noticed that the dialog eventually disappeared, but by that stage I was on another desktop - possibly, I'd clicked on 'cancel' while dragging it. The delay seemed to be about a minute. Today, I've taken another look at the December system - in evince the print dialog is totally grey (apart from the title) for a minute, then available. In epdfview there doesn't seem to be any problem. I've now rebuilt 1.3.11 with some security fixes from fedora. Didn't make a difference, except that the delay in forefox is now only 30 seconds. Logs (in debug mode) show vast amounts of activity (lots of '17' responses, whatever that means, then some others. This doesn't only happen the first time, it is every time I open the print dialog. The printer is usb, but the problem is with the queue(s) and happens whether or not the printer is powered on. I can remember Greg KH mentioning *something* to do with a print problem on lkml (it was a reason why he was having trouble responding, because he couldn't print), posssibly something to do with udev, but I can't find that. Any ideas, please ? ĸen -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
