On Sunday, February 15, 2015 06:20:13 AM Lisi Reisz wrote: > On Saturday 14 February 2015 23:40:58 Ric Moore wrote: > > On 02/14/2015 05:41 PM, Lisi Reisz wrote: > > > On Saturday 14 February 2015 21:50:15 Ric Moore wrote: > > >> On 02/14/2015 04:09 PM, Gene Heskett wrote: > > >>> On Saturday, February 14, 2015 03:15:49 PM Ric Moore wrote: > > >>>> On 02/14/2015 03:05 PM, Gene Heskett wrote: > > >>>>> I have a "save as" grab from an insurance company web site that > > >>>>> is supposedly the link to grab a .pdf of a policy of mine > > >>>>> that's a couple decades or more old. > > >>>>> > > >>>>> Looked at in a text editor, it resembles somewhat an .html > > >>>>> file, but has an extension of ".pt", and apparently iceweazal > > >>>>> is stymied as to what the heck to do with it, so it spins > > >>>>> forever. > > >>>>> > > >>>>> Opening up its prefs/applications and entering .pt in the > > >>>>> search gets me an empty window. > > >>>>> > > >>>>> Does anyone have a clue what this is? Its potentially worth > > >>>>> quite a bit of money to me. > > >>>> > > >>>> Doah! What do you get if you type > > >>>> file filename.pt ?? > > >>>> (insert your filename) Ric > > >>> > > >>> gene@coyote:~/Documents$ file ./Aflac-server.pt > > >>> ./Aflac-server.pt: HTML document, ASCII text, with very long > > >>> lines, with CRLF, CR, LF line terminators > > >>> > > >>> Is that enough to choke iceweasal? > > >> > > >> Just for giggles, try opening it with gimp or Office? Ric > > > > > > In desperation - vi? Try dos2unix? Then try them all again? > > > > I call that trouble shooting with a shot gun. > > Not quite, only almost. vi is always a good idea where text is > concerned. dos2unix can sometimes sort out line terminators. Having > used dos2unix it would have been worth trying gimp and vi again - > though not,. of course, Office. > > > Shoot enough, you're bound > > to hit something. > > Only if you are shooting in the right direction. And if you hit, that > is great. We are after all shooting blind. Gene doesn't exactly give > us enough information for the more usual methods of troubleshooting - > and if gimp is worth a try, vi certainly is. > > Lisi
As previously posted Lisi, problem is in iceweasal, and solved. Before it decided to spin forever, it actually did download the pdf I was clicking on. I found 4 copies in the Downloads directory when I looked. Installed okular, which was missing from this install, and it printed right up. That was the target of this exercise. ;-) Now, sitting here over a morning cuppa and contemplating the rest of my sins, I am wondering if the missing okular was the problem. What does iceweasal by default call to, to process a .pdf? According to about:config, /usr/bin/acroread, which does not exist, and on the next line it calls /usr/bin/acrorerad #custom comment. That will likely cause iceweasal to throw up its hands. Sigh. Since its user set, I'll change both to point at okular. FWIW, for those using acroread, okular is what acroread should ought to have been but isn't. Particularly when actually printing the document. Using acroread, if the printer sneezes and wrecks a page, it just goes on its merry way, but okular see's the error, waits for me to clear the jam, and dutifully reprints the jammed page(s) even if the printer is in duplex mode. That was a very welcome improvement discovered by a jam. Thanks Lisi. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502150927.17074.ghesk...@wdtv.com
