> Date: Wed, 4 Sep 2013 07:42:18 -0700 (PDT) > From: Sirsendu Roy <[email protected]> > To: BLFS Support List <[email protected]> > Subject: [blfs-support] Cannot Print document using HP Printer > > Hello All, > I have already written a post about this problem but unfortunately didn't get > any answer. So I am writing again. > I have a HP Deskjet 1050A Printer which works fine under Ubuntu. Now after > having created BLFS (With KDE ) I have tried to get the printer to work. > First of all I have compiled all the printer related packages from the BLFS > website. > ThenI have followed the instruction of > http://hplipopensource.com/hplip-web/install/manual/distros/lfs.html to build > and install the hplip driver. > > In kde print applet the printer (My printer is HP deskjet 1050 All in one) > the printer is automatically detected when I plugged in the printer. > > But when I try to print a pdf document (opened with okular) I am getting the > following error message : > write failed: Interrupted System call. > > > And when I try to print something from Kwrite or trying to print a test page > I am getting the following error message : > Filter failed. > > I have already installed the cups filter 1.0.36 as mentioned above. > Regards, > Roy
Some googling on the kwrite and okular error messages that you note, gave e.g.: -- * http://forums.opensuse.org/english/get-technical-help-here/applications/475889-printing-stopped-working.html * http://en.opensuse.org/Portal:Printing -- There, they deal with 'pstoraster failed' in error_log, and suggest fixing it via setting 'RIPCache 128m' or 'RIPCache 1024m' (or other appropriate value) in cupsd.conf . It may be related to the more-underlying issue discussed at: == * http://stackoverflow.com/questions/5909717/interrupted-system-call-error-when-writing-to-a-pipe == However, obviously & as noted in others' replies, you'll want to look at your own error_log and see if it points you directly to a cause/fix, or at least gives enough info for googling on. And, it's still a good idea to at least do those basic sanity-checks (is cups running, can you login to its admin interface and test-print from there, etc) per another reply: sometimes 'higher-level' applications can give slightly misleading, red-herring error messages. hth, akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
