> Date: Sun, 22 Sep 2013 01:08:04 +0100 > From: [email protected] (akhiezer) > To: [email protected] > Subject: [blfs-support] cups printing in blfs-7.4 > > > Date: Sat, 21 Sep 2013 12:02:11 -0700 (PDT) > > From: Sirsendu Roy <[email protected]> > > To: BLFS Support List <[email protected]> > > Subject: Re: [blfs-support] Kde cannot start !!!!! solved !!!!! > > > . > . > > > > As per the HP printer problem is concerned, I have tried almost every > > combination, but somehow it didn't work. > > SO I would like start from the beginning unstalling everything. > > Can you please tell me the order in which I will install the required > > module and and configure everything. > > > First, did you see the thread from Fernando, that ended with the message: > -- > Fernando de Olivei Sun Sep 15 17:29 156/6529 \ > [blfs-dev] Can print - again, but... (was: Cannot print - > -- > ? There, Fernando summarises (AIUI) that downgrading to an earlier version of > cups*, got printing working again for him (with an Epson (?) printer). > > > So, you might want to retry with the version(s) that Fernando describes. > Normally I'd install, in this order: > foomatic-rip, hpijs, gutenprint, ghostscript, cups, cups-filters. > But I've not actually built any lfs/blfs-7.4 stuff yet - haven't even got > near > to it. > Normally I'd never touch hplip: but as it's an HP All-In-One device, so you > may > want to use hplip in order to more-readily use the fuller range of > functionality > of the device; but I'd suggest at most doing so only further down the line & > after you've got basic printing working without hplip. Btw, as/when going the > hplip route, be sure to get an hplip version that has got the recent security > issues corrected (ref e.g. the '21 Aug' entry in Slackware changelog > 'www.slackware.com/changelog/current.php?cpu=x86_64' ; and bear in mind the > likes of the Aug 30 & June 4 entries). >
In case it needs saying explicitly: I'd recommend quite strongly that you _don't_ launch into the printing stuff, _until_ you're reasonably (sensibly) sure that your underlying system is behaving normally: otherwise you'll very likely be wasting your time. The reported issues with can't-start-kde (/dev/... problem), konsole (possibly /dev/... issue), X11 stuff having its permissions changed, &(?)usw, should at least give pause for thought. For a common-usage desktop kde setup you'd at least want to be able to do the following reliably and repeatably: --- * login & logout of KDE. * clean boot & shutdown of machine. * xterm/konsole shell environment works OK for everyday stuff. * links/lynx/konqueror/... can show and navigate basic websites ok. * imap/pop & smtp email (even if just through a secondary isp account) works ok. NB this is as distinct from webmail. * jpg/png shows onscreen OK (maybe as part of browser tests). --- Without (approx.) those foundations in place, for 'a common-usage desktop kde setup' type of machine, then I'd say it's not sensible to try to build more on top of that at this stage. rgds, akh -- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
